Hi - does anyone know the answer to the following errors I'm getting in the nagios.log for a handful of hosts that have a specific timeperiod for checks set. [Wed Nov 9 23:46:00 2011] Warning: Check of service 'DEAL SERVER SERVICE TCP 4099' on host 'TDUKUBS02' could not be rescheduled properly. Scheduling check for next week... [Wed Nov 9 23:46:00 2011] Warning: Check of service 'DEAL SERVER SERVICE TCP 4099' on host 'TDUKUBS01' could not be rescheduled properly. Scheduling check for next week... Obviously this is causing major issues as checks are just not being carried out as expected, the hosts / services are defined as follows: define host{ use unix_host_template ; Name of host template to use icon_image win40.jpg host_name TDUKUBS01 address 192.168.75.84 alias TDUKUBS01 192.168.75.84 } define service{ use ubs-service hostgroup_name ubsdealservers service_description DEAL SERVER SERVICE TCP 4099 check_command check_ubs!4099 check_period ubs4099hours } define service{ name ubs-service is_volatile 0 max_check_attempts 5 normal_check_interval 1 notification_interval 5 retry_check_interval 1 contact_groups dtns-ooh active_checks_enabled 1 ; Active service checks are enabled passive_checks_enabled 1 ; Passive service checks are enabled/accepted parallelize_check 1 ; Active service checks should be parallelized (disabling this can lead to major performance problems) obsess_over_service 1 ; We should obsess over this service (if necessary) check_freshness 0 ; Default is to NOT check service 'freshness' notifications_enabled 1 ; Service notifications are enabled event_handler_enabled 1 ; Service event handler is enabled flap_detection_enabled 1 ; Flap detection is enabled failure_prediction_enabled 1 ; Failure prediction is enabled process_perf_data 1 ; Process performance data retain_status_information 1 ; Retain status information across program restarts retain_nonstatus_information 1 ; Retain non-status information across program restarts is_volatile 0 ; The service is not volatile register 0 } define timeperiod{ timeperiod_name ubs4099hours alias UBS 4099 Dealserver Monitoring Hours monday 23:46-20:30 tuesday 23:46-20:30 wednesday 23:46-20:30 thursday 23:46-20:30 friday 23:46-20:30 } It all looks ok to me, if I manually re-schedule the check above it will run fine but when it comes to the check being carried out as defined by the timeperiod above again it will not run and then get scheduled for the following week. Any help would be appreciated. Thanks - Julian. Julian Grunnell | Unix Analyst, Infrastructure | TD Waterhouse T: +44 (0) 113 346 2824 | M: +44 (0) 7889 352527 -------------------------------------------------------------------------------- Consider the environment. Please don't print this e-mail unless you really need to. Confidentiality: This email and its attachments are intended for the above named only and may be confidential. If they have come to you in error you must take no action based on them, nor must you copy or show them to anyone; please reply to this email and highlight the error. Viruses: Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure that they are actually virus-free. Brokerage services provided by TD Waterhouse Investor Services (Europe) Limited (a subsidiary of The Toronto-Dominion Bank). Authorised and regulated by the Financial Services Authority (FSA registered number 141282), member of the London Stock Exchange and the PLUS market. Incorporated in England and Wales under registration number 2101863. Registered office: Exchange Court, Duncombe Street, Leeds LS1 4AX. Banking services provided by TD Waterhouse Bank N.V. authorised and regulated by De Nederlandsche Bank and the Financial Services Authority for UK Business (FSA registered number 216791). Incorporated in the Netherlands and registered as a branch in England and Wales under branch registration number BR006780. --------------------------------------------------------------------------------