<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>Nachricht</TITLE> <META content="MSHTML 6.00.2800.1528" name=GENERATOR></HEAD> <BODY> <DIV>I had this problem like others, too. I paste som archive-mail concerning this issue: (but none of them helped with my probs or i didn´t try the solutions. the problem cleared itself, don´t ask my why), You´ll find more searching the archives for "timeout", good luck :)</DIV> <DIV> </DIV> <DIV>Andreas Ericsson wrote:</DIV> <DIV> PEYRE Julien wrote: > Hello everybody, > > I'm trying to use Nagios in order to survey our databases with custom > plug-in. On Nagios browser, if I choose a host and I launch "Schedule > an immediate check of all services on this host", I have all status > for all services that take value " CHECK_NRPE: Socket Timeout after 10 > seconds". > > If I launch an immediate check service by service (one by one), it's > OK, it functions. > > Any idea would be welcome ! > You're most likely flooding the socket receive buffers in the kernel. What systems are you seeing this on and how many checks are there to run? Most systems have an accept(2) queue size of five, so above that and you're in uncharted territory unless you fiddle with the receive-buffers directly through fcntl(2) in which case it should be possible to set it to some quite large value (see check_icmp.c on how to do this).</DIV> <DIV> </DIV> <DIV> </DIV> <DIV>Another one:</DIV> <DIV> Thomas.Zimmer@oppenheim.de wrote: > Hi Andreas, > Many thanks for the solution of the timout-prob. Do you think the > modification the socket receive buffers could cause undesireble > consequences for the system nagios is running on? The program enhancing the buffers will ofcourse consume more memory. On some systems this comes from the kernel's pre-allocated chunks which it is either expensive or impossible to grow. Since it's only one program and one socket though it shouldn't make much difference. > Any security-related issues? Not with a sane implementation which most systems have these days. Ancient True64 had some problems, as did HPUX and UniCOS. To my knowledge this has been fixed though (except possibly UniCOS which I doubt you're running).</DIV> <DIV> </DIV> <DIV>And this one </DIV> <DIV> Hello everybody, I'm trying to use Nagios in order to survey our databases with custom plug-in. On Nagios browser, if I choose a host and I launch "Schedule an immediate check of all services on this host", I have all status for all services that take value " CHECK_NRPE: Socket Timeout after 10 seconds". If I launch an immediate check service by service (one by one), it's OK, it functions. Any idea would be welcome ! Thanks in advance, Julien. </DIV> Thomas Zimmer Produktservice & Betrieb Betrieb & Support Sal. Oppenheim jr. & Cie., Frankfurt a. Main Telefon: +49 69 7134 5192 Internet: <A href="http://www.oppenheim.de/">http://www.oppenheim.de</A> E-Mail: thomas.zimmer@oppenheim.de <BLOCKQUOTE style="MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=OutlookMessageHeader lang=de dir=ltr align=left>-----Ursprüngliche Nachricht----- Von: nagios-users-admin@lists.sourceforge.net [mailto:nagios-users-admin@lists.sourceforge.net] Im Auftrag von Larry Ludlow Gesendet: Donnerstag, 13. April 2006 19:54 An: nagios-users@lists.sourceforge.net Betreff: Re: [Nagios-users] Strange NRPE / Nagios problem </DIV>Here are some of my configs... comands.cfg define command{ command_name check_sun_disk1 command_line $USER1$/check_nrpe -n -H $HOSTADDRESS$ -t 30 -c check_disk1 } nrpe.cfg command[check_disk1]=/export/nagios/libexec/check_disk -w 20 -c 10 -p /dev/vx/dsk/rootvol service for this particular host define service { use check_sun_disk1 service_description / check_command check_sun_disk1 host_name ######## servicegroups Sun contact_groups LAdmins } I can run this command manually. When nagios performs the check I get a socket time out... I am getting very frustrated... I have used nagios for a few years now.. and this is the 1st time I have ran into this problem... there are no firewalls, iptables, filtering or anyhting running on these boxes yet.... </BLOCKQUOTE></BODY></HTML>