Linux client logs, traces, and crash dumps

This topic describes the log, trace, and crash dump mechanisms for the Linux™ client.

Logs

Use the syslog utility to enable logging on a Linux client. The log messages are routed through the syslog utility on the Linux operating system. The syslog utility captures log output from the kernel, as well as other operating system services. By default, the syslog utility discards all kernel output. However, you can configure the syslog utility to specify a destination for the messages by modifying the/etc/syslog.conf file.

Traces

The trace messages are recorded in a memory-based trace buffer. The trace buffer is a circular buffer. Trace messages are overwritten with new messages when the buffer overflows.

First failure tracing is enabled by default and cannot be disabled. All other tracing levels are disabled by default and can be enabled using the sanfstrace set utility. You can also use the sanfstrace utility to set and list levels of tracing.

You can use sanfstrace log utility to retrieve the logged trace messages from the trace buffer and append them in text format to a specified log file. If you do not specify a file, the messages are sent to the standard output device.

Restriction: Modify the tracing levels only when directed to do so by you IBM® support personnel.

Crash dumps

You can initiate a memory dump of the kernel image using the Linux netdumpt command. This command creates a memory dump on a central server over the network. Refer to your Linux operating system documentation for information and implementation considerations.

Parent topic: Client logs and traces

Library | Support | Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.
IBM TotalStorage SAN File System v2.2