Filter
Top Products
System Event Analyzer
2.3 SEA Known Issues
Rev. 9/8/06
2–8 Web-Based Enterprise Services Release Notes
2.3.1.9 SEA Problem Reports Not Received by OSEM
You may see an error similar to the following in the Director error log (see the section on log
files in the WEBES User Guide, Chapter 2):
RECOVERED FROM ERROR on January 13, 2004 4:48:05 PM GMT+00:00 (254.912
sec elapsed)
IOException :
Current Thread[Thread-29:
com.compaq.svctools.desta.services.notification.HTTPNotification
,5,main]
EXCEPTION java.net.ConnectException: Connection refused at
java.net.PlainSocketImpl.socketConnect(Native Method)
One cause is when WEBES cannot connect to the OSEM host because OSEM Viewer access
has been restricted. This is a known issue from the latest OSEM release notes.
Workaround
Any time that you restrict access by adding at least one system to the Enabled Clients list in
the OSEM Viewer, you also must add WEBES systems as “enabled clients” before problem
reports from those systems can appear.
To add enabled clients, see the “controlling access” section in the latest OSEM user guide.
To verify that OSEM is receiving SEA problem reports, use the SEA wsea test nosystem
command to generate a simulated problem report.
2.3.2 SEA Command Line Interface Issues
These issues apply to the SEA CLI on all operating systems:
2.3.2.1 .ca Command Changed to wsea
The command prefix used with the command line interface has changed from ca to wsea. In
this version, commands can be entered using either prefix; however, future releases will not
support the
ca prefix.
2.3.2.2 Entering Commands
Because of differences in the command prompts on each operating system, CLI commands
may not be exactly the same across systems. The following instructions describe special
formatting issues for each operating system.