Dear All,

We have an NSCA server which is having too many connections in CLOSE_WAIT 
state. 
Because of too many connections the NSCA is not responding to the packets 
coming.

Increasing the time out option has not solved the problem :-( 

How to resolve this issue? Has any one come across this error before? 

Is there an upper limit to the number of connections NSCA can handle?

We are using Nagios 3.0.3 and NSCA 2.7.1

Thanks
Ankit Arun Mehrotra
Tata Consultancy Services
54, Hadapsar Industrial Estate,
Hadapsar,
Pune - 411 013,Maharashtra
India
Ph:- (020)-6608 6254
Buzz:- 420 6254
Cell:- 9881108390
Mailto: [EMAIL PROTECTED]
Website: http://www.tcs.com
____________________________________________
Experience certainty.   IT Services
                        Business Solutions
                        Outsourcing
____________________________________________
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
[email protected]
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

Reply via email to