Notification blackout ignored

[Martin, Jeremy]

Hi,

Some of our older servers restart their web server software every day
early in the morning. I am trying to set up an exclude in the timeperiod
so we don't get pages/emails every day when the servers reset. 

For example one of our servers "web03" resets around 4:10 am, so I'm
trying to disable notifications just from 4:00 - 4:30 AM. 30 minutes is
a bit overkill so I might narrow it down later on, but I'm just trying
to get it to work first. 

Here's the timeperiod I have set up:

define timeperiod {
timeperiod_name                web03
alias                          WEB03
sunday                         00:00-04:00,04:30-24:00
monday                         00:00-04:00,04:30-24:00
tuesday                        00:00-04:00,04:30-24:00
wednesday                      00:00-04:00,04:30-24:00
thursday                       00:00-04:00,04:30-24:00
friday                         00:00-04:00,04:30-24:00
saturday                       00:00-04:00,04:30-24:00
}

For each service for web03 in my services.cfg file, first I am
inheriting a generic-tcp definition which is using the 24x7
notification_period by default. Then I try to override the default
notification_period with my custom one:

define service {
use                            generic-tcp
host_name                      web03
service_description            HTTP-QA
check_command                  check_site!/!whatever
notification_period            web03
}

Also in my hosts.cfg file I have a similar set up - inheriting a generic
host template and then trying to override the notification_period to be
web03 instead of 24x7.

Unfortunately I'm still getting warnings during the 4:00 - 4:30 AM
"blackout" zone... a "Host DOWN" and "Host UP" warning. At first I had
the notification_period set up in the services.cfg only so I figured
surely once I added it to hosts.cfg it would work, but it doesn't seem
to be working.

So far it has only been host up / host down messages that have got
through, not actual service up/down messages. I'm halfway tempted to use
"notification_options n" for the host and only be notified about
services, but that's probably not the best way to do things.

Nagios is giving me 0 warnings/errors when I test my config files so I'm
not sure why it seems to be ignoring my notification_period in my hosts
file. 

I also thought about maybe setting the check_period to my custom
timeperiod as well but I'd prefer to have Nagios checking it 24/7, to
keep accurate availability logs, and just disable the warnings, not the
checks. Though if this won't work any other way I could change the
check_period too if I had to. 

Hopefully someone can spot what I'm doing wrong! 

Thanks, and best wishes,
Jeremy 



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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