> Boyer, Timothy A. wrote: >> >> I'm getting the usual nrpe timeout on a slow network here. Error >> messages says >> >> CHECK_NRPE: Socket timeout after 30 seconds. >> >> And normally know how to fix it. The really strange thing is that the >> client has timeouts set to 60 in nrpe.cfg: >> >> command_timeout=60 >> >> and the nrpe call itself is being done with a timeout of 60: >> >> command_line $USER1$/check_nrpe -H cabot -t 60 -c check_local_info >> >> with the check_local_info being my own shell script. >> >> So is there another place that the '30' timeout could possibly be >> coming from? >> >> Thanks much... >>
> On "cabot" check the time out definition in the nrpe.cfg of the daemon , > that may be the reason for the 30 sec time out. > > Change it to the time you want and restart the NRPE . > > Assaf Cabot nrpe.cfg already has the command_timeout=60 line in it (and, yeah, I restarted nrpe). That's what's driving me nuts. Tim ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Nagios-users mailing list [email protected] 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
