Time periods seem to be no-ops

[Andreas Ericsson]

Patrick Rutkowski wrote:
> We've defined the following time period for use with a service which we
> know to be down between 9am and 10am every day:
> 
> ========== BEGIN CODE SNIPPET ==========
> define timeperiod{
>          timeperiod_name do_not_notify_bw_9am_10am
>          alias           Every day and time, except 9am-10am
>          sunday          00:00-8:59,10:01-24:00
>          monday          00:00-8:59,10:01-24:00
>          tuesday         00:00-8:59,10:01-24:00
>          wednesday       00:00-8:59,10:01-24:00
>          thursday        00:00-8:59,10:01-24:00
>          friday          00:00-8:59,10:01-24:00
>          saturday        00:00-8:59,10:01-24:00
>          }
> ========== END CODE SNIPPET ==========
> 
> We then applied it to a service like so:
> 
> ========== BEGIN CODE SNIPPET ==========
> define service {
>          host_name                       our-special-host
>          service_description             Check status of MySQL  
> reporting:3307
>          check_command                   check_mysql_service!16105
>          use                             generic-service
>          notification_period             do_not_notify_bw_9am_10am
>          notification_interval           0
>          contact_groups                  company-admins
>          }
> ========== END CODE SNIPPET ==========
> 
> Oddly, the service continues to give us notifications during that time
> interval. We tried setting check_interval instead of
> notification_interval, but still no luck. We also tried setting both
> {notification,check}_interval, but again, no luck.
> 
> To preempt the obvious question, yes, we did restart
> Nagios. Additionally, to ensure that the time period was indeed
> getting attached to the service, we used to GUI page to browse to
> "Configuration" -> "View Config" -> "Object Type: Services" and
> verified that the columns entitled "Check Period" and "Notification
> Period" had "do_not_notify_bw_9am_10am" instead of the usual "24x7".
> 
> Despite all this, we're still getting warnings during this time
> interval.
> 

I take it the system clock on the Nagios server is running correctly?

> As a quick fix, we can use SCHEDULE_SVC_DOWNTIME with
> /var/lib/nagios2/rw/nagios.cmd, which does work; but it definitely
> doesn't feel like a permanent solution.
> 

Make sure you don't have multiple nagios instances running.

Timeperiods clearly work, or hundreds of thousands of people would
have complained on a daily basis. Something else must be going wrong,
but I can't for the life of me think of what.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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