CHECK NRPE time out after 50 seconds

[Lori Adams]

I wrote a small script to pipe the state and output to.  If the output
said "CHECK_NRPE: Socket timeout after 50 seconds", then exit(1).  

 

In the checkcommand is where you set up the pipe. 

 

define checkcommand {

            command_name            check_nrpe_ignore

            command_line               /your/path/to/check_nrpe -H
$HOSTADDRESS -c nrpe_command -a (if you have args) |
/your/path/to/nrpe/ignore/script $SERVICESTATE$

            }

 

The other option is to turn up your nrpe timeout, but that's not a very
good solution, as it just means it will take longer to timeout.

 

-Lori

 

________________________________

From: nagios-users-admin at lists.sourceforge.net
[mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of
mohamed.azizi at belgacom.be
Sent: Monday, October 03, 2005 1:20 AM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] CHECK NRPE time out after 50 seconds

 

 

Dear colleagues , 

I am using nagios 1.2 on linux  server to check process on both servers
which runs on linux. 
When we have lot of load  on the servers , Nagios receives check nrpe
time out after 50 seconds. 
After 3 times , this service is put on critical status .Normally , when
a check is on CRITICAL , Nagios launchs  a scripts to restart the system

and we have a lot of restart on each servers due to the timeout of
checknrpe. 
How can I avoid this kind of problem.I have increased the timer od NRPE
from 30 seconds to 50 seconds but without succes.

Can we configure nagios to have only warning state for a checknrpe
timeout 

Thanks for your support 

Mohamed 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20051003/fb4adea5/attachment.html>