NSCA Time Out
Morris, Patrick
patrick.morris at hp.com
Fri May 5 21:12:38 CEST 2006
OK, that still leaves one question (I feel like a dentist):
>> If standalone, is the nsca server configured to allow connections
>> from your clients?
This would be "allowed_hosts" in the nsca config file.
At this point, It might be good to add the questions:
Have you tried enabling debugging in the nsca config?
What does your nsca config look like, anyway?
Can you telnet to port 5667 on the nsca server?
-----Original Message-----
From: Ian Marks [mailto:imarks at comcast.net]
Sent: Friday, May 05, 2006 12:05 PM
To: Morris, Patrick
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] NSCA Time Out
When I run it manually, it times out after 10 seconds.
I have iptables allowing port 5667 from the distributed server and no
tcp wrappers enabled.
I have enabled debug for nsca on the central server. According to
/var/log/messages events are getting to the server, but just not being
read by nagios.
Morris, Patrick wrote:
> OK, that still leaves a couple important questions:
>
>
>> What happens if you run it manually as the Nagios user?
>> If standalone, is the nsca server configured to allow connections
>> from
>>
>
>
>> your clients?
>>
>
> -----Original Message-----
> From: Ian Marks [mailto:imarks at comcast.net]
> Sent: Friday, May 05, 2006 11:47 AM
> To: Morris, Patrick
> Cc: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] NSCA Time Out
>
> 1. It times out at 10 seconds. I also tried setting ocsp_timeout=30.
> 2. I'm really not sure what log to look at on the server side, I was
> basing the connection established on tcpdump after seeing a handshake
> take place.
> 3. nsca is running under init.d as a service.
>
> Morris, Patrick wrote:
>
>> What happens if you run it manually as the Nagios user?
>>
>> What, if anything, appears in the logs on the server side?
>>
>> How are you running nsca? inetd? Standalone?
>>
>> If standalone, is the nsca server configured to allow connections
>> from
>>
>
>
>> your clients?
>>
>> Give us something to work with here.
>>
>> -----Original Message-----
>> From: nagios-users-admin at lists.sourceforge.net
>> [mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of Ian
>> Marks
>> Sent: Friday, May 05, 2006 11:20 AM
>> To: nagios-users at lists.sourceforge.net
>> Subject: [Nagios-users] NSCA Time Out
>>
>> I'm having an issue with nsca in a distributed setup. I keep getting
>> the following error
>> "Warning: OCSP command
>> '/usr/local/nagios/libexec/eventhandlers/submit_check_result_nsca
>> /host_name/ 'Check Ping Service' OK '$OUTPUT$'' for service 'Check
>> Ping Service' on host '/host_name/' timed out after 5 seconds"
>> I see the initial connection on the central server get established,
>> so
>>
>
>
>> I was assuming it was an encryption issue. For troubleshooting
>> purposes, I have disabled encryption, but still see the same error.
>>
>> I have the following defined on the
>> ##distributed server.
>> in nagios.cfg
>> obsess_over_services=1
>> ocsp_command=submit_check_result_nsca
>>
>> in checkcommnands.cfg
>> define command{
>> command_name submit_check_result_nsca
>> command_line
>> /usr/local/nagios/libexec/eventhandlers/submit_check_result_nsca
>> $HOSTNAME$ '$SERVICEDESC$' $SERVICESTATE$ '$OUTPUT$'
>> }
>>
>> ##central server
>> all services and hosts have been defined for the remote server, nsca
>> is running, passive checks are enabled, and iptables rules have been
>> set to allow the connection.
>>
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
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