FYI - SOLUTION: STALE Passive Results
Posted: Tue Nov 08, 2016 5:59 pm
IF you are using xinetd... with NSCA on your Nagios Server to RECEIVE passive results from either send_nsca or NSClient++ (running on Windows hosts)... Be AWARE of the following setting in the nsca config file in /etc/xinetd.d:
From the xinetd.conf (5) man page:
The key take-away from the man page... is the DEFAULT settings. 50 connections PER second... and then a time-out, go sit in the corner until you can play nicely, for 10 seconds.
IF you have a large number of computers, submitting passive results to your host... the default settings are most likely NOT going to suffice.
If you are seeing the following message in either your syslog (/var/log/messages), or the particular log file to which nsca writes:
FAIL: nsca connections per second
AND/OR this message in your nsclient.log file on your windows host(s):
error:c:\source\nscp\modules\Scheduler\Scheduler.cpp:122: Failed to submit ... : Error: Failed to connect to: nagioshost:5667 :No connection could be made because the target machine actively refused it
You'll most likely need to set or increase the 'cps' setting in the /etc/xinetd.d/nsca configuration file on your nagios host... and then restart xinetd
The following is a snippet from our config file:
KEYWORDS: stale passive refused xinetd nsca send_nsca "connections per second" "Failed to submit" "target machine actively refused it"
From the xinetd.conf (5) man page:
Code: Select all
cps - Limits the rate of incoming connections. Takes two arguments. The first argument is the number of connections per second to handle. If the rate of incoming connections is higher than this, the service will be temporarily disabled. The second argument is the number of seconds to wait before re-enabling the service after it has been disabled. The default for this setting is 50 incoming connections and the interval is 10 seconds.
IF you have a large number of computers, submitting passive results to your host... the default settings are most likely NOT going to suffice.
If you are seeing the following message in either your syslog (/var/log/messages), or the particular log file to which nsca writes:
FAIL: nsca connections per second
AND/OR this message in your nsclient.log file on your windows host(s):
error:c:\source\nscp\modules\Scheduler\Scheduler.cpp:122: Failed to submit ... : Error: Failed to connect to: nagioshost:5667 :No connection could be made because the target machine actively refused it
You'll most likely need to set or increase the 'cps' setting in the /etc/xinetd.d/nsca configuration file on your nagios host... and then restart xinetd
The following is a snippet from our config file:
Code: Select all
# default: on
# description: NSCA (Nagios Service Check Acceptor)
service nsca
{
disable = no
flags = REUSE
socket_type = stream
per_source = 500
instances = 2000
cps = 500 2
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/nsca
server_args = -c /usr/local/nagios/etc/nsca.cfg --inetd
log_type = FILE /var/log/nsca.log