Problems with nagios remembering things

Mikel Bauer mikel at bridgeband.net
Thu Jun 12 23:26:40 CEST 2003


I seem to be having a problem disabling active checks on services when 
migrating from active checks on a single host to a distributed system.

The original master server will still be doing _some_ active checks, so 
I can't just disable it globally, but have changed the 
"active_checks_enabled" to 0 in the template for the services in 
question, and "passive_checks_enabled" to 1.

The problem is, it's still doing active checks, and refuses to believe 
that they are disabled for the services in question.  It accepts passive 
checks just fine, but it still for some odd reason, goes out and does 
it's own active check as well.  The only way I've found to get this to 
update, is to completely wipe the history and status of nagios, and 
start fresh.

Nagios seems to (unless I'm missing an obvious step) "cache" the 
previous setup of an existing service, and not let this be changed via 
the config files.

I have the same problem with notifications.  If I originally have 
notifications enabled for a host, does this happily for a time, then I 
go and disable notifications in the service and hosts files, it still 
thinks that notifications are enabled, until I force an external command 
for each specific host/service, or wipe the status/history of nagios.

Maybe I'm smokin something, but that's what's happening.

I don't want to wipe the status/history of nagios during my migration to 
a distributed system, as I use the history of the hosts quite often.

Thoughts are appreciated,
-- 
Mikel Bauer



-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
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





More information about the Users mailing list