Page 2 of 2

Re: Monitoring Windows Event Logs

Posted: Thu Feb 03, 2011 3:10 pm
by rdedon
could you try retarting xinetd:

Code: Select all

service xinetd restart
and verifying that your daemon is listening on the correct port for nsca

Code: Select all

netstat -aunt
There should be a result similar to:

Code: Select all

tcp             0                 0   0.0.0.0:5667               0.0.0.0:*            LISTEN
please respond with results when possible.

Thanks!

Re: Monitoring Windows Event Logs

Posted: Mon Feb 07, 2011 10:01 am
by josh.rodriguez
Here are the results:

tcp 0 0 0.0.0.0:5667 0.0.0.0:* LISTEN

-Josh

Re: Monitoring Windows Event Logs

Posted: Tue Feb 08, 2011 11:32 am
by rdedon
Could you run this from a command prompt o the client machine (Windows):

Code: Select all

net stop NagiosEventLog
net start NagiosEventLog
Also restart the Host (Nagios XI) service and see if this helps any.

Re: Monitoring Windows Event Logs

Posted: Fri Apr 26, 2013 8:34 am
by WillemDH
Hello,

I have the same iisue as Josh. When trying to test the NCSA daemon, I get Error: Could not connect to host (ip address Nagios XI server) on port 5667.

When executing netstat -aunt, on of the results is

tcp 0 0 0.0.0.0:5667 0.0.0.0:* LISTEN

the server from whom I try to connect is in the only_from list...

# default: on
# description: NSCA (Nagios Service Check Acceptor)
service nsca
{
flags = REUSE
socket_type = stream
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/nsca
server_args = -c /usr/local/nagios/etc/nsca.cfg --inetd
log_on_failure += USERID
disable = no
only_from = xx.xx.18.70 xx.xx.17.27
}

I reall need to get NCSA working. I've restarted the Nagios XI server, the Nagios eventlog service on the server.

Any help is welcome.

Willem

Re: Monitoring Windows Event Logs

Posted: Fri Apr 26, 2013 9:23 am
by slansing
Locking this thread, we will continue working on this in your new thread.