Problem Solving and Troubleshooting in AIX 5L - IBM Redbooks

Resource Name: errdemon
Description
ERROR LOGGING TURNED ON
► To display a detailed report of all errors logged for a particular error identifier,
enter the following command:
# errpt -a -j identifier
Where identifier is the eight digit hexadecimal unique error identifier.
► To clear all entries from the error log, enter the following command:
# errclear 0
► To stop error logging, enter the following command:
# /usr/lib/errstop
► To start error logging, enter the following command:
# /usr/lib/errdemon
► To list the current setting of error log file and buffer size and duplicate
information, enter the following command:
# /usr/lib/errdemon -l
If you want to change the buffer size and error log file size, you can use the
errdemon command. For further detail, refer to the manual page for errdemon.
Note: When you remove the errlog file accidently, use the /usr/lib/errstop
and /usr/lib/errdemon commands in sequence to recover the file. errdemon
creates the errlog file if the file does not exist.
Software service aid configuration information is stored in the
/etc/objrepos/SWservAt ODM database. This ODM class is used to store
information about the location and size of various log files used by the system. It
is also used to hold information about trace hooks available for use by the trace
subsystem, described in Chapter 11, “Event tracing” on page 341.
By default, AIX runs a cron job that deletes all hardware error log entries older
than 90 days daily at 12 AM and all software and operator message error log
entries older than 30 days daily at 11 AM. The cron job simply uses the errclear
command to delete the old entries. If you are investigating a software problem
that has been on a machine for a long time, do not assume that the first instance
of the error in the error log was caused the first time the software problem
occurred. Previous entries may have been deleted if older than 30 days.
Chapter 2. Error logging 25