1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: alh not handling log files correctly |
From: | Chris Timossi <[email protected]> |
To: | Janet Anderson <[email protected]> |
Cc: | TECHTALK <[email protected]> |
Date: | Mon, 05 Nov 2007 09:55:45 -0800 |
If I remember correctly, the alarm log and the current alarm history display
new alarm events (changes in alarm fields STAT and SEVR) as they happen.
Existing alarms are not logged when the alarm handler starts up because they
are not new alarm events.
The -T command line option from DESY creates alarm log files with special
dated names which are automatically switched at midnight. This option must
conflict with the runtime log file name change option.
An -xml command line option was added to alh by SNS. If this flag exists
alh will use XML-ish format for log files and will print "XML!" to stdout.
If it is not present, alh prints "no XML!" .
Janet
Chris Timossi wrote:
I've downloaded an built alh1_2_23 for Red Hat Enterprise Linux.
There are several problems related to viewing / changing the alarm log file. It actually crashes if I attempt to specify a new alarm log file:
Setup -> New Alarm Log File Name
============================
crconlnx1.als.lbl.gov% ./alh.sh &
[1] 32688
crconlnx1.als.lbl.gov% no XML!
*** glibc detected *** free(): invalid next size (fast): 0x0839e748 ***
./alh.sh: line 10: 32689 Aborted alh -f /home/als/alsoper/alh -l /home/als/alsoper/alh/logs -global -m 0 -L -T als.alhConfig
============================
The View->Current Alarm History shows a blank window even though there are active alarms.
The View->Alarm Log File Window also seems to be missing items. Again, there is a PV in major alarm that I would expect to see in the log file.
Is the 'no XML!' message important?
Chris Timossi ALS/LBNL