Problem with nagios check_ping plugin

[Alex Dehaini]

Hi Everyone,

I have been using nagios for 2 months now and it is really good. So far, all
plug-ins work well but recently the check_ping plugin has been acting funny
and giving wrong results.

This is the OS info
OS - Debian
Nagios Version 2.9
Problem = check_ping plugin reports alot of packet loss on our network but
when we use regular ping commands, it is not true. check_ping looks like
this in the command.cfg file

# 'check_ping' command definition
define command{
        command_name    check_ping
        command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ -c
$ARG2$ -p 10
        }

This is an example of a service that uses check_ping

define service{
        use                             servers
        host_name                       bhslave at nkwanta
        service_description             PING
        check_command                   check_ping!200.0,20%!600.0,60%
        }

The problem is nagios will warn me of 28% packet loss to this host that is 3
hops away from the monitoring system and the RTA will be about 60ms. It does
this randomly. I will like to know how nagios computes this info and how it
determines this.

Any help will be greatly appreciated.

Regards,
Alex Dehaini
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20071005/5806628a/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
-------------- 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