Huge Service Latencies

[Eli Stair]

Good point.  I don't know how to implement 
host-check-only-on-servicecheck-fail on 2.0. I don't see in the config 
that it is supported, from what I read execute_host_checks is a global 
do or donot hostcheck declarative.

Is this correct?

/eli

Ludwig Pummer wrote:
> I should point out I'm running Nagios 1.3, which will only perform host 
> checks if a service check fails. I use check_ping and the 30 seconds and 
> 6 seconds numbers were what I passed to check_ping in my 
> checkcommands.cfg (although it's probable check_ping wasn't waiting the 
> full 30 seconds, it certainly did wait longer than 6 seconds). It was in 
> the host template definition that I set max_check_attempts.
>  
> If you just want to see whether host checks are the source of your 
> latency, try temporarily replacing your host check command with a shell 
> script which does "exit 0". You will of course have to suffer through 
> more service notifications due to downed hosts.
> 
> --
> Ludwig Pummer
> System Administrator
> Copart Auto Auctions
> 
>  
> 
>     ------------------------------------------------------------------------
>     *From:* Blake Krone [mailto:blakekrone at gmail.com]
>     *Sent:* Monday, December 05, 2005 3:14 PM
>     *To:* Ludwig Pummer
>     *Cc:* Nagios Users
>     *Subject:* Re: [Nagios-users] Huge Service Latencies
> 
>     I have active host checks set to 0 so that they won't actually check
>     unless a service fails on the host. How do you specify a recheck in
>     seconds? I thought minutes were all that was allowed.
> 
>     -Blake
> 
>     On 12/5/05, *Ludwig Pummer* <Ludwig.Pummer at copart.com
>     <mailto:Ludwig.Pummer at copart.com>> wrote:
> 
>         I had large latencies caused by (1) hosts being down and (2) a
>         host check that took way too long. Nagios will suspend all
>         service checks while it performs a host check. In my case, the
>         Nagios config I inherited made 10 attempts at 30 seconds each
>         attempt before declaring a host to be down, so if one host went
>         down, the host check took 300 seconds. I typically have 15 hosts
>         down out of 475. I changed my host checks to 3 attempts at 6
>         seconds each, and latencies went way down.
>          
> 
>         --
>         Ludwig Pummer
>         System Administrator
>         Copart Auto Auctions
> 
>          
> 
>             ------------------------------------------------------------------------
>             *From:* nagios-users-admin at lists.sourceforge.net
>             <mailto:nagios-users-admin at lists.sourceforge.net>
>             [mailto:nagios-users-admin at lists.sourceforge.net
>             <mailto:nagios-users-admin at lists.sourceforge.net>] *On
>             Behalf Of *Blake Krone
>             *Sent:* Monday, December 05, 2005 2:08 PM
>             *To:* Nagios Users
>             *Subject:* [Nagios-users] Huge Service Latencies
> 
>             Service Check Execution Time:    0.10 / 10.04 / 2.175 sec
>             Service Check Latency:    21.25 / 483.37 / 224.970 sec
>             Host Check Execution Time:    0.06 / 10.70 / 4.307 sec
>             Host Check Latency:    0.00 / 529.15 / 5.137 sec
>             # Active Host / Service Checks:    103 / 236
>             # Passive Host / Service Checks:    0 / 1
> 
>             Machine is a P3 733mhz with 128mb ram running
>             2.6.11-gentoo-r3 kernel and Nagios 2.03b
> 
> 
>             Any ideas as to why it has such huge latencies?
> 
> 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&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