On 03/15/2012 11:31 AM, julian_grunn...@tdwh.co.uk wrote:
> Anyone ... thought I'd go back to this. Does anyone have any ideas why I
> would get the following in the Nagios logs:
>
> nagios-03-10-2012-00.log:[1331336760] Warning: Check of service 'DEAL
> SERVER SERVICE TCP 4099' on host 'TDUKUBS01' could not be rescheduled
> properly. Scheduling check for next week...
> nagios-03-10-2012-00.log:[1331336760] Warning: Check of service 'DEAL
> SERVER SERVICE TCP 4099' on host 'TDUKUBS02' could not be rescheduled
> properly. Scheduling check for next week...
>
> As mentioed below, I've checked the config multiple times, I run 1100+
> service checks across 100+ hosts and just these two are causing a problem
> - they differ in that they have specific time periods defined - all
> detailed below. I've checked the various reports that NTP is at fault but
> it made no difference at all.
>
>> 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
>> }
>>
This timeperiod isn't valid. FROM 23:46 TO 20:30 on the same date,
there is no time for any checks to be executed in.
00:00-20:30,23:46-00:00
should work better, unless you meant "20:30-23:46", but I guess you
wouldn't have screwed it up if that's what you intended.
hth
--
Andreas Ericsson andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Nagios-users mailing list
Nagios-users@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
