Re: [foxboro] AIM*OPC Server CLOSE_WAIT errors
- From: Michael Toecker <michael.toecker@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 14 Mar 2013 15:34:55 -0500
Was the PI server recently upgraded to Windows 2008 R2, or received
patches? I"m working a theory here.
In the meantime, you can use TCPView from Microsoft Sysinternals to
!!!!CAREFULLY!!!! kill zombie (close_wait) connections on a periodic basis.
(http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx)
Mike Toecker
Digital Bond, Inc
On Thu, Mar 14, 2013 at 12:57 PM, Ted Jirik <ted.jirik@xxxxxxxxxxxxxxx>wrote:
> David,
>
> Also be sure there is nothing in the AIM* Servers field in the opc server
> configurator / server parameters (advanced) tab
>
> Ted
>
> On Mar 14, 2013, at 10:37 AM, Ted Jirik <ted.jirik@xxxxxxxxxxxxxxx> wrote:
>
> > David,
> >
> > Just spoke to our field service rep and he verified my thinking. That is
> what we did to solve it at two sites.
> >
> > Reboot after changes?
> >
> > Be sure other servers are not listed in your an_init.tcp file?
> >
> > Ted
> >
> > On Mar 14, 2013, at 8:48 AM, "Johnson, David" <
> David.Johnson@xxxxxxxxxxxxxxxxxx> wrote:
> >
> >> Ted,
> >>
> >> That sounds like a potential problem, but we checked, and the disable
> broadcast box was checked in APIAdmin on ALL of the AWs listed. We only
> have AIM*OPC Server on SRVONE, there are no other OPC servers or clients on
> the DCS network. So I still don't know why the AIM*OPC Server is
> attempting to talk to the other AWs. And although I only listed 2 sample
> netstat lines with the CLOSE_WAIT there are many, possibly hundreds, to
> each AW after a few days.
> >>
> >> Any other ideas?
> >> Thanks,
> >> David
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Ted Jirik
> >> Sent: Thursday, March 14, 2013 9:32 AM
> >> To: foxboro@xxxxxxxxxxxxx
> >> Subject: Re: [foxboro] AIM*OPC Server CLOSE_WAIT errors
> >>
> >> David,
> >>
> >> We had the same problem. As I recall we had to disable broadcast
> requests under edit server connection in apiadmin. We did this on all
> stations and the problem went away.
> >>
> >> Ted
> >>
> >> On Mar 14, 2013, at 6:25 AM, Johnson, David wrote:
> >>
> >>> Hello All,
> >>> We have an AIM*OPC server installed on an AW running Win 2003 Server.
> The OPC server is working (will return data, no errors). We have an OSI PI
> data collector running. It will connect to and get data from I/A via the
> OPC link. This will work for several days, but then the AW becomes so
> unresponsive, it must be rebooted. After a reboot the problem goes away
> for a day or two, and then returns.
> >>>
>
>
> _______________________________________________________________________
> 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
>
>
--
Michael Toecker
Head Dragon Slayer
_______________________________________________________________________
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:
