Re: [foxboro] AIM*OPC Server CLOSE_WAIT errors
- From: Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 15 Mar 2013 22:13:22 +0800
I had a very similar problem with Aim_OPC occasionally at my last site -
clients were Metso OCS APC applications. We'd encounter the problem about
once a month - symptom was a bunch of close_wait sockets. We normally
rebooted the OPC server to correct. Never did get it resolved.
Cheers,
Kevin
On Fri, Mar 15, 2013 at 9:29 PM, Johnson, David <
David.Johnson@xxxxxxxxxxxxxxxxxx> wrote:
> 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
>
>
_______________________________________________________________________
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
Other related posts:
