Hi all, I currently have Nagios 2.10 installed on a couple of machines, one of which is configured as a master and the other as a slave.
I have a script running on the slave which rsync's up the configs from the master and performs health checks of the master to see that it is running (and if it is not then it enables service checks/notifications on the slave until such time as it detects that the master is back up and running). I also use nsca to pass passive checks to the slave to ensure that it has up to date information about services. The slave does not perform any active service checks, nor are notifications enabled unless the master is down. I do however still have one problem and that is that the slave has no way of knowing when we're ack'ed a critical, scheduled downtime, disabled/enabled notfications/event handlers/checks for a service/host on the master. What this means is that if we schedule downtime on a host, then the master goes down, the slave starts bitching about the host that is down (because it does not know that it's in downtime). A similar problem occurs if we disable an event handler on the master, because unless the slave also knows to disable the event handler it will fire it (regardless of whether or not it is active) as soon as the passive check result returns a critical. At present I am getting round this by tailing the nagios log file through a perl script that looks for specific 'EXTERNAL COMMAND' entries and then flushes those through to the slave by ssh'ing to the slave and writing the command string to the nagios pipe file on the slave. Is there a better way of doing this ? -- bright blessings, Mark ------------------------------------------------------------------------- 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 [email protected] 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
