Next possible notification time bug

Chung, Jeff Jeff.Chung at sig.com
Tue Nov 16 21:44:22 CET 2010


Hi,
            Here is the problem I'm trying to solve.  We have services that have a set maintenance window, for example every Tuesday from 13:30 to 14:00.  So to stop Nagios from sending notifications during this maintenance window I have created a time period that excludes "tuesday 13:30-14:00" and use it as the notification_period for the service.  When testing this it seems like Nagios isn't correctly picking the next available time to send notifications out.  I have configured a service called "TEST_SERVICE2" to return CRITICAL status starting at 13:57:28 (which is during the maintenance window).  In Nagios' debug log it says "Next possible notification time: Wed Nov 17 00:00:00 2010", but I think the next possible time should be Nov 16 14:00 or soon after.  Anyone else came across this issue?

Thanks in advance!


Here are my configurations.

define timeperiod{
        name            24x7
        timeperiod_name 24x7
        alias           24 Hours A Day, 7 Days A Week
        sunday          00:00-24:00
        monday          00:00-24:00
        tuesday         00:00-24:00
        wednesday       00:00-24:00
        thursday        00:00-24:00
        friday          00:00-24:00
        saturday        00:00-24:00
}


# 'test-downtime' timeperiod definition
define timeperiod{
        name            test-downtime
        timeperiod_name test-downtime
        alias           test downtime
        tuesday         13:30-14:00
}

# 'test' timeperiod definition
define timeperiod{
        name            test
        timeperiod_name test
        alias           test
        use             24x7
        exclude         test-downtime
}


define service{
        host_name                       dsmgtbal800
        service_description             TEST_SERVICE2
        check_command                   check_test
        contacts                        chung
        contact_groups                  null
        active_checks_enabled           1
        passive_checks_enabled          1
        parallelize_check               1
        obsess_over_service             1
        check_freshness                 0
        notifications_enabled           1
        event_handler_enabled           1
        flap_detection_enabled          0
        failure_prediction_enabled      1
        process_perf_data               1
        retain_status_information       1
        retain_nonstatus_information    1
        is_volatile                     0
        check_period                    24x7
        max_check_attempts              1
        normal_check_interval           1
        retry_check_interval            1
        notification_options            u,c,r,s
        notification_interval           15
        notification_period             test
}


Here is the output from Nagios' debug log.
Tue Nov 16 13:57:28 2010 [1289933848.065697] [032.0] [pid=4359] ** Service Notification Attempt ** Host: 'dsmgtbal800', Service: 'TEST_SERVICE2', Type
: 0, Options: 0, Current State: 2, Last Notification: Wed Dec 31 19:00:00 1969
Tue Nov 16 13:57:28 2010 [1289933848.065732] [032.1] [pid=4359] This service shouldn't have notifications sent out at this time.
Tue Nov 16 13:57:28 2010 [1289933848.065747] [032.1] [pid=4359] Next possible notification time: Wed Nov 17 00:00:00 2010
Tue Nov 16 13:57:28 2010 [1289933848.065775] [032.0] [pid=4359] Notification viability test failed.  No notification will be sent out.

Tue Nov 16 13:58:28 2010 [1289933908.196211] [032.0] [pid=4359] ** Service Notification Attempt ** Host: 'dsmgtbal800', Service: 'TEST_SERVICE2', Type: 0, Options: 0, Current State: 2, Last Notification: Wed Dec 31 19:00:00 1969
Tue Nov 16 13:58:28 2010 [1289933908.196248] [032.1] [pid=4359] This service shouldn't have notifications sent out at this time.
Tue Nov 16 13:58:28 2010 [1289933908.196262] [032.1] [pid=4359] Next possible notification time: Wed Nov 17 00:00:00 2010
Tue Nov 16 13:58:28 2010 [1289933908.196269] [032.0] [pid=4359] Notification viability test failed.  No notification will be sent out.

Tue Nov 16 13:59:28 2010 [1289933968.114925] [032.0] [pid=4359] ** Service Notification Attempt ** Host: 'dsmgtbal800', Service: 'TEST_SERVICE2', Type: 0, Options: 0, Current State: 2, Last Notification: Wed Dec 31 19:00:00 1969
Tue Nov 16 13:59:28 2010 [1289933968.114970] [032.1] [pid=4359] This service shouldn't have notifications sent out at this time.
Tue Nov 16 13:59:28 2010 [1289933968.114985] [032.1] [pid=4359] Next possible notification time: Wed Nov 17 00:00:00 2010
Tue Nov 16 13:59:28 2010 [1289933968.114991] [032.0] [pid=4359] Notification viability test failed.  No notification will be sent out.

Tue Nov 16 14:00:28 2010 [1289934028.020298] [032.0] [pid=4359] ** Service Notification Attempt ** Host: 'dsmgtbal800', Service: 'TEST_SERVICE2', Type: 0, Options: 0, Current State: 2, Last Notification: Wed Dec 31 19:00:00 1969
Tue Nov 16 14:00:28 2010 [1289934028.020343] [032.1] [pid=4359] We haven't waited long enough to re-notify contacts about this service.
Tue Nov 16 14:00:28 2010 [1289934028.020353] [032.1] [pid=4359] Next valid notification time: Wed Nov 17 00:00:00 2010
Tue Nov 16 14:00:28 2010 [1289934028.020359] [032.0] [pid=4359] Notification viability test failed.  No notification will be sent out.

Tue Nov 16 14:01:28 2010 [1289934088.188354] [032.0] [pid=4359] ** Service Notification Attempt ** Host: 'dsmgtbal800', Service: 'TEST_SERVICE2', Type: 0, Options: 0, Current State: 2, Last Notification: Wed Dec 31 19:00:00 1969
Tue Nov 16 14:01:28 2010 [1289934088.188397] [032.1] [pid=4359] We haven't waited long enough to re-notify contacts about this service.
Tue Nov 16 14:01:28 2010 [1289934088.188407] [032.1] [pid=4359] Next valid notification time: Wed Nov 17 00:00:00 2010
Tue Nov 16 14:01:28 2010 [1289934088.188414] [032.0] [pid=4359] Notification viability test failed.  No notification will be sent out.




________________________________
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20101116/a97d7e39/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
-------------- next part --------------
_______________________________________________
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


More information about the Users mailing list