ping Critical Error

[Chester R. Hosey]

On Fri, 2005-08-12 at 15:05 +0200, Arjuna Scagnetto wrote:
> i've Scientific linux 3.4 , check_ping command gives back this error
> 
> []# check_ping -H 140.105.31.* -w 300.0,80% -c 5000.0,50% -p 1
> 
> /bin/ping -n -U -w 10 -c 1 140.105.31.*
> CRITICAL - Could not interpret output from ping command
> 
> Even if i change the values of the options.
> 
> Someone can help me?
> 
> p.s. of course "*" means every number ^^

Offhand, I'd suggest at least giving us the output of running ping
manually on a failing host.

I'd probably start with strace (if installed) to find out whether ping
is even executing successfully. But then, I run strace on just about
everything. It's ALWAYS my answer.

At least some ping output might shed some light on whether your copy of
ping is doing anything naughty (FSVO 'naughty').

Chet


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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