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
In that situation I would use a command other than ping that would be more
indicative of the host being down. Like ssh/telnet, or for windows a check_tcp
against the remote desktop port, anything that will send a response back
indicates the host is up.
Sent on the Sprint® Now Network from my
One thing that just occured to me and I only thought of it just now. Are you
using a PERL script as a notification command? If so, that could explain the
wrong information. If Nagios was compiled with the embedded PERL interpreter
and the script is not written with that in mind, it could easily
The line above indicates he need Hash::Merge::Simple. Install that one and try
again. If it stops again, install what is indicated as missing.
Sent on the Sprint® Now Network from my BlackBerry®
-Original Message-
From: john s. firesk...@emailn.de
Date: Thu, 18 Oct 2012 13:37:58
To:
Did you try making a group of the router you want to exclude and then exclude
that on the hostgroup_name line instead? That may solve it although I agree it
is weird that the host exclusion seems limited to 5 exclusions. The only other
thing I can think of is that the Routers group only
When I have issues like that, I turn up debugging in nagios.cfg then force the
service to go critical with passive commands from the CGI. Remember that the
debug options are additive, so only include what you need to figure out what is
going on. I would say just from this conversation that it
