Re: check_fping generates wrong results

On 8 Nov 2002 at 16:12, Robert Tritscher wrote about "[netsaint] check_fping generates wrong results":

> hi,
> 
> i´ve a large amount of devices to monitor and because of better
> perfomance i want to use check_fping instead of check_ping for
> hostcheck.
> 
> Problem is that with check_fping, Netsaint always says Host Status is UP
> and Status Information displays a "Warning [IPadress]",  independent if
> the host is up or down in reality.
> 
> When i check the host with check_ping, everthing is ok, also when i try
> check_fping on commandline with the same args as in netsaint.
> 
> 
> this is the command:
> command[check-host-alive]=$USER1$/check_fping -H $HOSTADDRESS$ -w
> 2000.0,60% -c 4000.0,100%
> 
> this is netsaint´s output in Host-State-Information:
> Host Status   UP     
> Status Information FPING WARNING - 192.168.0.1 
> 
> this is check_fping´s output on commandline:
> check_fping -H 192.168.0.1 -w 2000.0,60% -c 4000.0,100%
> FPING CRITICAL - 192.168.0.1 (loss=100.000000%, rta=0.000000 ms)
> 
> 
> i use Suse Linux 7.3, Netsaint 0.0.7, check_fping 1.13.2.4

Are you doing your test from the command line as root?

I remeber reading 'the fping executable should be set suid'
to check_fping to work somewhere. I assume it means it should
be set UID root.

Don't forget the fact that Netsaint execute chechs as a non
privileged user.

HTH

> 
> thanks!
> robert
> 

-
Ramiro



-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en