HP StorageWorks XPath OS 7.4.X Administrator Guide (AA-RVHDD-TE, February 2006)

96 Monitoring system logs
Viewing the system error log
The system error log is a collection of all daemon-related errors (such as memory allocation errors), as well
as all events from the event log.
1. Log in as user or admin.
2. Issue the errShow command:
The system error log content is displayed, with page breaks.
Alternatively, you can use the -a option to display the system error log content without page breaks:
Sample system error log message
The following is a sample message from the system error log:
The fields in the event message are described in Table 13.
Table 12 Message severity levels
Event level Description
0 = Panic Panic messages indicate that a specific software subsystem has detected a fatal or
unrecoverable error condition. Examples are memory allocation failure, system call
failure, and software detection of problems with the ASIC or with hardware
subsystems. These errors usually indicate partial or complete failure of a subsystem.
1 = Critical Critical messages indicate that the software has detected serious problems that
eventually cause a partial or complete failure of a subsystem if not corrected
immediately. A power supply failure, for example, or a rise in temperature must
receive immediate attention. Some of the critical errors might overlap in severity
with the panic messages.
2 = Error Error messages indicate error conditions that do not significantly affect overall
system functionality. For example, error messages might indicate time-outs on
certain operations, failures of certain operations after retries, invalid parameters,
or failures to perform requested operations.
3 = Warning Warning messages highlight current operating conditions that should be checked
before they cause failures. For example, a power supply failure in a redundant
system relays a warning that the system is no longer operating in redundant mode,
and that the failed power supply should be replaced or fixed.
4 = Info Info messages report the current status of the system components other than error
status. For example, detecting on and off line status of a fabric port.
5 = Debug Debug messages are for debugging use only. They are produced by code inserted
by the vendor to inform the user that a suspected problem has occurred.
router:admin> errshow
router:admin> errshow -a
router:admin> errshow
Error 239
----------
301 (EvtMgr): Jan 26 13:10:34
Info CM-EVENT_USER_LOGIN_SUCCESS, 4, User login: admin