False Positive Results for check_ping

[Robert V. Bolton]

Thanks for the tip Marty.

On Sat, Aug 20, 2011 at 10:16 AM, Martin Hugo <Martin_Hugo at hboe.org> wrote:

>  I believe there Is a previous post about a bug in check_ping.  Use
> check_icmp instead.****
>
> ** **
>
> HTH****
>
> ** **
>
> Marty****
>
> ** **
>
> *From:* Robert V. Bolton [mailto:robert at robertvbolton.com]
> *Sent:* Saturday, August 20, 2011 12:06 PM
> *To:* nagios-users at lists.sourceforge.net
> *Subject:* [Nagios-users] False Positive Results for check_ping****
>
> ** **
>
> I'm seeing a lot of false positive results from one of the host I'm
> monitoring with the check_ping plugin. Looking at the logs I see various
> degrees of packet lost for this host, but when a run the standard ping from
> the command line don't have any packet loss. Does anyone have any insight
> about this?
>
> --- Section From Log File ---
> Aug 20 08:55:29 monitor nagios: EXTERNAL COMMAND:
> PROCESS_SERVICE_CHECK_RESULT;gw-ssb-moria;Ping Check IPv4;0;PING OK - Packet
> loss = 50%, RTA = 0.57 ms
> Aug 20 08:55:35 monitor nagios: PASSIVE SERVICE CHECK: gw-ssb-moria;Ping
> Check IPv4;0;PING OK - Packet loss = 50%, RTA = 0.57 ms
> Aug 20 08:56:36 monitor nsca[25608]: SERVICE CHECK -> Host Name:
> 'gw-ssb-moria', Service Description: 'Ping Check IPv4', Return Code: '0',
> Output: 'PING OK - Packet loss = 37%, RTA = 0.56 ms'
> Aug 20 08:56:38 monitor nagios: EXTERNAL COMMAND:
> PROCESS_SERVICE_CHECK_RESULT;gw-ssb-moria;Ping Check IPv4;0;PING OK - Packet
> loss = 37%, RTA = 0.56 ms
> Aug 20 08:56:44 monitor nagios: PASSIVE SERVICE CHECK: gw-ssb-moria;Ping
> Check IPv4;0;PING OK - Packet loss = 37%, RTA = 0.56 ms
> Aug 20 08:57:44 monitor nsca[27186]: SERVICE CHECK -> Host Name:
> 'gw-ssb-moria', Service Description: 'Ping Check IPv4', Return Code: '0',
> Output: 'PING OK - Packet loss = 0%, RTA = 1.19 ms'
> Aug 20 08:57:48 monitor nagios: EXTERNAL COMMAND:
> PROCESS_SERVICE_CHECK_RESULT;gw-ssb-moria;Ping Check IPv4;0;PING OK - Packet
> loss = 0%, RTA = 1.19 ms
> Aug 20 08:57:53 monitor nagios: PASSIVE SERVICE CHECK: gw-ssb-moria;Ping
> Check IPv4;0;PING OK - Packet loss = 0%, RTA = 1.19 ms
> Aug 20 08:58:14 monitor nsca[27765]: HOST CHECK -> Host Name:
> 'gw-ssb-moria', Return Code: '0', Output: 'PING OK - Packet loss = 0%, RTA =
> 0.55 ms'
> Aug 20 08:58:16 monitor nagios: EXTERNAL COMMAND:
> PROCESS_HOST_CHECK_RESULT;gw-ssb-moria;0;PING OK - Packet loss = 0%, RTA =
> 0.55 ms
> Aug 20 08:58:23 monitor nagios: PASSIVE HOST CHECK: gw-ssb-moria;0;PING OK
> - Packet loss = 0%, RTA = 0.55 ms
> Aug 20 08:58:44 monitor nsca[28875]: SERVICE CHECK -> Host Name:
> 'gw-ssb-moria', Service Description: 'Ping Check IPv4', Return Code: '0',
> Output: 'PING OK - Packet loss = 50%, RTA = 0.54 ms'
> Aug 20 08:58:49 monitor nagios: EXTERNAL COMMAND:
> PROCESS_SERVICE_CHECK_RESULT;gw-ssb-moria;Ping Check IPv4;0;PING OK - Packet
> loss = 50%, RTA = 0.54 ms
> Aug 20 08:58:53 monitor nagios: PASSIVE SERVICE CHECK: gw-ssb-moria;Ping
> Check IPv4;0;PING OK - Packet loss = 50%, RTA = 0.54 ms
> Aug 20 08:59:46 monitor nsca[30278]: SERVICE CHECK -> Host Name:
> 'gw-ssb-moria', Service Description: 'Ping Check IPv4', Return Code: '0',
> Output: 'PING OK - Packet loss = 0%, RTA = 0.54 ms'
> Aug 20 08:59:48 monitor nagios: EXTERNAL COMMAND:
> PROCESS_SERVICE_CHECK_RESULT;gw-ssb-moria;Ping Check IPv4;0;PING OK - Packet
> loss = 0%, RTA = 0.54 ms
> Aug 20 08:59:54 monitor nagios: PASSIVE SERVICE CHECK: gw-ssb-moria;Ping
> Check IPv4;0;PING OK - Packet loss = 0%, RTA = 0.54 ms
>
> --- Results From Ping Command ---
> PING 172.30.0.3 (172.30.0.3) 56(84) bytes of data.
> 64 bytes from 172.30.0.3: icmp_seq=1 ttl=255 time=0.531 ms
> 64 bytes from 172.30.0.3: icmp_seq=2 ttl=255 time=0.563 ms
> 64 bytes from 172.30.0.3: icmp_seq=3 ttl=255 time=0.506 ms
> 64 bytes from 172.30.0.3: icmp_seq=4 ttl=255 time=0.554 ms
> 64 bytes from 172.30.0.3: icmp_seq=5 ttl=255 time=0.505 ms
> 64 bytes from 172.30.0.3: icmp_seq=6 ttl=255 time=0.561 ms
> 64 bytes from 172.30.0.3: icmp_seq=7 ttl=255 time=0.534 ms
> 64 bytes from 172.30.0.3: icmp_seq=8 ttl=255 time=0.499 ms
> 64 bytes from 172.30.0.3: icmp_seq=9 ttl=255 time=0.496 ms
> 64 bytes from 172.30.0.3: icmp_seq=10 ttl=255 time=0.554 ms
> 64 bytes from 172.30.0.3: icmp_seq=11 ttl=255 time=0.512 ms
>
> --- 172.30.0.3 ping statistics ---
> 11 packets transmitted, 11 received, 0% packet loss, time 10000ms
> rtt min/avg/max/mdev = 0.496/0.528/0.563/0.035 ms
>
> --
> Robert V. Bolton
> Email: robert at robertvbolton.com
> Web: http://robertvbolton.com
>
> ****
>
>
> ------------------------------------------------------------------------------
> Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
> user administration capabilities and model configuration. Take
> the hassle out of deploying and managing Subversion and the
> tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
> _______________________________________________
> 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
>



-- 
Robert V. Bolton
Email: robert at robertvbolton.com
Web: http://robertvbolton.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20110820/ae582e10/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
-------------- next part --------------
_______________________________________________
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