freshness checks threshold

[Sean Dilda]

On Mon, 2004-10-04 at 10:16, Ralf Wigand wrote:
> hi!
> 
> when I define a passive check and want to check if the passive check
> reported on the schedules times, I am using the following config:
> 
> ...
> check_command                   check_missed_passive-check
> check_freshness                 1
> freshness_threshold             1800
> active_checks_enabled           0
> passive_checks_enabled          1
> max_check_attempts              3
> normal_check_interval           1
> retry_check_interval            1
> ...
> 
> So, my understanding is:
> passive check should send a result every 60 seconds
> (normal_check_interval), and if the result is missing for more then 1800
> sec (freshness_threshold) do the check_missed_passive-check (as in
> check_command).
> 
> Well, here is what the logfile says:
> Warning: The results of service 'xxxxxx' on host 'xxxxxx' are stale by
> 19 seconds (threshold=1800 seconds). I'm forcing an immediate check of
> the service.

I have a similar setup and things work the way I expect, and I get
similar messages to what you have.  I believe what it means is that the
service is stale when it hasn't been updated in 1800 seconds, and its
been stale for 19 seconds, which means that the service hasn't been
updated in 1819 seconds.  You should check the web interface details on
that service to see when it says it last received an update.



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Nagios-users mailing list
Nagios-users at 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