Service and host check plugins are responsible for implementing their own timeouts, not Nagios. This socket timeout must be specific to the plugin you are using for the service. The timeouts in nagios.cfg are backstops that prevent "stuck" plugins from tying up Nagios resources. You should look at the command or service definition in your other config files and/or the plugin itself to see where and how this timeout is defined.
Andre Tann wrote: > Hello everyone, > > some of my services report a socket timeout after 5 seconds. How can I > increase this value to 10 secs? > > # grep -i timeout /etc/nagios3/nagios.cfg > # TIMEOUT VALUES > service_check_timeout=60 > host_check_timeout=30 > event_handler_timeout=30 > notification_timeout=30 > ocsp_timeout=10 # <- has been 5 before > perfdata_timeout=10 # <- has been 5 before > > > In the last two lines there was a value of 5, and I changed it to 10. > This didn't help, which surprises me not much, as the problem isn't ocsp > or perfdata related. > > In my understanding the timeout should be 60 secs as in > service_check_timeout, but it is 5 secs as noted before. > > Where do these 5 secs come from? > ------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 _______________________________________________ Nagios-users mailing list Nagios-users@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
