Re: [foxboro] OM lists

  • From: "Brown, Stanley" <stan.brown@xxxxxxxxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Tue, 24 Aug 2010 11:07:31 -0400


> -----Original Message-----
> From: Stan Brown [mailto:stanb@xxxxxxxxx] On Behalf Of
> duc.do@xxxxxxxxxxxxxx
> Sent: Tuesday, August 24, 2010 10:59 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] OM lists
>
> Stan,
>
> Do the operators use DM from this AW to run the process and receiving
> alarms?

No, but..

It is used for remote DM access for management. We have recently changed this 
from a X based method to a VNC based method. I need to check and see if an AM 
is started for this session. I do not think it is, but if it is, then we might 
be suffering from the issue you mention.

>
> We experienced something like this, and traced the problem back to the
> alarm manager (AM) display being open and closed, as is the practice
> with our operators. It doesn't happen all the time, but many times when
> the AM display is X'ed out, it leaves an OM list of two objects. And
> these lists "orphan" lists hang around until the AW exhausts it limit
> of OM lists.
>
> Rebooting the AW does fix this problem as the OM table gets wiped
> clean. A less intrusive tactic involves searching for the orphan OM
> lists and close them out. Jeremy Milum wrote a C program to close the
> orphan lists. I stole it and a script file from him and modified to
> work for our site. I run this script about once a week. (I'll send you
> both off-list.)

That would be greatly appreciated.

>
> You can search the freelists.org archive for "orphan OM lists" for the
> discussion about this problem back in 2005.
>
> Duc
>
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-
> bounce@xxxxxxxxxxxxx] On Behalf Of stan
> Sent: Tuesday, August 24, 2010 10:42 AM
> To: Foxboro List
> Subject: [foxboro] OM lists
>
> WE had an instance where we ran out of OM lists last night. Foxboro TAC
> logged in and determined that the AW on this node was using too mangy,
> and
> we resolved the issue (for the moment) by rebooting this machine.
>
> However,, I am not convinced we have found the root cause on this. The
> configuration on this node has been stable for quite a while, and the
> last
> time the AW was rebooted was 150+ days ago, after an upgrade to 7.1.5
> software.
>
> We have run a variant of the checkit script from the Casandra site for
> a
> number of years, and it uses /usr/local/show_params to report on some
> OM
> statistics. Frankly I am not all that familiar with the output of this
> section of the report. Can someone tell me if these values are global
> to
> the node? If not, is there a script that I can run to get statistics
> for a
> specific station (AB integrator 30A in this case).
>
> Thanks for any suggestions as to forensics on this.
>
> --
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
>
> _______________________________________________________________________
> 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
>


The information contained in this message and any attached files may be 
privileged and/or confidential and protected from disclosure. If you are not 
the intended recipient, any disclosure, copying, distribution or use of any of 
the information contained in or attached to this transmission is strictly 
prohibited. If you have received this transmission in error, please so notify 
the sender immediately without reading it. Also, please promptly destroy the 
original transmission and its attachments. Any views or opinions presented in 
this message or attachments are those of the author and do not necessarily 
represent those of KapStone Paper and Packaging Corporation or its subsidiaries.
 
 
_______________________________________________________________________
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:

  1. Home
  2. foxboro
  3. Archive
  4. 08-2010