Reproducible bug scheduling second host check following failure
Matthew Richardson
matthew-ln at itconsult.co.uk
Fri Feb 1 18:59:19 CET 2008
>From: Ethan Galstad <nagios at nagios.org>
>To: Nagios Developers List <nagios-devel at lists.sourceforge.net>
>Cc: matthew-ln at itconsult.co.uk
>Date: Thu, 24 Jan 2008 10:03:11 -0600
>Subject: Re: [Nagios-devel] Reproducible bug scheduling second host check following failure
>Matthew Richardson wrote:
>> I have, for some time, been suspicions that Nagios 3 appeared a bit slow
>> alerting on host failures. In order to diagnose this, I setup a minimal
>> config to try to show the problem using 3.0rc1 with a default nagios.cfg.
>> It consists of one host and one service (both checked by ping), with the
>> retries and timers set as below (the config file is attached in full):-
>>
>> |define host{
>> | host_name hostname
>> | check_interval 10
>> | retry_interval 1
>> | max_check_attempts 5
>> |}
>> |define service{
>> | max_check_attempts 5
>> | normal_check_interval 5
>> | retry_check_interval 5
>> | host_name hostname
>> | service_description ping
>> |}
>>
>[snip]
>
>Thanks for the debug info Matthew. I believe I've tracked down and
>fixed the problem. Patch will be in CVS in a few moments...
I have repeated exactly the same tests with 3.0rc2, and can confirm that it
is now behaving correctly.
Thank you most kindly...
Best wishes,
Matthew
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
More information about the Developers
mailing list