Nagios Support Forum

Posted: **Thu May 15, 2014 11:50 am**

We have a few services that are scheduled for recurring downtime every night, and they seem to be getting scheduled correctly:

Screen Shot 2014-05-15 at 9.47.08 AM.png

However we're still getting alerts during this downtime (example):

Code: Select all

From: "NOX Alerts" 
To: [email protected]
Sent: Thursday, May 15, 2014 3:03:27 AM
Subject: PROBLEM Service Alert - mysqlslave3/MySQL Slave Lag is CRITICAL

***** Nagios XI Alert *****

Nagios has detected a problem with this service.

Notification Type: PROBLEM

Service: MySQL Slave Lag
Host: mysqlslave3
Address: 10.1.2.19
State: CRITICAL
Info:
CRITICAL - Slave is 621 seconds behind master
Date/Time: 2014-05-15 03:03:27

What can we do to fix this?

Posted: **Thu May 15, 2014 4:10 pm**

I believe this was patched long ago, but did you happen to restart or reload nagios core after scheduling those downtimes? Such as via apply config or other such items.

Posted: **Fri May 16, 2014 2:29 am**

Immediately after? I'm not sure... It's been a long time. But I've definitely done those things since setting them up... Should I just re-do them?

Posted: **Fri May 16, 2014 12:27 pm**

Your alert was sent on May 15, 2014 3:03:27 AM, which is outside on the downtime period you are showing for this service...

Code: Select all

Start Time: 05-15-2014 23:55:00
End Time: 05-16-2014 04:25:00

...unless you have:

Code: Select all

Start Time: 05-14-2014 23:55:00
End Time: 05-15-2014 04:25:00

that you are not showing us.

Nagios Support Forum

Recurring/scheduled downtime not working since 2014 upgrade

Recurring/scheduled downtime not working since 2014 upgrade

Re: Recurring/scheduled downtime not working since 2014 upgr

Re: Recurring/scheduled downtime not working since 2014 upgr

Re: Recurring/scheduled downtime not working since 2014 upgr