This may be a bit off track but.. On our unix boxes we have always had /usr/sbin/ndd -set /dev/tcp tcp_close_wait_interval 2400 In user_apps.dat This goes back 10+ years but it was a fix for data for windows flat lining I cant remember much more detail but if we forgot to put it back in after an update the AW would fill up with CLOSE WAIT's -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Johnson, David Sent: Saturday, 16 March 2013 02:29 To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] AIM*OPC Server CLOSE_WAIT errors Hi guys, I'm still trying to determine what's wrong with our AIM*OPC. I'm looking at the an_init.tcp file from /opt/aim/bin and SRVONE (the AW I am on) is the only Foxboro workstation listed in the file. So there goes that theory. I did a little reading on the CLOSE_WAIT tcpip condition and this is what I found. CLOSE_WAIT Indicates that the server has received the first FIN signal from the client and the connection is in the process of being closed So this essentially means that this is a state where socket is waiting for the application to execute close() A socket can be in CLOSE_WAIT state indefinitely until the application closes it. Faulty scenarios would be like filedescriptor leak, server not executing close() on sockets, leading to pile up of close_wait sockets. Although I understand all the words, I don't know how to fix it, or even if it's the real problem. But it is certainly suspicious. We will continue to investigate. Thanks to all who have responded. David Confidentiality Notice: The information contained in this message is private and confidential. This information is intended only for the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, review, dissemination, distribution, copying or action taken based on this message or its attachments, if any, is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and delete or destroy all copies of this message and any attachments. Thank you. _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave NOTICE - This message and any attached files may contain information that is confidential, legally privileged or proprietary. It is intended only for use by the intended recipient. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, be advised that you have received this message in error. Any dissemination, copying, use or re-transmission of this message or attachment, or the disclosure of any information therein, is strictly forbidden. BlueScope Steel Limited does not represent or guarantee that this message or attachment is free of errors, virus or interference. If you have received this message in error please notify the sender immediately and delete the message. Any views expressed in this email are not necessarily the views of BlueScope Steel Limited. _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave