fping issue

[Andy Stein]

Hey Gang,

I'm having a recurring problem:

I have two hosts that are listed as down right now, but pinging with both
ping and fping from the nagios server return replies that the host is up.

Running RH7.3, Nagios 1.2, Nagios-plugins 1.3.1.  I am watching over 400
hosts and I am currently having this issue with two hosts.

Config file:
# 'check-host-alive' command definition
define command{
        command_name    check-host-alive
#       command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w 2000.0,60%
-c 5000.0,100% -t 15 -p 2
        command_line    $USER1$/check_fping -H $HOSTADDRESS$ -w 2000.0,60%
-c 5000.0,100%
        }

Web status page:
Host Status:
  DOWN  (Has been acknowledged)
Status Information:	FPING CRITICAL - 165.75.x.x (loss=100.000000% ) Last
Status Check:	08-02-2004 09:48:31
Status Data Age:	0d 0h 0m 51s
Last State Change:	08-02-2004 05:48:26
Current State Duration:	0d 4h 0m 56s
Last Host Notification:	08-02-2004 06:30:13
Current Notification Number:  	2
Is This Host Flapping?
  NO
Percent State Change:	10.00%
In Scheduled Downtime?
  NO
Last Update:	08-02-2004 09:49:07

fping from command line:
[root at mnmslx11 libexec]# ./check_fping -v -H 165.75.x.x
/usr/local/sbin/fping -b 56 -c 1 165.75.x.x
165.75.x.x : [0], 84 bytes, 0.22 ms (0.22 avg, 0% loss)

165.75.x.x : xmt/rcv/%loss = 1/1/0%, min/avg/max = 0.22/0.22/0.22
FPING OK - 165.75.x.x (loss=0.000000%, rta=0.220000 ms)







-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.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