<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.3354" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV>I've tried to do a fair bit of searching of the various mailing lists and messageboards and not come across anyone reporting a similar error (or trying such a thing!).. </DIV>
<DIV> </DIV>
<DIV>Nagios Version: 3.0.3</DIV>
<DIV>ndoutils: 1.4b7</DIV>
<DIV> </DIV>
<DIV>I am trying to use both 'nagvis' and the NPC addon for cacti with the same Nagios installation.</DIV>
<DIV> </DIV>
<DIV>NPC implements the ndo database tables itself within the Cacti database, and as such, the 'best' way to run these two addons side-by-side appears to be to run two separate instances of the broker_module ndomod</DIV>
<DIV> </DIV>
<DIV>This appears to be supported by the comments in the ndomod sample cfg files by simply adding a second entry in nagios.cfg eg:</DIV>
<DIV> </DIV>
<DIV>broker_module=/data01/nagios/bin/ndomod-3x.o config_file=/data01/nagios/etc/ndomod_npc.cfg<BR>broker_module=/data01/nagios/bin/ndomod-3x.o config_file=/data01/nagios/etc/ndomod.cfg</DIV>
<DIV> </DIV>
<DIV>I have then configured the two ndomod processes to bind to separate sockets and use distinct filenames in all instances (config below). </DIV>
<DIV> </DIV>
<DIV>The outcome of this is both ndomod objects are initialized by Nagios (as seen in the nagios.log file), however, the first broker_module entry is the only one to actually start outputting data from Nagios to it's socket/TCP port. The second module outputs some startup information and then just sits there with no Nagios data being output. </DIV>
<DIV> </DIV>
<DIV>I've tried using both TCP and unix sockets, and also set both ndomod processes to dump to a file to debug further, and the behaviour is consistent. </DIV>
<DIV> </DIV>
<DIV>If i reverse the broker_module lines, the first module (and thus, the first application) is the one that works, so i'm confident my configurations are correct.</DIV>
<DIV> </DIV>
<DIV>I'm suspecting this could be a Nagios bug in how it feeds data to the modules. I havent tried this on earlier versions, but I do have a v3.0.1 installation on an older server that I will try to test on to see it it's somehow a regression.</DIV>
<DIV> </DIV>
<DIV>I have also tried adding a 3rd instance of broker_module and still only the first instance is the one that processes any Nagios data.. </DIV>
<DIV> </DIV>
<DIV>Has anyone tried this or does anyone have any input as to how to proceed? Happy to do further debugging.. </DIV>
<DIV> </DIV>
<DIV>ndomod.cfg:</DIV>
<DIV> </DIV>
<DIV>instance_name=nagiostest<BR>output_type=unixsocket<BR>output=/data01/nagios/var/ndo.sock<BR>output_buffer_items=5000<BR>buffer_file=/data01/nagios/var/ndomod.tmp<BR>file_rotation_interval=14400<BR>file_rotation_command=rotate_ndo_log<BR>file_rotation_timeout=60<BR>reconnect_interval=15<BR>reconnect_warning_interval=15<BR>data_processing_options=-1<BR>config_output_options=2<BR></DIV>
<DIV>ndomod_npc.cfg:</DIV>
<DIV> </DIV>
<DIV>instance_name=npc<BR>output_type=unixsocket<BR>output=/data01/nagios/var/ndo_npc.sock<BR>output_buffer_items=5000<BR>buffer_file=/data01/nagios/var/ndomod_npc.tmp<BR>file_rotation_interval=14400<BR>file_rotation_command=rotate_ndo_log<BR>file_rotation_timeout=60<BR>reconnect_interval=15<BR>reconnect_warning_interval=15<BR>data_processing_options=-1<BR>config_output_options=2<BR></DIV>
<DIV>Cheers</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>
<DIV>Alastair Cousins</DIV>
<DIV>Broadcast IT Systems Engineer</DIV>
<DIV>Network Ten Pty Ltd</DIV>
<DIV>Main: +61-2-9650-1010</DIV>
<DIV>Direct: +61-2-9650-1151</DIV></DIV><p style="color:#444444;font-family:arial;font-size:9px;font-weight:regular">
Network Ten Pty Ltd ABN 91 052 515 250
</p>
<p style="color:#444444;font-family:arial;font-size:9px;font-weight:regular;">
<u>Network Ten Disclaimer</u><br>
This e-mail (including all attachments) is intended solely for the named
addressee. If you receive it in error, please let us know by reply e-mail,
delete it from your system and destroy the copies. This e-mail is also
subject to copyright. No part of it should be reproduced, adapted or
transmitted without the written consent of the copyright owner. E-mails
may be interfered with, may contain computer viruses or other defects and
may not be successfully replicated on other systems. We give no warranties
in relation to these matters. If you have any doubts about the authenticity
of an e-mail purportedly sent by us, please contact us immediately.
</p>
</BODY></HTML>