[dev] [Fwd: Re: SPAM Subject: Re: [otrs] Multiple OTRS
installations, same machine]
Matt Linton
mlinton at email.arc.nasa.gov
Tue May 2 11:32:33 CEST 2006
Hello all;
I sent this to the users list but didn't get specific feedback on the
parts of the code I was interested in, so this seems like a more
appropriate channel.
I have two OTRS installations within a single Apache -- one in mod_perl2
and one in plain CGI mode. If I set the SystemIDs too close together,
Log.pm seems to panic.
For instance, if #1 is SystemID 01 and #2 is SystemID 02, then they
conflict on memory space (it appears).
If #1 is SystemID 01 and #2 is SystemID 20, then they do not conflict.
It looks like in Syslog.pm, shmget is using SystemID as a parameter in
grabbing shared memory. Am I reading this right, and can this problem
be duplicated?
The offending line of code seems to be:
75 $Self->{IPCSize} = $Param{ConfigObject}->Get('LogSystemCacheSize
') || 4*1024;
76 # init session data mem (at first a dummy for RH8 workaround)
77 shmget(($Self->{IPCKey}+1), 1, 0777 | 0001000);
78 # init session data mem (the real one)
79 $Self->{Key} = shmget($Self->{IPCKey}, $Self->{IPCSize}, 0777 |
0001000) || die $!;
80 }
81
82 return $Self;
83 }
84
85 =item Log()
It looks like in line 79 the system is grabbing memory segments in part based on the IPCKey (System ID). Am I understanding this code right?
-------------------------------------------------------------
Matt Linton "So, you think there's no money
UNIX/Linux SysAdmin to be made as a philosophy major?
ASANI Solutions, LLC Think again! You're still right."
Christian Schoepplein wrote:
>Hi Matt,
>
>On Fri, Apr 21, 2006 at 11:37:25AM -0700, Matt Linton wrote:
>
>
>>I'd like to allow multiple software groups within our single
>>organization to handle their own "issue reporting" via OTRS. Since I
>>don't want to manage multiple servers, and want them each to have full
>>administrative control over their own FAQ entries, customer users, etc
>>-- I had planned on installing multiple OTRS installations like this:
>>
>>ScriptAlias /otrs1/ /local/otrs1
>>ScriptAlias /otrs2/ /local/otrs2
>>(and so on...)
>>
>>Problem is, I'm running into wierd behaviors with the secondary and
>>other OTRS's. Log.pm seems to use the OTRS ID as a function for
>>grabbing memory for logging. Is that true? If I set my server IDs "1"
>>and "2" then #2 has memory conflicts, but if I set them to "1" and "20"
>>then it seems fine.
>>
>>
>
>You have to use different system IDS for the different OTRS instances:
>
> $Self->{'SystemID'} = ...
>
>I use 3 different OTRS instances (without mod_perl" and it works fine.
>
>
>
>>Has anyone done this before, and does anyone know how to accomplish it
>>better, perhaps?
>>
>>
>
>The way you like to do it is perfect, only take on the different
>SystemIDs and the different aliases in the web server configuration.
>Also do only use mod_perl for one instance.
>
>
>
>>Matt Linton
>>
>>
>
>Ciao,
>Christian
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>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
>Support oder Consulting für Ihr OTRS System?
>=> http://www.otrs.de/
>
_______________________________________________
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
Support oder Consulting für Ihr OTRS System?
=> http://www.otrs.de/
--
-------------------------------------------------------------
Matt Linton "So, you think there's no money
UNIX/Linux SysAdmin to be made as a philosophy major?
ASANI Solutions, LLC Think again! You're still right."
More information about the dev
mailing list