Virtual TapeServer 6.03.41 Installation Guide

Troubleshooting | 105
Event log file
VTS provides many log files for troubleshooting issues with various functions of the system.
For example, the EMS log contains all messages (dependant on filters) received from the
NonStop server and the responses sent from VTS. VTS adds text that describes successful or
unsuccessful mounts, VTSPolicy commands that were interpreted, and so on. This file enables
you to diagnose the EMS configuration to and from the NonStop. For example, the log shows
the error that the password is invalid or the IP address did not connect. The event.log file
resides in /usr/local/tape/log on the VTS server.
The system event log file is generated by the VTS operating system (Linux) and records
information about events such as the creation and deletion of virtual tapes, failures of
processes and services, and the status of jobs and policies. The messages are stored in a single
log file, which is plain text and viewable from the user interface. The messages include
information about the time and date of the event as well as the name of the user who initiated
the event. Use the messages in this file to detect problems, track down the source of faults,
and audit users. In addition, information in the system event log can be retrieved by third-
party applications, such as Prognosis or Insight Manager, for notification purposes.
Requires the View log files access right
To access the system event log from the VTS user interface
Select Supervisor Functions→Log Files→Examine Event Log.
By default, the Examine the system log file page displays the latest entries in the log, which
are located at the bottom of the file.
•Click Refresh to refresh the log.
•Click Top to view the top of the log (and the oldest entries).
•Click Download to save the entire file to a local directory.
•Click Previous or Next to page through the file.
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 4 a.m.
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