host check interval

[Fredrik Wänglund]

You could make it a little bit better by decreasing 'max_check_attempts'

/FredrikW


Marc Powell wrote:

> This is certainly one of those things I wish I could change easily 
> about nagios. It's not uncommon for us to have 20-30 devices down on 
> our statewide network at any given time. This equates to 1-1.5% of the 
> total number of devices we are monitoring. Because of the fact that 
> nagios goes hard and heavy on host failures, I've had to make my 
> check-host-alive command just a null command so that my other checks 
> are not delayed. Allowing a min/max host-check-interval would be a 
> nice addition.
>  
> --
> Marc
>
>     -----Original Message-----
>     From: Dean Bishop [mailto:dbishop at ehvert.com]
>     Sent: Wed 5/21/2003 4:41 PM
>     To: 'Douglas K. Rand'; Nagios-Users
>     Cc:
>     Subject: RE: [Nagios-users] host check interval
>
>     Nope.  Host alerts do not have any interval.  They are run only if
>     a service
>     check on that host fails.  If the service check fails once, and
>     only once,
>     regardless of retry interval and max check, the host is checked
>     using the
>     host's check command.  There is no sense in continuing to test the
>     service
>     if the host is down right?
>
>     When the host is checked, it is check fast and furious.  The
>     checks are run
>     at the highest priority above normally scheduled checks.  After
>     all, you may
>     have a server down and you would like to know about it right away.
>
>     Hope this helps,
>     dean
>
>     -----Original Message-----
>     From: Douglas K. Rand [mailto:rand at meridian-enviro.com]
>     Sent: May 21, 2003 4:14 PM
>     To: Nagios-Users
>     Subject: [Nagios-users] host check interval
>
>     I'm trying to adjust the interval between host checks, and I'm not
>     having any luck. The directives normal_check_interrval and
>     retry_check_interrval don't work for hosts:
>
>       Error: Could not add object property in file
>     '/usr/local/etc/nagios/hosts.cfg' on line 13.
>
>     And while I have host_check_timeout set to 30, it doesn't seem to
>     have
>     any affect. Here is a snippett from my nagios.log:
>
>       [1053541716] HOST ALERT: Hahn-VPN;DOWN;SOFT;1;CRITICAL - Plugin
>     timed out
>     after 10 seconds
>       [1053541726] HOST ALERT: Hahn-VPN;DOWN;SOFT;2;CRITICAL - Plugin
>     timed out
>     after 10 seconds
>       [1053541736] HOST ALERT: Hahn-VPN;DOWN;SOFT;3;CRITICAL - Plugin
>     timed out
>     after 10 seconds
>       [1053541746] HOST ALERT: Hahn-VPN;DOWN;SOFT;4;CRITICAL - Plugin
>     timed out
>     after 10 seconds
>       [1053541756] HOST ALERT: Hahn-VPN;DOWN;HARD;5;CRITICAL - Plugin
>     timed out
>     after 10 seconds
>       [1053541756] HOST NOTIFICATION:
>     rand;Hahn-VPN;DOWN;host-notify-by-email;CRITICAL - Plugin timed
>     out after 10
>     seconds
>       [1053541757] SERVICE ALERT: Hahn-VPN;PING;CRITICAL;HARD;1;FPING
>     CRITICAL -
>     192.168.2.1 (loss=100.000000% )
>
>     As you can see, nagios checks the hosts every 10 seconds. And that is
>     too quick for us, we'd like it to check every minute, because with
>     the
>     10 second interval we get too many host down notifications for our
>     remote systems.
>
>     The docs say:
>
>       Also of note - when Nagios is check the status of a host, it holds
>       off on doing anything else (executing new service checks,
>     processing
>       other service check results, etc). This can slow things down a bit
>       and cause pending service checks to be delayed for a while, but it
>       is necessary to determine the status of the host before Nagios can
>       take any further action on the service(s) that are having problems.
>
>     It isn't clear to me, if it is checking a host, does it hold off on
>     ALL other service checks, or just service checks to that host (and
>     perhaps child hosts)?
>
>     If it holds off on ALL other service checks, I've got to find another
>     way to do this, I can't have no service checks happening for 5
>     minutes.
>
>
>     -------------------------------------------------------
>     This SF.net email is sponsored by: ObjectStore.
>     If flattening out C++ or Java code to make your application fit in a
>     relational database is painful, don't do it! Check out ObjectStore.
>     Now part of Progress Software. http://www.objectstore.net/sourceforge
>     _______________________________________________
>     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
>
>
>     -------------------------------------------------------
>     This SF.net email is sponsored by: ObjectStore.
>     If flattening out C++ or Java code to make your application fit in a
>     relational database is painful, don't do it! Check out ObjectStore.
>     Now part of Progress Software. http://www.objectstore.net/sourceforge
>     _______________________________________________
>     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
>




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
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