I'm administering multiple servers in a distributed/failover environment - running Nagios v1.2. Recently I noticed that one of the servers was performing active checks of some services where it should have been receiving passive checks from the Nagios server local to the service. With some debugging and hair pulling I discovered that some of the services have obsess_over_service=0 in the status.sav file on the "local" Nagios server. These services are configured for obsession, which is confirmed by config.cgi, but they aren't being obsessed over because of the state retention values.
Firstly, what is the best way to correct this? As far as I can tell there is no way to fix this through the web interface. My next guess would be to shutdown Nagios, modify the relevant values in status.sav, and restart. Any other ideas? I have a LOT of services I will need to check, so I would probably need to figure out some way to script it if I need to go this way. Otherwise, is there some way to just reset the value to whatever was configured? I don't want to lose all the status information, so deleting everything would not be a good option. Secondly, how does it get into this state? There are services for the same host that were added at the same time, yet have differing values in the state retention. I would prefer to avoid this in the future - our servers are busy enough without each server having to perform it's own checks. Thanks for any input, Owen ------------------------------------------------------------------------- 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 [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
