Forcing renotification for existing states

[Tedman Eng]

> From: Robert King [mailto:robert.king at ingenta.com]
> 
> Hello all,
> 
> We have a high availability nagios setup, with two hosts in different 
> data centers. Our secondary nagios installation by default runs with 
> notifications disabled, and enables them when it senses the 
> primary has 
> gone down, using the example event handler scripts 
> distributed with Nagios.
> 
> This all works great, however... If we lose our primary, and 
> happen to 
> lose other hosts/services at the same time, there is a possibility of 
> notifications not being sent! Suppose the secondary Nagios 
> host decides 
> that a service is in a non-OK state, and does not notify since it's 
> disabled, at this same time, we lose the primary server, 
> which has not 
> already sent a notification, because it has not checked this service 
> yet. Notifications then get enabled on the secondary. Any 
> state changes 
> that occur after that get notified, but this non-OK service that was 
> detected during that short window slips through the cracks...
> 
> Does this make sense?

Can you leave notifications enabled on the secondary server all the time (in
nagios), and have the notifications "disabled" instead at the OS level (ie.
toggle or flag your notification script to printf to a log file or /dev/null
when inactive, printf to /bin/mail when active?


_______________________________________________
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