Socket timeout causes immediate critical notification

[Castelhano, Dan]

Hi,

We periodically get socket timeout errors with nrpe service checks. Problem
is, a notification is sent on the very first socket timeout error (which is
causing a critical status)...its not adhering to the max_check_attempts
number defined in the host and service templates (its set to 3). We'll get a
recovery email 30-60 seconds after the critical email.

i did a grep search on all the config files just to make sure i didn't miss
any max_check_attempts definitions hidden in the config files and confirmed
they're all set to a minimum of 3 (one template is set to 10)

i'm at a loss, and it doesn't help that these emails are being sent to my
cell after hours. 

I'm running nagios 1.2 on redhat 9.0 
i'm using nsclient++ 1.22 on windows servers, and nrpe 2.0 on linux servers.


All the socket timeouts are coming from nrpe service checks on the linux
clients.

any ideas what could be wrong? 

Thanks,
dan


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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