CRITICAL - You need more args!


Hi all!

I now have a Nagios setup running on a vserver, but am getting some weird reports… All nodes are being checked with check_alive, but that gives the state of ‘CRITICAL - You need more args!!!’ on all of them!

When I run the check_ping from the command line, I get:

CRITICAL - You need more args!!!
Could not open pipe:

When I attempt a normal ping the hosts respond normally though…


Try check_fping. It looks like it compiled poorly, since my check_ping returns “Could not parse arguments” when I give it no args whatsoever.
check_ping: Could not parse arguments
Usage: check_ping -H <host_address> -w ,% -c ,%
-p packets] -t timeout] -L] -4|-6]


What do you get when you try ./check_ping --help?


I get what I’m supposed to get:

./check_fping --help
check_fping (nagios-plugins 1.4) 1.24
Copyright (c) 1999 Didi Rieder <>
Copyright (c) 2000-2004 Nagios Plugin Development Team

This plugin will use the /bin/fping command to ping the specified host
for a fast check if the host is alive.
Note that it is necessary to set the suid flag on fping.

Usage: check_fping <host_address>

 -h, --help
    Print detailed help screen
 -V, --version
    Print version information
 -H, --hostname=HOST
    Name or IP Address of host to ping (IP Address bypasses name lookup,
    reducing system load)
 -w, --warning=THRESHOLD
    warning threshold pair
 -c, --critical=THRESHOLD
    critical threshold pair
 -b, --bytes=INTEGER
    Size of ICMP packet (default: 56)
 -n, --number=INTEGER
    Number of ICMP packets to send (default: 1)
 -v, --verbose
    Show details for command-line debugging (Nagios may truncate output)

THRESHOLD is <rta>,<pl>% where <rta> is the round trip average travel
time (ms) which triggers a WARNING or CRITICAL state, and <pl> is the
percentage of packet loss to trigger an alarm state.

Send email to if you have questions
regarding use of this software. To submit patches or suggest improvements,
send email to


check_ping is what you stated you are having trouble with, but you gave output from check_fping --help so I’m wondering what you get for output from check_ping --help. I suspect that check_ping is compiled poorly and won’t even give you help output.


check_ping also compiled correctly. The output I get is pretty similar to the one listed above for check_fping… 8)


So check_ping --help works, but
./check_ping -H localhost -w 10,10% -c 20,20%
PING OK - Packet loss = 0%, RTA = 0.04 ms

Doesn’t work like mine does? Perhaps you didn’t include the -H, or the -w or the -c?


Found it!

It turns out the problem is related to this thread. The check_ping I eventually ended up with after the compilation seems fine, but doesn’t work!

I had to take the check_ping compiled on the physical server, and move it to the vserver to get things to work… :shock: