Network tuning for Nagios with slave servers

[Andreas Ericsson]

Wheeler, JF (Jonathan) wrote:
> Our configuration is quite large (830 hosts, 160700+ services),

You run more than 193 checks against each host? Good gods, you must
be *really* curious about the state of those hosts :)

> so have
> implemented a master/slave configuration for Nagios (the Nagios servers
> are running Linux).  The master server only runs checks if a check
> becomes stale; i.e. it should have been checked by a slave but no result
> has been received, but I find that (for example), in the last days log
> there are 80,000 + warning messages saying the master has run a check
> because it has become "stale".  On further investigation I find that on
> all of our 5 slaves the command netstat shows that there are a large
> number of TCP sockets in CLOSE_WAIT state (more .  My question is, has
> anyone done any network tuning to improve Nagios network performance ?
> 

Nope, but you could try doing

	sysconf net.ipv4.tcp_fin_timeout=30

to halve the default tcp timeout in the kernel, which should reduce
the number of half-open connections you have.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at 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