Monitoring an intermittent host
Rob Nelson
rob at capband.net
Wed Aug 13 00:13:33 CEST 2003
> Thanks that is a great idea, IE if my checks are every 5 minutes
> then I can set max check attempts to 25 and that will mean it has to be
> down for over 2 hours before it sends me a note. Thanks again, I new it
> was something simple I was missing.
Actually, you want to listen to what the other poster said, with the
retry_delay or whatnot. The reason you don't want to set max check attempts
to 25 is that if, 5 minutes after the last successful check, the host is
unavailable, Nagios stops processing ALL other host/service checks while
determining the status of this host/server. So for the next 25 * X sec,
Nagios is trying to talk to JUST that device. So after 75 seconds, Nagios
waits another 5 minutes, then spends another 75 seconds checking just that
host, etc.
This may or may not impact you that much. My system is running about 5-10
checks per second, depending on how fast they return, so I lose 80-90%
performance every time a single service is unavailable.
Rob Nelson
Network Administrator, Capitol Broadband
C: 919-369-1874
rob at capband.net
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
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
More information about the Users
mailing list