<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
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.<br>
<br>
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!<br>
<div class="moz-signature">
<meta http-equiv="CONTENT-TYPE" content="text/html; ">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 2.0 (Win32)">
<meta name="CREATED" content="20061002;17015100">
<meta name="CHANGEDBY" content="Dan Foote">
<meta name="CHANGED" content="20061220;1243142">
<style>
        <!--
                @page { size: 8.5in 11in; margin: 0.79in }
        -->
        </style>
<p align="left"><font color="#000080"><b><font face="Agency FB">Dan
Foote</font></b> </font><font color="#000080"><b><font face="Agency FB"><br>
</font></b></font></p>
</div>
<br>
<br>
Dan Foote - DTS wrote:
<blockquote cite="mid:45EB1974.7030000@dantech-services.com" type="cite">Chris,
<br>
Here's what I get in the error logs (either Koha or Opac):
<br>
read_config_file(/etc/koha.conf) returned undef at
/usr/lib/perl5/5.8.7/C4/Context.pm line 229.
<br>
<br>
This is after I have the following in the httpd include file:
<br>
SetEnv KOHA_CONF /etc/koha-2.conf
<br>
<br>
And my export of:
<br>
export KOHA_CONF=/etc/koha-httpd-2.conf
<br>
<br>
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.
<br>
<br>
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.
<br>
*Dan Foote* *
<br>
* <a class="moz-txt-link-rfc2396E" href="http://www.dantech-services.com/"><http://www.dantech-services.com/></a>
<br>
<br>
<br>
<br>
Chris Cormack wrote:
<br>
<blockquote type="cite">On Sat, Mar 03, 2007 at 05:37:31PM -0900, Dan
Foote - DTS said:
<br>
<br>
<blockquote type="cite">Can somebody please give me some
information on how to go about putting
<br>
more than one Koha site on the same server? <br>
<br>
<br>
<br>
I do have an installation up and running. I created a second
<br>
installation using different ports for both the intranet and opac
<br>
sides. Two config files for each site have also been created with
<br>
different names, appropriate paths, db info, permissions, etc. Web
<br>
server listens and responds on the assigned ports. <br>
<br>
<br>
<br>
I can watch both the koha and opac error logs and see where I fail,
<br>
which always appears to be in relation to C4::Context.&nbsp; With
this, I
<br>
reviewed the Context.pm file and set the "use constant CONFIG_FNAME
<br>
=&gt; "/etc/koha.conf";" statement to "use constant CONFIG_FNAME
=&gt;
<br>
"/etc/koha-2.conf";" (the name of my second config file). <br>
<br>
</blockquote>
<br>
In your httpd.conf
<br>
<br>
For the second Koha do you have SetEnv KOHA_CONF "/etc/koha-2.conf"
<br>
<br>
Instead of SetEnv KOHA_CONF "/etc/koha.conf"
<br>
<br>
Chris
<br>
</blockquote>
_______________________________________________
<br>
Koha mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.katipo.co.nz/mailman/listinfo/koha">http://lists.katipo.co.nz/mailman/listinfo/koha</a>
<br>
</blockquote>
</body>
</html>