#100 check_ping demands more args

[Anonymous]

I am having a problem with the check-host-alive
function. The following line exists in my hosts.cfg
file...

host[host]=host.domain.com;127.0.0.1;;check-host-alive;10;120;24x7;1;1;1;

Netsaint reports a CRITICAL down failure and
consistently generates the following email
notifications...

Notification Type: PROBLEM
Host: host
State: DOWN
Address: 127.0.0.1
Info: You've got a big problem buddy! You need more
args!!!

The command.cfg file contains the following line...

command[check-host-alive]=$USER1$/check_ping
$HOSTADDRESS$ 100 100 5000.0 5000.0 -p 1

The system is up and running, able to respond to pings
and reports status "OK" on ftp and http services.

I've checked my system by running the following from
the command line...

[prompt]./check_ping 127.0.0.1 100 100 5000.0 5000.0 -p
1
You've got a big problem buddy! You need more args!!!

By the way, I'm running NetSaint 0.0.6, plugins 1.2.9-4
(out-of-the-box installation) on a RedHat 7.2 system.

[Nobody/Anonymous]

Logged In: NO

I am having this same issue. Furthermore ( I suspect this
is related ) when installing the latest plugin package the
installation halted when seeking /bin/ping. CTRL C let the
installation continue but it said something along the lines
of not being able to find a suitable ping command. If
somebody can detail how check_ping can be made to function
correctly I will attempt to create/correct documentation
for it and get this part of the project squared away. The
existing help clearly is inadequate as it provides no
answer as to what "more args" means exactly.

[Nobody/Anonymous]

Logged In: NO

Basically 1.2.9-4 check_ping is expecting the warning and
critical threshold times. In the following example the
warning is set to 150ms and critical to 180ms. change it to
suit your site and it should work without any problems

In commands.cfg, change check_ping line to
command[check_ping]=$USER1$/check_ping -H $HOSTADDRESS$ -w
$ARG1$ -c $ARG2$ -p 1

In hosts.cfg, service definitions, use as follows
service[host10]=ping;0;24x7;10;5;1;router-admins;10;24x7;
1;1;1;;check_ping!150,80%!180,80%

Hope that helps

[Nobody/Anonymous]

Logged In: NO

I have the same problem, I have tried using:

./check_ping -H x.x.x.x -w 100.0,20% -c 500.0,60% -p 5

From the command line but still get the same error about
not having enough args. I can ping from the command line
using the ping command so this is not the problem.

Thanks,

[Nobody/Anonymous]

Logged In: NO

Just done a bit of digging in popen.c and if I print out
the cmdline var at the point the error is printed i
get "Cannot open pipe"

Thanks,

Karl

[Nobody/Anonymous]

Logged In: NO

It gets weirder, I modified the check_ping.c to output a
little debug, tested, took the changes out, recompiled and
it works fine now.

[Nobody/Anonymous]

Logged In: NO

I have the same problem, using Suse Linux 8.0. The solution
of the problem is to exchange /bin/ping with an older one (I
use ping from Suse 6.4). The you have to run "make clean" in
the plugins directory and then rebuild und reinstall the
plugins. Dont forget to run the configure script againg
after "make clean".

Hope that helps you