Re: [Nagios-devel] Check becomes unplanned
Posted: Tue Sep 09, 2008 10:55 am
Please line-wrap your emails, or ask your MUA to do it for you.
Bernd Arnold wrote:
> Hi everyone,
>
> I don't know whether this is a bug or not. And maybe you'll never be affected by this. I believe this only happens when you are using time periods for service (or host) checks and an external program corrects the time backwards. The service check will no longer be executed. This happened in our environment three times already. The bad thing: you never realize that there is an unplanned service. The service state resides at the last check result.
>
> We're having service checks only occurring nightly. During the day, the time was corrected by ntp. Nagios realized the time change (see message below). The next check time is corrected for these services, but in the evening, when the check should occur, the service becomes unplanned. The service check stays unplanned until the nagios configuration is reloaded or the service is re-scheduled manually.
>
> Did anyone experience this behavior already? Please let me know if you need further information.
>
Given the rather huge work in the scheduling queue management
recently, I wouldn't be the slightest surprised if there are
some undiscovered bugs in there right now.
To alleviate your issue, you should be running an ntp daemon
on the Nagios server which slews the clock into its right
time rather than sets it (slew = make it go slightly faster
or slower until it matches the correct time). Are you running
ntpdate via a cronjob or something?
I'm not sure how one would go about debugging this, as the
time required to run a single test is prohibitive for rapid
repeated testing.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Bernd Arnold wrote:
> Hi everyone,
>
> I don't know whether this is a bug or not. And maybe you'll never be affected by this. I believe this only happens when you are using time periods for service (or host) checks and an external program corrects the time backwards. The service check will no longer be executed. This happened in our environment three times already. The bad thing: you never realize that there is an unplanned service. The service state resides at the last check result.
>
> We're having service checks only occurring nightly. During the day, the time was corrected by ntp. Nagios realized the time change (see message below). The next check time is corrected for these services, but in the evening, when the check should occur, the service becomes unplanned. The service check stays unplanned until the nagios configuration is reloaded or the service is re-scheduled manually.
>
> Did anyone experience this behavior already? Please let me know if you need further information.
>
Given the rather huge work in the scheduling queue management
recently, I wouldn't be the slightest surprised if there are
some undiscovered bugs in there right now.
To alleviate your issue, you should be running an ntp daemon
on the Nagios server which slews the clock into its right
time rather than sets it (slew = make it go slightly faster
or slower until it matches the correct time). Are you running
ntpdate via a cronjob or something?
I'm not sure how one would go about debugging this, as the
time required to run a single test is prohibitive for rapid
repeated testing.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]