Nagios cluster

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Steve Shipway
> Sent: Monday, November 20, 2006 5:10 PM
> To: trevor obba
> Cc: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Nagios cluster
> 
> > I would also like both of my Nagios servers (server A
> > and server B) to monitor clients but only one nagios sever
> > will send out
> > notifications at a time.  If server A
> > goes down, server B take over the sending notification. And
> > if server B goes down
> > take over sending notification.
> 
> How about this - on server B, have the global notifications enabled
set
> to no.  Then you add an extra check on server B that tests for server
A
> being properly up.  This check has an Event Handler that edits the
> nagios.cfg to set the global notify flag to yes and restart Nagios.
> Have a similar event handler to do the same in reverse when the server
A
> reappears.

There are external commands that you can send to the command pipe to
enable/disable host and service notifications from the eventhandler.
That's how I'd approach this particular task instead of editing
nagios.cfg and reloading. Enable/disable_host_notifications,
enable/disable_svc_notifications.

http://www.nagios.org/developerinfo/externalcommands/commandlist.php?cat
egory_id=4&version_id=7&btnSubmit=Update

--
Marc

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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