Hi,
i'm currently trying to setup a multi-installation of OTRS, meaning
two or more instances on the same machine with only one Apache.
The docs tell me that only apache2+mod_perl2 is capable of this (with
mod_perl1 i'd have to setup another webserver) but they don't tell the
exact steps on how to install OTRS in multiple instances.
So i decided to unpack the otrs.tar.gz twice, to /opt/otrs and
/opt/otrs2. I also added these two lines to my httpd.conf:
Include /opt/otrs/scripts/apache2-httpd.include.conf
Include /opt/otrs2/scripts/apache2-httpd.include.conf
As a matter of course i edited several files that contained the
hard-coded path /opt/otrs to point to the new location /opt/otrs2.
I did _NOT_ add a new system-user "otrs2" but i called
bin/SetPermissions.sh with the already existing (from the first
otrs-installation) user "otrs" on both installations.
Ok, so much about the setup. Then i called the installer.pl from my
otrs2 directory and it asked me correctly to create a new database and
stuff... Everything seemed fine until i actually tried to use the new
otrs2-installation:
It doesn't matter whether i call /otrs/index.pl or /otrs2/index.pl, i
only see the tickets of the first installation. Obviously the
otrs2-installation uses the database of the first installation (otrs).
Now you might think "double check the config files, they might point
to the wrong database". I double checked everything and the settings
are in fact okay. I even replaced every "otrs" string in the whole
otrs2-tree by the string "otrs2", but with no success (works, but only
on the first otrs-database).
Interestingly the Database which is being accessed by BOTH
installations changes if i swap the order of the "Include"-lines in
httpd.conf which tells me that the second database is in fact working.
Maybe it's some Perl-module that has the old configuration cached? Or
the second otrs won't even load the modules twice because they already
_are_ loaded? (but with wrong configuration)
Now i did the following:
I commented out the whole