Thanks Bernard, but in order for Context.pm to establish which conf
file to use, it has to be read. Currently, requests to the second site
are still going to the first sites Context.pm file. I'm investigating
my httpd.conf file and the includes and looking at options there. It's
those instructions that are supposed to direct traffic to the proper
path.
Any thoughts that help me get that traffic redirected would be helpful
Bernard Shiundu wrote:
On Sun, 2007-03-04 at 14:50 -0900, Dan Foote - DTS wrote:
Here's what I know now. If I move the
Context.pm file in the original installation to a new name, like
Context.pm.orig, the error changes to a "Can't locate C4/Context.pm"
error. This tells me that the installation is not looking at the
correct path to the new installation. It doesn't appear that the SetEnv
and/or ScriiptAlias functions in my httpd include file for the second
installation are being used.
Regardless of what I've done, my second installation wants to use the
first installations koha.conf file. Once again, that four letter word
comes to mind: HELP!
Dan Foote
In addition to
In your httpd.conf
For the second Koha do you have SetEnv KOHA_CONF "/etc/koha-2.conf"
Instead of SetEnv KOHA_CONF "/etc/koha.conf"
Chris
also change the line "use constant CONFIG_FNAME => "/etc/koha.conf";
(line 97 I think) in context.pm for the second install to read the path
to your alternate Koha.conf.
And SetEnv PERL5LIB in httpd.conf for the second instance should also
point to "/path to koha2/intranet/modules"
Bernard
Dan Foote - DTS wrote:
Chris,
Here's what I get in the error logs (either Koha or Opac):
read_config_file(/etc/koha.conf) returned undef at
/usr/lib/perl5/5.8.7/C4/Context.pm line 229.
This is after I have the following in the httpd include file:
SetEnv KOHA_CONF /etc/koha-2.conf
And my export of:
export KOHA_CONF=/etc/koha-httpd-2.conf
With my original post, I'd SetEnv to KOHA_2_CONF and added that to the
Context.pm file for that site with the koha-2.conf path. I even went as
far as changing the "use C4:Context ("/etc/koha-2.conf"); " statement
into the *.pm files of modules/C4.
I've now reverted to what you've suggested and I still get the above
error that points to the /etc/koha.conf file of the first installation.
*Dan Foote* *
* <http://www.dantech-services.com/>
Chris Cormack wrote:
On Sat, Mar 03, 2007 at 05:37:31PM
-0900, Dan Foote - DTS said:
Can somebody please give me some
information on how to go about putting
more than one Koha site on the same server? <br>
<br>
I do have an installation up and running. I created a second
installation using different ports for both the intranet and opac
sides. Two config files for each site have also been created with
different names, appropriate paths, db info, permissions, etc. Web
server listens and responds on the assigned ports. <br>
<br>
I can watch both the koha and opac error logs and see where I fail,
which always appears to be in relation to C4::Context. With
this, I
reviewed the Context.pm file and set the "use constant CONFIG_FNAME
=> "/etc/koha.conf";" statement to "use constant CONFIG_FNAME
=>
"/etc/koha-2.conf";" (the name of my second config file). <br>
In your httpd.conf
For the second Koha do you have SetEnv KOHA_CONF "/etc/koha-2.conf"
Instead of SetEnv KOHA_CONF "/etc/koha.conf"
Chris
_______________________________________________
Koha mailing list
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha