Issues with TimePeriod Exclusions

[tbmay]

Hi,

We're running

2014R2.5 on CentOS 6.6 on the metal.

When I first set these exclusions, probably almost a year ago, they worked. At some point, presumable because of updates, they stopped and we're getting notifications during those hours we don't want them.

Could you take a look at the screenshots and offer some insight? I had to put them in a zip because the board wouldn't let me upload 4 pics.

Best regards,

[tgriep]

Can you post the Contacts and/or the Contact Groups that are assigned to that service check?
Do they have another timeperiod assigned to them?

[tbmay]

Thank you.

It's xi_contactgroup_all...and all contact's. Each contact has the default settings.

In my case it's tbmay_notification_settings. Others are the same because I made no changes to the defaults.

[tgriep]

I just found that the Time Exclusion may not be working like we think and it may be a bug that needs to be fixed.

One way to work around this is setup the Sunday time period for the Windows Servers as below to exclude those times.
Set the Sunday time period as follows

Code: Select all

00:00-02:54, 06:31-13:24, 15:00-24:00

[questrad]

That is bug in Nagios Core:
http://tracker.nagios.org/view.php?id=57

And how I understand - dont know when it will be fixed

[scottwilkerson]

Actually, the images show me that this comes down to precedence, and your exclusions are the same precedence and will not be used
http://nagios.sourceforge.net/docs/nagi ... riods.html

You exclude period would have to have a greater precedence than the Windows Servers

the good news in your example, you could simple remove the exclude, and change your sunday definition to the following

Code: Select all

00:00-2:35,06:30-13:25,15:00-24:00

to have the same effect

[tbmay]

Appreciate it. Are spaces needed between the commas?

[abrist]

Not necessary.

[tbmay]

Thanks. Regarding the precedence issue, this worked for quite awhile. It stopped working a few updates ago. Unfortunately, a lot was going on and getting to the bottom of it wasn't a priority, but it definitely worked when I first did it.

Thanks again. You can close the thread unless there's more relevant information.