Filter
Top Products
System Event Analyzer
2.3 SEA Known Issues
Rev. 9/8/06
Web-Based Enterprise Services Release Notes 2–25
# rm -rf /usr/opt/hp/svctools/specific/desta/data/managedentities/*.xml
3. Remove the DESTA.stat file.
# rm -rf /usr/opt/hp/svctools/specific/desta/data/DESTA.stat
4. 4. Restart the WEBES Director process.
#/usr/sbin/desta start
2.3.7 OpenVMS SEA Issues
These issues apply to SEA on OpenVMS:
2.3.7.1 ERRFMT May Create New Version of ERRLOG.SYS
During WEBES Processing
When the WEBES Director has the ERRLOG.SYS file open to do its processing, even though
WEBES opens the file read-only, VMS considers the file locked. The lock prevents the VMS
ERRFMT from writing a new event to the file.
Normally, this is not a problem, because ERRFMT will retry the write repeatedly for up to
about 6 minutes. Usually the Director only has ERRLOG.SYS open for a short time to read the
last event just written, or the last few events written since the Director was stopped.
If, however, the ERRLOG.SYS file is large, and the Director has the ERRLOG.SYS file open
long enough for all of the ERRFMT retries to fail (more than 6 minutes after the time
ERRFMT initially tries to write a new event), then ERRFMT will create a new file version of
ERRLOG.SYS. The cases that can cause this are:
1. the initial automatic analysis of the entire log file for the first time after WEBES is
installed, requiring processing of the entire log file, or
2. if the Director has been stopped for a long time and many events have been written to
ERRLOG.SYS while the Director was not running, then it can take a while to process the
new unprocessed events.
3. manual analysis of ERRLOG.SYS, either using the CLI ("wsea ana ..."), or the SEA Web
Interface (Full View). The threshold of how large an ERRLOG.SYS file or how many
events will trigger this condition varies depending on the speed and load of the VMS
machine.
Since the Director only reads the latest file version, it can "lose its place" at the moment the
new file version is created. An error message similar to the following may be logged to the
Director's DESTA_DIR.LOG file, or in the CLI output:
> > WARNING on November 23, 2005 4:19:25 AM MST (1129.661 sec elapsed)
> Error retrieving event EventDescriptor: CEH event
> originID: -1
> fieldNotFound: false
{ ... }
> EXCEPTION com.compaq.svctools.desta.services.JNIRoot.PrivException:
java.n
et.SocketException: broken pipe