I tried running with a seperate httpd on another IP address. You still
need to change the hardcoded lib paths in scripts/apache-perl-startup.pl
or you get the /opt/otrs instance.
You may want to add this to the documentation, or better still come up
with a way not to hardcode /opt/otrs in the startup script (relative path?).
Thanks for the help.
- Alan -
Wiktor Wodecki
hehe,
I just run recently on the same problem and commited an update to the otrs documentation regarding multihost. See the cvs version of the doc online for multihosting. http://otrs.org/pages/index.pl?Action=Ext&Site=Docu-CVS/multi-hosting-multi-...
On Fri, Mar 21, 2003 at 12:26:13PM +0200, Alan J. Rothstein wrote:
I'm trying to run two instances of OTRS under one server. The server is running Solaris 8 with Apache 1.3.27 and mod_perl 1.27.
I've installed one in /opt/otrs (1.0.1), the second in /opt/otrs_is (1.0.2). One is using a user called otrs, the second a user called is_issue. I've set up two databases, one called otrs, the second called otrs_is. Each system has unique TicketHook, Database, DatabaseUser, DatabasePW, SystemID in it's Config.pm file.
In the httpd.conf file I have the following:
Perlrequire /opt/otrs/scripts/apache-perl-startup.pl Alias /otrs/ "/opt/otrs/bin/cgi-bin/"
SetHandler perl-script PerlHandler Apache::Registry Options ExecCGI PerlSendHeader On </Location> Perlrequire /opt/otrs_is/scripts/apache-perl-startup.pl Alias /is_issue/ "/opt/otrs_is/bin/cgi-bin/"
SetHandler perl-script PerlHandler Apache::Registry Options ExecCGI PerlSendHeader On </Location> My initial install in /opt/otrs works fine. If I then try to use the second one http:://hostname/is_issue/index.pl I end up getting the the queview for the initial install rather than the login screen for the second. It seems like no matter what I do I end up back at the /opt/otrs install.
One thing I noticed is that the startup script (apache-perl-startup) has the /opt/otrs hard coded in it (lines 10&11). I tried changing this in the /opt/otrs_is instance, but it did not help.
It occured to me that the two startup scripts each try and update perl's lib path (@INC) so that when the script later does the: use Kernel::Config, it will always get whichever Config.pm shows up first in the perl library path. To confirm this, I switched the order of the Perlrequire lines in my httpd.conf. Sure enough, I could only get to the /opt/otrs_is instance.
So, am I doing something wrong? Have I missed something? Anyone out there have two instances of OTRS running under mod_perl?
Thanks in advance for any help.
- Alan -
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
-- Regards,
Wiktor Wodecki
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs