Passive checks with NSCA
Colin A. White
colin at trematon.com
Thu Dec 4 20:14:56 CET 2003
I have set the same password and decrypt method=1 in both nsca.cfg and
send_nsca.cfg.
For testing, I also entered the currently assigned dynamic IP address of
the remote host running send_nsca to allowed_hosts in nsca.cfg on the
nagios host (though this isn't going to work for me long term)
I set nsca.cfg debug=1 and can see the debug entries in my
/var/adm/messages (yes, I'm running Solaris on the nagios end)
> Dec 4 18:47:51 falun nsca[9868]: [ID 601491 daemon.notice] Starting
> up daemon
> Dec 4 18:48:14 falun nsca[9868]: [ID 862360 daemon.error] End of
> connection...
The 2nd entry appears when I attempt to run send_nsca which eventuall
ends with :
> Error: Timeout after 10 seconds
Not exactly detailed/verbose error messages to work with...
Can anyone suggest what's happening here?
Thks
Colin
>>>Error: Server closed connection before init packet was received
>>>Error: Could not read init packet from server
>>>
>>>
>>I've had my firewall admin open tcp-5667 to the nagios host. Should
>>this have been udp-5667 ??
>>Any suggestions on how to pursue this cryptic error msg?
>>
>>
>
>It's TCP. Is there anything in /var/log/* on the server running the NSCA
>daemon? Did you remember to add the IP of the host sending the checks to
>allowed_hosts in nsca.cfg (and restart NSCA if necessary). Consider
>turning on debugging in nsca.cfg also. I presume that you're using the
>same password and encryption/decryption method on both machines.
>
>--
>Marc
>
>
>
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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