host down but up problem

[Andreas Ericsson]

Serveur-Faucon Surveillance wrote:
> Hi all,
> 
> I have been using Nagios for quite a while now over 2 years, so I am
> pretty familiar with it.
> 
> One of my host recently went to a down state on the network status,
> but is actually UP. This is not FAQ F0015 or F0016 related, since the
> same command is used by all other hosts (and they are just fine).
> 
> I use the check_host_alive default command to check on hosts status
> (yeah I know, I dont use the hip (new, cool) check_icmp from Andreas
> Ericsson for now. Later)
> 

Don't know about hip and cool, but you're probably better off without 
it. "Don't fix it if it ain't broken".

> So I went to my console to try a couple of things... ping myhost =
> ok! check_ping -H myhost etc etc = ok! (exactly like the
> check_host_alive)
> 
> So... my next theory would be to erase everything from that host in
> the history, and start over. But before that, is there someone who
> actually had something like that?
> 
> There was the bug witch two nagios process could run at the same
> time, but that's not it. Thanks!
> 

This can happen properly when the host starts flapping while down and 
comes out OK on the other end of the flapping. Assuming you aren't 
running 2.0 with f among your notification_options, ofcourse.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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