catlog

Displays the contents of the various log files maintained by the administrative server and the cluster.

Read syntax diagramSkip visual syntax diagram
>>-catlog--+----------+--+----------------------+--------------->
           +- –?----+  '- –entries--+-25--+-'
           +- –h----+                 +-50--+
           '- –help-'                 +-75--+
                                        '-100-'

>--+-----------------------+--+--------------------------+------>
   |          .-cluster--. |  '- –date--YYYY–MM–DD-'
   '- –log--+-admin----+-'
              +-audit----+
              +-event----+
              '-security-'

                                         .-,--------.
                                         V          |
>--+-----------------------+-- –level----+-info-+-+----------><
   '- –order--+-newest-+-'               +-err--+
                '-oldest-'                 +-warn-+
                                           '-sev--'

Parameters

–? | –h | –help
Displays a detailed description of this command, including syntax, parameter descriptions, and examples. If you specify a help option, all other command options are ignored.
–entries
Specifies the number of log entries to show at a time, from oldest to newest. Valid values are 25, 50, 75, or 100. If not specified, this command shows the entire log.
–log
Displays entries in the specified log, ordered by timestamp starting with the most recent entry. The default is cluster.
admin
Displays entries in the administrative log, which maintains a history of messages created by the administrative server.
audit
Displays entries in the audit log, which maintains a history of all commands issued by any administrator for all metadata servers in the cluster.
cluster
Displays entries in the cluster log, which maintains a history of messages created by all metadata servers in the cluster.
event
Displays event entries in the event log, which maintains a history of event messages issued by all metadata servers in the cluster.
security
Displays entries in the security log, which maintains a history of administrative-user login activity.
–date
Specifies the date at which you want the displayed log entries to start. The date must be in the format YYYYMMDD, where YYYY is the year, MM is the month, and DD is the day.

This date must be the current date or older. Future dates are not acceptable.

–order
Specifies the direction of the displayed log entries. You can specify one of the following values:
newest
Displays the log entries form newest to oldest. This is the default value if the –date parameter is not specified.
oldest
Displays the log entries form oldest to newest. This is the default value if the –date parameter is specified.
–level info | err | warn | sev
Specifies the severity level of the displayed log entries. If not specified, all severity levels are displayed. You can specify one or more levels, separate by a comma and no space (for example, –level info,warn,err)

Description

If you run this command from an engine hosting a subordinate metadata server, logs for only the local engine are displayed. If you run this command from the engine hosting the master metadata server, logs for the entire cluster are displayed.

If there are log entries that have not been displayed, you are prompted to press Enter to display the next set of entries or to type exit and press Enter to stop.

This command displays the following information for the specified log:
  • Message identifier.
  • Severity level (Info, Error, Warning, Severe).
  • Message type (Normal or Event).
  • Name of the metadata server that generated the message.
  • Date and time the message was generated.
  • Message description.
Tip: It is important that the date and time are correct on the metadata servers so messages are logged correctly and log entries are displayed correctly when using the –time parameter.

Example

Display the event entries in the cluster log The following example displays the error messages in the event log that occurred on or after January 4, 2003.
sfscli> catlog -log event -date 2003-01-04 -level err

ID           Level   Type    Server   Date and Time
============================================================
HSTSS0009E   Error   Event   ST3      Jan 2, 2003 8:39:15 PM
HSTNL0019E   Error   Event   ST2      Jan 2, 2003 8:40:46 PM

Message
======================================================
The Metadata server rpm is not installed.
Unable to extract boot record when server is running.

Parent topic: Administrative commands

Related reference
clearlog
collectdiag

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