In about a month I'll be getting an official request to have freshness
checking turned on, with all the commands being something like:
echo Stale check!;exit 2
So, unfortunately ensuring that the master never ever accidentally runs
a check is important, even beyond the current issue of hosts
On 10/23/2012 11:00 PM, Mike Lindsey wrote:
I've got a passive-only master that is configured to never execute
checks. Yet it's still performing ping checks for some hosts at some
times. This is mostly just annoying, but when it decides to ping hosts
that it doesn't have a route to, pagers
You can always set the check command for the host to execute the check_dummy
plugin so that if it doesn't get the result and decides to run an active check
check_dummy will force it to be in an up state.
Sent on the Sprint® Now Network from my BlackBerry®
-Original Message-
From: Mike
