Passive host results & soft states?

[Mike Hamrick]

Thanks Marc, I found this answer from Ethan Galstad in the thread you posted:

> Nagios 2 doesn't support a max_attempts directive for hosts and all 
> passive host check results will immediately force the host into a HARD 
> state.  This has changed a bit in Nagios 3 - hosts do have a 
> max_attempts directive, but passive results still put the host into a 
> HARD state.

I think the solution for me is to change the check-host-alive command
to send more pings, that way one dropped packet on a remotely
monitored box won't cause me to get woken up at some ungodly hour.

The command_line I had for check-host-alive (not sure where I got it) 
seems somewhat silly to me:

Original:
$USER1$/check_ping -H $HOSTADDRESS$ -w 3000.0,80% -c 5000.0,100% -p 1

My Change:
$USER1$/check_ping -H $HOSTADDRESS$ -w 1000.0,40% -c 5000.0,100% -p 5

Mike

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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