strange behavior - timeperiod problem?

Terry td3201 at yahoo.com
Mon Jul 14 16:02:06 CEST 2003


Hello,

I have defined a service that is to be checked
differently based on the timeperiod.  For some reason,
the service wasnt checked over the weekend.  Here are
the timeperiods involved:
define timeperiod{
        timeperiod_name maintenence
        alias           Maintenence Period
        sunday          01:00-04:15
        monday          01:00-04:15
        tuesday         01:00-04:15
        wednesday       01:00-04:15
        thursday        01:00-04:15
        friday          01:00-04:15
        saturday        01:00-04:15
        }

define timeperiod{
        timeperiod_name nonmaintenence
        alias           Non-Maintenence Period
        sunday          04:15-01:00
        monday          04:15-01:00
        tuesday         04:15-01:00
        wednesday       04:15-01:00
        thursday        04:15-01:00
        friday          04:15-01:00
        saturday        04:15-01:00
        }

Here are the service definitions:
define service{
        use                            
generic-service
        host_name                       cmsws01
        service_description            
SLS-Non-Maintenence
        is_volatile                     0
        check_period                    nonmaintenence
        normal_check_interval           120
        contact_groups                 
warning,critical
        notification_interval           120
        notification_period             nonmaintenence
        notification_options            w,u,c,r
        check_command                   check_ping
        }

define service{
        use                            
generic-service
        host_name                       cmsws01
        service_description            
SLS-Maintenence
        is_volatile                     0
        check_period                    maintenence
        normal_check_interval           120
        contact_groups                 
warning-critical-no-pager
        notification_interval           120
        notification_period             maintenence
        notification_options            w,u,c,r
        check_command                   check_ping
        }

Finally, here is the webpage that shows the service
wasnt checked over the weekend:

Current Status:	OK    
Status Information:	OK. ping is OK.
Current Attempt:	1/3
State Type:	HARD
Last Check Type:	ACTIVE
Last Check Time:	2003-07-11 10:01:16
Status Data Age:	2d 22h 57m 58s
Next Scheduled Active Check:  	N/A
Latency:	< 1 second
Check Duration:	< 1 second
Last State Change:	2003-07-11 08:43:37
Current State Duration:	3d 0h 15m 37s
Last Service Notification:	N/A
Current Notification Number:	0
Is This Service Flapping?	NO  
Percent State Change:	0.00%
In Scheduled Downtime?	NO  
Last Update:	2003-07-14 08:59:01


Notice the last check time, last update, and next
scheduled active check....

thanks for the help!

=====
Terry

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
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