NSCA Error timeout after 10 seconds
Mark Nadir
mnadir at sympatico.ca
Tue Dec 7 17:03:28 CET 2004
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.
Any thoughts?
M.
Sloane, Robert Raymond wrote:
>The NSCA daemon has a debug option in the config file. Have you tried
>turning it on and then connecting to see what shows up in syslog?
>Usually when there is a problem with the handshake you don't get a
>timeout. Is it possible there is some sort of firewall blocking the
>connection? What happens if you just telnet to the NSCA port from the
>client system?
>
>
-------------------------------------------------------
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
More information about the Users
mailing list