NSCA : Time out

[trm asn]

On Mon, Jul 16, 2012 at 2:08 AM, trm asn <trm.nagios at gmail.com> wrote:

> Dear Team,
>
> I am getting the below error message while pushing the results to central
> nagios. I am able to telnet 5667 from Monitor node to central server. in
> Tcp-Wrapper this ip is allowed .
>
> The results are not getting updated due to this. Please help me out to
> sort this ..
>
> Warning: OCSP command
> '/mnt/vol1/nagios/libexec/eventhandlers/submit_check_result
> Lnx-ProdDatabase1 'Checks if the SQL Slave thread is running' OK 'OK -
> Slave io is running'' for service 'Checks if the SQL Slave thread is
> running' on host ' Lnx-ProdDatabase1' timed out after 10 seconds .
>

Still not able to figure out , where is the actual problem is.

i) I am able to telnet to central server's 5667 port .
ii) I am able to test it from commandline ..
 echo "testhost    TestService     0    OK" |
/mnt/vol1/nagios/libexec/send_nsca -H x.x.x.x -p 5667 -c
/mnt/vol1/nagios/etc/send_nsca.cfg
0 data packet(s) sent to host successfully.

Is there anywhere else , I need to lookout to get the result submitted to
the central server.

/\
TRM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120717/0cd739cd/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
-------------- next part --------------
_______________________________________________
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