check_ping changed to check_fping

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Marc Hultquist
> Sent: Thursday, October 18, 2007 3:18 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] check_ping changed to check_fping
> 
> Hi All
> 
> Ok I seem to have solved my previous problem with the check_ping
stuff,
> it seems that by slightly increasing the threshhold as well as
changing
> the flags slightly.
> 
> Now here's the thing, I have now changed to use check_fping in terms
of
> monitoring, for example one of my services being hosted is as follows:
> define service{
>         use                     generic-service ;
>         host_name               cksdialup;
>         service_description     PING            ;
>         check_command           check_fping!200.0,20%!600.0,60%  ;
>         normal_check_interval   5;
>         retry_check_interval    1;
>         }
> 
> Now thats all good and well, but if I then go check on my dashboard
for
> service problems, I still see it being checked with ping and not
fping,

How _exactly_ do you know it's using ping and not fping from the web
interface?

> define command{
>         command_name    check_ping
>         command_line    $USER1$/check_fping $HOSTADDRESS$ -w $ARG1$ -c
> $ARG2$ -n 5
>         }

Note in the service definition that you've specified to use the
check_fping command, but provided us the check_ping command definition.
They are not the same.
 
--
Marc


-------------------------------------------------------------------------
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/
_______________________________________________
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