Administrative server logs

This topic describes where the SAN File System administrative server logs are stored.

The following logs for the administrative server are stored on the engine hosting those servers.
Table 1. SAN File System administrative server message log files
Log File name Location Maximum file size
Administrative log cimom.log /usr/tank/admin/log
Console log console.log /usr/tank/admin/log
Security log security.log /usr/tank/admin/log
Standard error stderr.log /usr/tank/admin/log
Standard out stdout.log /usr/tank/admin/log
Note:
  1. Although log.std has a maximum file size of 250 MB, the SAN File System actually stores 500 MB of data for this log. This log reaches its maximum size, it is renamed to include the .old extension. If a file by that name already exists, the existing file is overwritten. Then the log is cleared so that it can start accepting new messages again.
When you display these logs from the master metadata server using either the administrative command-line interface or the SAN File System console, you actually see a consolidated view of all of the logs from each engine in the cluster.
Note: You can also display the event log. This log is actually a subset of the messages stored in the cluster log. It contains only those messages that have a message type of event.

Service only logs

The console.log, stderr.log, and the stdout.log are not intended for normal problem determination. They will not be discussed in detail.

Parent topic: Server diagnostic tools

Related reference
catlog

Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.