Diagnosis Guide

Trace information

ATTENTION - READ THIS FIRST
Do not activate this trace facility until you have read this section completely, and understand this material. If you are not certain how to properly use this facility, or if you are not under the guidance of IBM Service, do not activate this facility. Activating this facility may result in degraded performance of your system. Activating this facility may also result in longer response times, higher processor loads, and the consumption of system disk resources. Activating this facility may also obscure or modify the symptoms of timing-related problems.

ATTENTION - READ THIS FIRST

Do not activate this trace facility until you have read this section completely, and understand this material. If you are not certain how to properly use this facility, or if you are not under the guidance of IBM Service, do not activate this facility.

Activating this facility may result in degraded performance of your system. Activating this facility may also result in longer response times, higher processor loads, and the consumption of system disk resources. Activating this facility may also obscure or modify the symptoms of timing-related problems.

SDR daemon trace

The sdrd daemon trace is intended for IBM Support Center personnel only. It is not intended for general customer use. When you work with IBM Service on a problem, you may be asked to turn this trace on to collect more information.

Trace information goes into the daemon error log in /var/adm/SPlogs/sdr. Since a large amount of information is logged, it may fill up the /var file system. Therefore, it is not recommended that the trace facility be left on for an extended period of time.

To turn on and off the sdrd trace, find the PID (process id) of the sdrd that you want to trace. Sending a hangup signal (SIGHUP) to the process will cause the daemon to toggle the trace setting. If the trace is on when the daemon receives the SIGHUP, the trace will be turned off. If the trace is off when the daemon receives the SIGHUP, the trace will be turned on.

To toggle the trace setting, perform these steps:

lssrc -g sdr
This finds the PIDs of all of the sdrd daemons on the system.
kill -HUP sdrdpid, where sdrdpid is the process id of the sdrd that you are interested in tracing.
Sending the SIGHUP signal toggles tracing on or off.

Before doing this, you must stop the currently running sdrd for that system partition:

stopsrc -s sdr.partition_name

where partition_name is the short hostname of the system partition of the sdrd.

If you want tracing to be on when the sdrd is started, use the d flag. Issue this command:

/usr/lpp/ssp/bin/sdrd partition_ip_address d

where partition_ip_address is the IP address being used for the system partition of the sdrd.

Note:: The d flag here is not preceded by a - (minus sign).

Rather than start the sdrd in the foreground, you may use the -a flag on the startsrc command to pass the d flag. Issue this command:

startsrc -s sdr.partition_name -a d

Note:: The d flag is not preceded by a - (minus sign).

Trace log entries consist of free form text messages.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]