nagios reload status retention bug

[Jason Lancaster]

Note: This is not a request for help, I'm just hoping my experiences can 
help someone else in the future.

Periodically, during a Nagios reload, "odd flapping issues" may occur. 
The flapping issues only affect new passive services previously not in 
the status retention file. A bug causes these services to become active 
services, causing the specified check_command (stale_check) to be 
executed at the check_interval in addition to any passive submission you 
may be making.

This problem will remain until the status.sav file is cleared (and 
Nagios restarted)
/etc/rc.d/init.d/nagios stop
echo "" > /usr/local/nagios/var/status.sav
/etc/rc.d/init.d/nagios start

I have not tested (I can't duplicate this problem on purpose), but I 
believe a reload will also work.
echo "" > /usr/local/nagios/var/status.sav
/etc/rc.d/init.d/nagios/reload

This problem is very easy to identify (you'll see active services in 
your web-interface or status.log that are indeed not active) and the 
posted resolutions are fast and virtually unnoticeable. The only side 
affect for the first solution is that email notifications for any down 
service will be redelivered and some data may show up as pending until 
the first service check has been performed.

Jason



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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