Diego,

When looking at Kernel/System/Log.pm and the files under Kernel/System/Log I noticed the following:

Whether you choose for the use for a logfile or syslogd, OTRS will ALSO use IPC queues for storing the latest error messages. These are the messages that you'll see via the OTRS > Admin > System Messages section of the web frontend.

In the IPC message it uses the SystemID as a part of the key. That should provide a separate queue per instance, resolving your issues. But, after you specified the new SystemIDs, did you restart OTRS? I guess that will be needed in order to initialize the new IPC queues.

KR,
--
Michiel Beijen
Software Consultant
+31 6 - 457 42 418
Bee Free IT + http://beefreeit.nl


On Mon, Apr 27, 2009 at 09:10, <diego.giardinetto@zephirworks.com> wrote:
Hi all,
some days ago I posted a similar request having no answer. I try to explain in a better way my problem, hoping in such an answer. I have three otrs instances, one each unix jail. Log messages are stored correctly, separated, in three different logfiles, one each instance. But... the buffered log messages (OTRS uses system V shared memory primitives) are shown in each instance: also if the message is owned by the instance A, it's shown into log viewer otrs page of the instance B and C.

I changed SystemID variable in each instance; I set OTRS to use its own logfile instead of syslogd. Trying disabling system V communication between jails and host, OTRS stop working.

Could you help me?
Thx,
Diego

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


---------------------------------------------------------------------
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/