Using Nagios 1.0a7 sometimes the scheduled downtimes are disappearing or
will not be accepted although the timerange of the downtime is not
finished. I often recognized this behaviour after sending a reload to
the main nagios process.
Here is an excerpt of the nagios log file which demonstrates the problem:
-> schedule downtime for 6 hours on us02ssp
[1020843163] EXTERNAL COMMAND:
SCHEDULE_HOST_DOWNTIME;us02ssp;1020843105;1020864705;1;21600;Marcus
Hildenbrand;disk reorg
-> nagios accepts downtime
[1020843163] HOST DOWNTIME ALERT: us02ssp;STARTED; Host has entered a
period of scheduled downtime
-> config reload
[1020846304] Caught SIGHUP, restarting...
[1020846306] Nagios 1.0a7 starting... (PID=5411)
-> for this host no downtime was scheduled, maybe this is a part of the
problem
[1020846308] HOST DOWNTIME ALERT: uw1039;STARTED; Host has entered a
period of scheduled downtime
[1020846308] HOST DOWNTIME ALERT: uw1039;STOPPED; Host has exited from a
period of scheduled downtime
-> downtime disappeared and notification was send
[1020846796] SERVICE ALERT: us02ssp;fs /;CRITICAL;HARD;1;Couldn't
connect to us02ssp.wdf.sap-ag.de:5666 : Connection refused
[1020846796] SERVICE NOTIFICATION: d022099;us02ssp;fs
/;CRITICAL;notify-by-email;Couldn't connect to
us02ssp.wdf.sap-ag.de:5666 : Connection refused
-> tried again to schedule a downtime but this was never accepted
[1020846891] EXTERNAL COMMAND:
SCHEDULE_HOST_DOWNTIME;us02ssp;1020846867;1020854067;1;7200;Marcus
Hildenbrand;disk reorg
Does anyone have the same problem? Is this maybe a bug?
Thanks Marcus
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: Marcus.Hildenbrand@sap.com