ERROR - Service Check Timed Out

[Gerald Wichmann]

One of my service checks runs a script that I wrote that does a find for
certain files. It's invoked by NRPE and works fine on many systems until the
number of files gets really high and the script takes some time to run to
come up with a result. Now I have 3 systems that show critical due to a
status of "(Service Check Timed Out)". I assume because it takes too long to
run the script on those systems and nagios is giving up before it gets a
result. I've seen it take 30+ minutes to run this script (to give you an
idea of how long it can take). It could even be significantly worse..
 
I modified my check_nrpe command definition in checkcommands.cfg and added
"-to 2700" which I thought would fix this problem. However it doesn't.. It's
supposed to set "number of seconds before connection attempt times out.
Default itmeout is 10 seconds". As you can see by the output below it's
still timing out after 10 seconds. Is this set someplace else? And yes I did
restart Nagios..
 
 
# 'check_nrpe' command definition
define command{
        command_name    check_nrpe
        command_line    /usr/local/nagios/libexec/check_nrpe $HOSTADDRESS$
-c $ARG1$ -to 2700
        }
[root at PS-NAT etc]# ../libexec/check_nrpe 10.1.82.31 -c check_mailsendeta
CHECK_NRPE: Socket timeout after 10 seconds.
 
 
Gerald Wichmann
Senior Systems Development Engineer
Zantaz, Inc.
925.598.3099 (w)
 


This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com. 
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communication in error, please notify the sender immediately by
telephone or directly reply to the original message(s) sent.  Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20021121/79be67d7/attachment.html>