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
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:
I have a check_command for my passive checks, but it just exits
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?)
Jason Marshall wrote:
Hi all, I've been scratching my head on this one for a couple days.
I have a service defined that can only run once an hour. If it runs much
more often than that, the check program (which I didn't write) often steps
on its own feet and returns a critical failure.
Hi all, I've been scratching my head on this one for a couple days.
I have a service defined that can only run once an hour. If it runs much
more often than that, the check program (which I didn't write) often steps
on its own feet and returns a critical failure. The service runs via NRPE
if
On Feb 6, 2009, at 4:06 PM, Jason Marshall wrote:
Hi all, I've been scratching my head on this one for a couple days.
I have a service defined that can only run once an hour. If it runs
much
more often than that, the check program (which I didn't write) often
steps
on its own feet
