[Nagios-users] check ping explanation required
Nagios uses check_ping for the host check of most hosts.
The check is configured to send only one ping.
So if Nagios receives a response, it is 0% packet loss.
If no response, it is 100% packet loss.
# 'check-host-alive' command definition
define command{
command_namecheck-host-alive
command_line$USER1$/check_ping -H $HOSTADDRESS$ t 45 -4 -w
3000.0,100% -c 3000.0,100% -p 1
}
Yet, Nagios reports:
p...@bway2852-3-1.net.columbia.edu:2009-06-30 23:24:33:PING
OK - Packet loss = 85%, RTA = 47.06 ms
How is it possible for Nagios to lose 85% of one ping?
--
Cordially,
Shadhin Rahman
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge___
Nagios-users mailing list
Nagios-users@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
Re: [Nagios-users] check ping explanation required
shadih rahman wrote: Nagios uses check_ping for the host check of most hosts. The check is configured to send only one ping. So if Nagios receives a response, it is 0% packet loss. If no response, it is 100% packet loss. How is it possible for Nagios to lose 85% of one ping? The plugin issues 5 pings by default: [r...@webapps nagios]# /usr/lib64/nagios/plugins/check_ping -help check_ping v1991 (nagios-plugins 1.4.13) Copyright (c) 1999 Ethan Galstad nag...@nagios.org Copyright (c) 2000-2007 Nagios Plugin Development Team nagiosplug-de...@lists.sourceforge.net Use ping to check connection statistics for a remote host. Usage:check_ping -H host_address -w wrta,wpl% -c crta,cpl% [-p packets] [-t timeout] [-4|-6] Options: -h, --help Print detailed help screen -V, --version Print version information -4, --use-ipv4 Use IPv4 connection -6, --use-ipv6 Use IPv6 connection -H, --hostname=HOST host to ping -w, --warning=THRESHOLD warning threshold pair -c, --critical=THRESHOLD critical threshold pair -p, --packets=INTEGER number of ICMP ECHO packets to send (Default: 5) ... DR -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] check ping explanation required
shadih rahman wrote: David, Thanks for your reply. I am ensuring one icmp packet by using -p option in my command definition. Please advise on this. Thanks On Tue, Jul 14, 2009 at 2:40 PM, David Rosenstrauch dar...@darose.netwrote: The plugin issues 5 pings by default: $USER1$/check_ping -H $HOSTADDRESS$ t 45 -4 -w 3000.0,100% -c 3000.0,100% -p 1 Hmmm ... Well, assuming that your command definition got pasted correctly, it looks like there's a typo in your command. It should be -t 45, not t 45. So I'd guess that perhaps the plugin is getting messed up by the typo and never parsing the -p 1 parm, and so still issuing 5 pings? Just a guess though. HTH, DR -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Nagios-users mailing list Nagios-users@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
