NSCA Error timeout after 10 seconds

[Andreas Ericsson]

Mark Nadir wrote:
> Hi Robert,
> 
> Thank you for your response. Whenever I try to telnet to the port, I can 
> connect to it. So, it is a pretty good chance that my firewall is 
> allowing TCP over 5667 to connect.
> 
> I turned on debugging, and tried to use the remote client to send to 
> NSCA daemon, however nothing shows up in syslog.
> 
> What's interesting is that if I try to use the client on the same 
> machine that the NSCA daemon is running, and I connect to localhost 5667 
> syslog returns a messaging saying that it is Deactivating the NSCA due 
> to excessive incoming connections -restarting in 30 seconds.
> 

The fact that the port is listening has nothing to do with nsca if 
you're using inetd to front it. inetd listens on the port and delivers a 
socket to the program in the other end if it can complete the 3-way 
handshake.

If you've got a lot of passive checks reporting in you might want to 
either run nsca as a standalone daemon or increase the number of allowed 
connections within any specified time.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.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