8.7.1  Bypassing The System Error Log

Use the following command to test SEA without sending an event through the system error log:

wsea test nosystem

The Director must be running in order to use the test nosystem command.

The nosystem option sends an event directly to the SEA event reader, bypassing the system altogether. This command is used to facilitate troubleshooting of a problem and determine if it is caused by SEA.

Regardless of the platform, the command creates a mock CEH for the event so that it can be recognized. Since SEA also requires an NT event header when running on Windows platforms, a mock NT header also is created when the command is executed on an Windows system. Only the NT header fields necessary for translation, analysis, and human identification are populated with valid values. Fields set to 0 or NULL do not affect translation or analysis.

Since the event created by the nosystem option has a CEH (and for Windows, a NT header as well), it should always be recognized by SEA. However, since the event is never appended to the system error log, it cannot be seen when manually translating or analyzing the system error log. In addition, the problem report immediately expires and, as a result, it will not appear if you subsequently run the wsea report command. The only ways to view the problem report generated by analysis is by using the "Real Time Monitoring" view in the web interface, or the problem report logging functionality (see Section 5.6.1.2). The wsea report command will not show the problem report because it is designed to expire immediately.

Note


The nosystem option creates an event that can be translated and analyzed for all the supported operating systems, regardless of whether or not the hardware platform is supported.