Problem running multiple nagios instances on one server

[David Wallis]

I searched for similar threads, but came up empty, sorry if this is a repeat question,

I want to run multiple nagios instances on a single server. I'm running nagios 3.0rc3 and nagios-plugins 1.4.11 on Solaris 9.

The nagios software is installed in /usr/local/nagios, and is available from there to the nagios server and all monitored clients.

I have a separate local directory for each nagios instance (e.g, /local/nagios1, /local/nagios2, etc) that contains the config files, logs and log archives, external command file, etc. (everything in nagios/var, nagios/etc and nagios/share)

Testing each config file, nagios recognizes the correct number of hosts and servers, and returns no errors. Each nagios instance starts up without errors, and runs fine when it's the only instance running. However, when more than one is running, the log files indicate that each instance is receiving some check results from hosts/services on another instance... I see messages like this in /local/nagios2/var/nagios.log, when the host "hadar" is configured in the /local/nagios1/etc/hosts.cfg config file:

[1204870487] Warning: Check result queue contained results for host 'hadar', but the host could not be found! Perhaps
you forgot to define the host in your config files?

I've checked the nagios.cfg files for both instances, and each refers properly to files in it's own path. What am I missing here?


- David Wallis (dbwallis)

-----------------------
The mailing list archive is found here:
http://www.nagiosexchange.org/nagios-users.34.0.html
				

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null