normal_check_interval misbehaving?

[Hiren Patel]

Jason Marshall wrote:
>> is the active-service template set to check freshness, if so what is its
>> value? I suspect the check results are getting stale and forcing an
>> active check, this can be verified from the nagios logs on the nagios
>> server though (perhaps depending on logging options?)
> 
> Thanks Hiren, the check_freshness value for active services is enabled, 
> and the threshold is set to 5 minutes, but there is no check_command set 
> for it.  I don't think I've ever had active checks go stale, so I'm 
> going to try turning that value off to see what happens.
> 
> Thanks for the idea, I never would have thought of this one!
> 


active-checks should be a template, so there wouldn't be a check_command 
for it. normally your active check won't go stale, because they're 
scheduled to run more often than the freshness threshold. check your 
logs for signs of:

--
[1233827017] Warning: The results of service 'Total Processes' on host 
'slave' are stale by 0d 0h 1m 0s (threshold=0d 0h 10m 0s).  I'm forcing 
an immediate check of the service.
--

this still doesn't explain why the checks are run every 10 minutes 
though, if freshness threshold is set to 5 minutes.

have you confirmed that there isn't another nagios process running, as 
directed from another reply to this thread?

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
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