Hi Benny.
C. Bensend wrote: >> Yesterday for instance, a host went down because of a hd controller >> failure, and I received 22 sms.. > > I apologize if this has already been stated, I haven't been following > this thread too closely. > > When this happened, was the host down *in a network sense*, or was > it just down in a user sense? Ie, was it still pingable? The host was not pingable. > A situation I've dealt with in the past is that a host's network > stack might still be "alive enough" (ie, pingable), while the host > itself is sitting at a kernel panic or locked up. In that case, > if you're using ping for the host check, Nagios would have no way > of knowing that the host is down, because it still responds. > > In those [rare] cases, I've had to define a second command that > requires a more intelligent response from a host, and then used > that as the host check command. Notable examples would be old > school Sun machines, which are still pingable when they're sitting > at the OK> prompt (ie, operating system is not running). Thank you Benny, but this was not the case. The host was not pingable at that time. I'm not 100% sure, but the problem maybe was maybe caused by a misconfiguration of the host/service check interval/max check attempts. Best regards. Robi ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Nagios-users mailing list [email protected] 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
