Nagios Support Forum

Hey Gents,

This is something of a follow up to this old thread: http://support.nagios.com/forum/viewtop ... =16&t=7687

I attempted the suggestion made by Scott but it doesn't look like it has worked. Re-reading the original post I think I might have mis-worded the problem, it actually schedules the downtime but it doesn't actually seem to stop notifications being sent.

The logs of the affected service look like this:

11-24-2012 04:30:00 11-24-2012 05:30:00 0d 1h 0m 0s SERVICE DOWNTIME START Start of scheduled downtime
11-24-2012 05:30:00 11-25-2012 13:00:00 1d 7h 30m 0s SERVICE DOWNTIME END End of scheduled downtime
11-25-2012 13:00:00 11-25-2012 23:27:08 0d 10h 27m 8s+ SERVICE OK (HARD) HTTP OK HTTP/1.1 200 OK - 10355 bytes in 0.071 seconds

The downtime schedule (for today, which is the same as previous):

Entry Time: 11-25-2012 05:01:09
Start Time: 11-26-2012 04:30:00
Entry Time: 11-26-2012 05:30:00
Duration: 0d 1h 0m 0s

The time stamp for the notification:

***** Nagios *****

Notification Type: PROBLEM

Service: xxxxxxxxxx
Host: xxxxxxxxxx
Address: xxxxxxxxxx
State: CRITICAL

Date/Time: Sun Nov 25 04:55:55 EST 2012

I have no idea what to make of this.

The downtime saga... Some of these bugs still persist in XI as we are using 3.4.1 Nagios Core.

There was considerable time spent on these over the last several months and the final results are rolled into Core 3.4.3 due to be released soon.

This will likely make in into XI a couple releases down the road as we need to let 3.4.3 smolder a bit to make sure we didn't introduce new bugs...

scottwilkerson wrote:The downtime saga...

Still friendlier than the "multiple instances of nagios starting" saga at least

Cheers Scott, the problem is only really impacting a handful of users right now so we can probably survive until then.