Virtual TapeServer 6.03.41 Operations and Administration Guide

104 | Troubleshooting
Location, retention, and rotation
The /usr/local/tape/log directory contains the current log file, which is named event.log, as
well as the previous seven log files. The event log is rotated, or “aged,” the same as the other
log files. Log aging is setup to check daily if a log file has reached a size greater than 10KB. If
the size limit is reached then the old log is renamed to a new name containing the rotation
number and a new (blank) log begins with the default name. Seven versions of the file are
kept. This file is renewed each day at 04:00 hrs.
Previous log files are compressed using gzip. If more than seven log files must be maintained,
the files must be backed up manually.
Note Users must have Read access to the /user/local/tape/log directory.
The following is an example directory listing of seven rotated logs plus the current log file:
-rw-rw-r-- 1 10240 Jul 25 04:02 ../log/event.log.7.gz
-rw-rw-r-- 1 5948 Jul 26 04:02 ../log/event.log.6.gz
-rw-rw-r-- 1 2326 Jul 28 04:02 ../log/event.log.5.gz
-rw-rw-r-- 1 905 Jul 29 04:02 ../log/event.log.4.gz
-rw-rw-r-- 1 998 Aug 1 04:02 ../log/event.log.3.gz
-rw-rw-r-- 1 1148 Aug 2 04:02 ../log/event.log.2.gz
-rw-rw-r-- 1 1038 Aug 4 04:02 ../log/event.log.1.gz
-rw-rw-r-- 1 4521 Aug 4 12:41 ../log/event.log
System event log format
Each message entry in the file follows the same format, as shown in the following example:
2006-08 28 16:25:18|WARNING|440002|5900-A|
127.0.0.1|Tapeserver01|administrator|Access Control RESTORE OPEN
defaults have been restored
Entries are divided into the sections described in the following table:
Attribute Format Example Description
Date/Timestamp 2006-08 28 16:25:18 Time and date when the message
originated, in a format that is specific to the
locale.
Severity WARNING The degree of impact or seriousness of the
event reported by the message. (See
Message severity on page 105.)
Message ID 440002 A unique six-digit identifier. All message
IDs contain the severity, subsystem, and
message ID. The unique ID falls within a
numerical range of 0-999999. (See
Message
IDs on page 106.)
Machine ID 5900-A The make and model of VTS on which the
message was generated.
IP address 127.0.0.1 The IP address of the user or client that
initiates a function on a page of VTS.