Page 1 of 1

Re: [Nagios-devel] freshness_threshold bug - big problem

Posted: Fri Dec 17, 2010 11:10 am
by Guest
--0016364d29550b89ba049799383e
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Jochen,

Than I understood that you confirm the problem, as your configuration was:
check_interval 15, retry_interval 2 and max_check_attempts 4.

And from your log we have:

18:39:55 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 12s
(threshold=3D0d 0h 15m 16s). I'm forcing an immediate check of the host.
18:40:05 HOST ALERT: Unfresh;DOWN;SOFT;1;(null)

18:56:13 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 59s
(threshold=3D0d 0h 15m 17s). I'm forcing an immediate check of the host.
18:56:23 HOST ALERT: Unfresh;DOWN;SOFT;2;(null)

--> It=B4s wrong. It should be about 18:42:05, 2 minutes after the SOFT1, a=
s
your retry_interval is 2 minutes.

19:28:13 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 39s
(threshold=3D0d 0h 15m 18s). I'm forcing an immediate check of the host.
19:28:23 HOST ALERT: Unfresh;DOWN;SOFT;3;CRITICAL: All life functions
terminated

--> It=B4s wrong. It should be about 18:58:23, 2 minutes after the SOFT2, a=
s
your retry_interval is 2 minutes.

19:44:13 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 39s
(threshold=3D0d 0h 15m 18s). I'm forcing an immediate check of the host.
19:44:23 HOST ALERT: Unfresh;DOWN;HARD;4;CRITICAL: All life functions
terminated

--> It=B4s wrong. It should be about 19:30:23, 2 minutes after the SOFT3, a=
s
your retry_interval is 2 minutes.

I=B4d like to know if the Nagios Core developers have already realized this
problem and if they are intending to correct it for the next release or
making a patch.

Thanks,
Rodney


On Thu, Dec 16, 2010 at 6:59 PM, Jochen Bern wrote=
:

> On 12/16/2010 12:03 PM, Rodney Ramos wrote:
> > As I=B4ve said before I think that it is a Nagios Core bug. I=B4ve test=
ed it
> > with Nagios 3.2.1 and I found the same problem.
> > I think it=B4s a serious problem.
>
>
> Oh, wow. 8-O I can confirm the effect on my 3.2.3, but there seems to be
> *more* of a problem with host freshness checks. Test run with
> check_interval 15, retry_interval 2, max_check_attempts 4; log excerpt:
>
>
> 18:23:55 Warning: Host 'Unfresh' has no services associated with it!
> 18:24:28 EXTERNAL COMMAND: PROCESS_HOST_CHECK_RESULT;Unfresh;0;Manual
> Init to UP|
> 18:24:35 PASSIVE HOST CHECK: Unfresh;0;Manual Init to UP
>
> 18:39:55 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 12s
> (threshold=3D0d 0h 15m 16s). I'm forcing an immediate check of the host=
.
> 18:40:05 HOST ALERT: Unfresh;DOWN;SOFT;1;(null)
>
> 18:51:12 Warning: Host 'Unfresh' has no services associated with it!
>
> 18:56:13 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 59s
> (threshold=3D0d 0h 15m 17s). I'm forcing an immediate check of the host=
.
> 18:56:23 HOST ALERT: Unfresh;DOWN;SOFT;2;(null)
> 19:00:12 Warning: Host 'Unfresh' has no services associated with it!
> 19:12:13 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 45s
> (threshold=3D0d 0h 15m 15s). I'm forcing an immediate check of the host=
.
> 19:12:23 HOST ALERT: Unfresh;DOWN;SOFT;2;CRITICAL: All life functions
> terminated
> 19:28:13 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 39s
> (threshold=3D0d 0h 15m 18s). I'm forcing an immediate check of the host=
.
> 19:28:23 HOST ALERT: Unfresh;DOWN;SOFT;3;CRITICAL: All life functions
> terminated
> 19:44:13 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 39s
> (threshold=3D0d 0h 15m 18s). I'm forcing an immediate check of the host=
.
> 19:44:23 HOST ALERT: Unfresh;DOWN;HARD;4;CRITICAL: All life functions
> terminated
> 20:00:13 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 39s
> (threshold=3D0d 0h 15m 18s). I'm forcing an immediate check of the host=
.
> 20:16:13 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 41s
> (threshold=3D0d 0h 15m 17s). I'm forcing an immediate check of the host=
.
> 20:32:13 Warning: The results of host 'Unfresh' are stale by 0d 0h 0m 39s
> (threshold=3D0d 0

...[email truncated]...


This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]