Diagnosis Guide
This is the standard AIX error log located on the control
workstation. Use errpt -a to display entries. These are
hardware errors. An example would be an entry that indicates:
"Power module - DC power loss." Entries are logged when the condition
appears to be permanent.
The error information can be cleared. Do not clear it if an
error has occurred. The Detail Data in the error log entries comes from
catalogs, and will appear in the language specified by the SP administrative
locale on the control workstation. This table lists the Logging daemon
error log entries.
Table 56. AIX Error Log templates for the Logging daemon
| Label
| Error ID
| Type
| Class
| Description
|
| SPLOGD01_ERR
| E2ADA7BF
| UNKN
| S
| Explanation: splogd input file error.
Details: An error occurred opening or while processing the
splogd input file.
|
| SPMON_EMSG100_ER
| 4CEF5A08
| PERM
| H
| Explanation: Link error.
Details: The Logging daemon has detected that a frame is
not responding to the System Monitor daemon (hardmon) .
|
| SPMON_EMSG101_ER
| A1843F1E
| PERM
| H
| Explanation: Communication error.
Details: The Logging daemon has detected that a frame is
not responding, for a specific node, to the System Monitor daemon
(hardmon).
|
| SPMON_EMSG102_ER
| 001BB5DD
| PERM
| H
| Explanation: Communications subsystem failure.
Details: The Logging daemon has detected a problem with a
frame supervisor bus, or a supervisor card may not be seated properly.
|
| SPMON_EMSG103_EM
| 8D9F2E66
| PEND
| H
| Explanation: Equipment malfunction.
Details: The Logging daemon has detected a problem
somewhere in the hardware. For example, this could be a failure of a
fan, or a voltage or temperature going out of range.
|
| SPMON_EMSG104_EM
| 76A4FAD9
| PEND
| H
| Explanation: Impending workstation subsystem
failure.
Details: The Logging daemon has detected a hardware
problem. If the problem persists, it will cause the supervisor
subsystem to shut down the node.
|
| SPMON_EMSG106_ER
| E406336B
| PERM
| H
| Explanation: Resources not active.
Details: The Logging daemon has detected that a power
module is not installed.
|
| SPMON_EMSG107_ER
| F708903E
| PERM
| H
| Explanation: Loss of electrical power.
Details: The Logging daemon has detected that a power
module has failed.
|
| SPMON_INFO100_TR
| E720BFB5
| UNKN
| H
| Explanation: Power Off detected.
Details: The Logging daemon has detected that power has
been turned off for a frame, node or switch.
|
| SPMON_INFO101_TR
| 3E6F3CE7
| UNKN
| H
| Explanation: Power On detected.
Details: The Logging daemon has detected that power has
been turned on for a frame, node or switch.
|
| SPMON_INFO102_TR
| 93FA22BC
| UNKN
| H
| Explanation: Mux value set.
Details: The Logging daemon has detected that the mux value
of a switch has been set.
|
| SPMON_INFO103_TR
| 0D1620A8
| UNKN
| H
| Explanation: Threshold has been exceeded.
Details: The Logging daemon has detected that a threshold
value has gone out of range. The value could represent a voltage,
current, or temperature.
|
| SPMON_INFO104_TR
| E91A5929
| TEMP
| H
| Explanation: An error condition has been resolved.
Details: The Logging daemon has previously detected a
problem. However, the problem has subsequently been cleared. For
example, a voltage that has exceeded it's threshold value is now within
it's threshold value.
|
Examine the hwevents file at the time of the failure. To
determine where the hwevents file is located, issue the
command:
odmget -q 'subsysname=splogd' SRCsubsys
If the cmdargs entry of the output contains the "-f"
flag, the location of the hwevents file follows this flag. If
the cmdargs entry of the output does not contain the "-f"
flag, the hwevents file is in directory
/spdata/sys1/spmon/. Make a copy of hwevents in case
the original is subsequently modified.
This file is named
/var/adm/SPlogs/spmon/splogd.debug. If the
debug option was specified by the splogd command, the
splogd.debug file contains useful information for analyzing
problems. If the debug option was not specified, and the
problem can be re-created, do the following in order to obtain the
splogd.debug file:
- Determine if the debug option was specified by
splogd. Issue the command:
odmget -q 'subsysname=splogd' SRCsubsys
-
If the cmdargs entry of the output contains the "-d" flag,
the splogd.debug file should exist. Make a copy of
/var/adm/SPlogs/spmon/splogd.debug in order not to lose the
existing information in this file.
- If the cmdargs entry of the output does not contain the
"-d" flag, and you want to attempt to re-create the problem with
debugging enabled, do the following:
- From the output of the previous odmget command, if the
cmdargs entry of the output contains the "-f" flag, cut
and paste the argument that follows the "-f" flag, and issue the
command:
chssys -s splogd -a "-d -f HWEVENTS_PATH"
where HWEVENTS_PATH is the argument that followed the
"-f" flag.
For example, if what you cut and paste was
/spdata/sys1/spmon/hwevents, issue the command:
chssys -s splogd -a "-d -f /spdata/sys1/spmon/hwevents"
-
From the output of the previous odmget command, if the
cmdargs entry of the output does not contain the "-f"
flag, issue the command:
chssys -s splogd -a "-d"
-
Verify that the "-d" flag is now enabled, by again issuing the
command:
odmget -q 'subsysname=splogd' SRCsubsys
-
Stop and start the Logging daemon, in an attempt to re-create the problem with
the debug option enabled. Issue these commands:
- stopsrc -s splogd
- startsrc -s splogd
Now, the splogd.debug file should exist. If you are
able to re-create the problem, then after the problem occurs make a copy of
/var/adm/SPlogs/spmon/splogd.debug in order to preserve the
information in this file. To remove the debug option:
-
Issue the last chssys command without the "-d" flag.
-
Issue the command: stopsrc -s splogd.
-
Issue the command: startsrc -s splogd.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]