Diagnosis Guide

Error symptoms, responses, and recoveries

Use the following table to diagnose problems with the Logging daemon component of PSSP. Locate the symptom and perform the action described in this table.

Table 57. Logging daemon symptoms

Actions

Action 1 - Run the setup_logd command

Perform test Installation test 1 - Verify splogd and setup_logd files.

On the control workstation, check directory /var/adm/SPlogs/spmon/splogd to see if a core dump was created. If so, save it, see Information to collect before contacting the IBM Support Center and contact the IBM Support Center.

Whether or not there is a core file, attempt to restart the Logging daemon:

1. Delete the following lines, if any exist, from the /etc/syslog.conf file. Do not simply comment these lines out. They must be deleted from the file for this repair action.

                daemon.notice         /var/adm/SPlogs/SPdaemon.log
                daemon.debug          /var/adm/SPlogs/SPdaemon.log
                daemon.info           /var/adm/SPlogs/SPdaemon.log
   

2. Issue the command:

   setup_logd
   

To ensure that this action has succeeded, perform test Operational test 3 - Check Logging daemon status, which verifies that the Logging daemon is now running.

If you are attempting this action because the Logging daemon died, be aware that this action may only temporarily resolve the problem. If the original condition that caused the Logging daemon to die in the first place still exists, this condition may again cause the Logging daemon to die before or after performing test Operational test 3 - Check Logging daemon status.

Action 2 - Ensure that the Logging daemon writes to syslog file

Perform these tests:

1. Installation test 2 - Verify hwevents file
2. Operational test 1 - Check System Monitor daemon
3. Operational test 2 - Check for frames responding
4. Configuration test 2 - Check /etc/syslog.conf and /var/adm/SPlogs/SPdaemon.log files

To ensure that this action has succeeded, perform test Operational test 6 - Check writing to syslog file.

Action 3 - Ensure that the Logging daemon writes to the AIX Error Log

Perform these tests:

1. Installation test 2 - Verify hwevents file
2. Operational test 1 - Check System Monitor daemon
3. Operational test 2 - Check for frames responding
4. Configuration test 3 - Check hwevents file
5. Configuration test 4 - Check SPMON error record templates
6. Operational test 4 - Check error daemon status

To ensure that this action has succeeded, perform test Operational test 7 - Check writing to the AIX Error Log.

Action 4 - Ensure that the Logging daemon writes to splogd.state_changes file

Perform these tests:

1. Installation test 2 - Verify hwevents file
2. Operational test 1 - Check System Monitor daemon
3. Operational test 2 - Check for frames responding
4. Configuration test 1 - Check for state logging

To ensure that this action has succeeded, perform test Operational test 8 - Check writing to splogd.state_changes file.

Action 5 - Correct Logging daemon user exit mechanism

Perform these tests:

1. Operational test 1 - Check System Monitor daemon
2. Operational test 2 - Check for frames responding
3. Installation test 2 - Verify hwevents file
4. Configuration test 5 - Check sser exits

To ensure that this action has succeeded, perform test Operational test 5 - Check user exit mechanism.