Re: [foxboro] Alarm History Update Problem
- From: stan <stanb@xxxxxxxxx>
- To: Ali Ahmed <alizahidi@xxxxxxxxxxx>
- Date: Fri, 30 Dec 2005 08:34:52 -0500
On Fri, Dec 30, 2005 at 10:04:48AM +0000, Ali Ahmed wrote:
> Hi All,
> We have three WP51Ds connected with an AW51E on nodebus. We are facing alarm
> history update problem on alarm history display page on two of the three
> WPs. When we call alarm history page from Current Alarm Display (CAD) the
> following error message appears.
>
> "Unable to open alarm history file for hist02 on 03AW02"
>
>
> where, hist02 is our historian instance name and 03AW02 is letter ID of our
> AW51E. To rectify this problem we rebooted the WPs but the problem remains
> same. We cannot reboot the AW for some time due to some reason. Is there any
> way to get rid of this problem without rebooting AW. Kindly advise.
>
This sounds similar to, but not exactly the same as a problem we had on one
of our nodes.
After a period of time, we were unable to open the CAD on some of our WP's.
In our case it turned out that one of our cleanup scripts was removing
"stale" files in /tmp/ Files of names similar to _amAMA403 are created at
boot time, and are the license files for the alarm handling software.
removing these files will prevent the CAD from starting.
However, in our case rebooting the WP's caused these to be created in
normal system startup, and all was well, until we shot ourselves in the
foot with the cleanup scripts.
Check on the WP's and make certain you have these files.
But, I think you must have a different problem.
--
U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong
Terror
- New York Times 9/3/1967
_______________________________________________________________________
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: http://www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
- References:
- [foxboro] Alarm History Update Problem
- From: Ali Ahmed
Other related posts:
- » Re: [foxboro] Alarm History Update Problem
- » Re: [foxboro] Alarm History Update Problem
- » Re: [foxboro] Alarm History Update Problem
- [foxboro] Alarm History Update Problem
- From: Ali Ahmed