Virtual TapeServer 6.04.02 Operations and Administration Guide

134 | Troubleshooting
/usr/local/tape/log/ems.lastmount.cmd
/usr/local/tape/log/rescan.txt
/usr/local/tape/log/SecureVTS.log
Note Though you can change the log level of these files, the log level is reset to the default
every time VTS is rebooted.
To view log files, the following commands are useful:
view logfile
To search the file
tail –f –n 35 logfile
To list the file in real-time
grep –ni string logfile
To search for a specific string
less logfile
To search a file by paging through it
Compressed log files can be searched and viewed by using zgrep and zless.
EMS messages
The following table lists the messages that are generated by VTS if EMS is enabled and
configured. Here is an explanation of the information for each EMS message:
The message text.
Some of the text in the messages and errors is parameterized, as indicated by the dollar
sign ($). In a real message, the parameterized text is replaced by a real value. For
example, the host system that initiated the request is represented in the message text as
$host, but an actual message displays the real hostname, such as DEV2.
The severity of the message. The levels of severity include the following:
Informational (Inform) — A normal operation has occurred.
Warning — A suspicious operation, configuration, or user error has occurred. The
system or application can handle the error with no interruption and limited
degradation of service.
Critical — A system or service error has occurred. The system can recover but a
momentary loss or permanent degradation of service may occur.
The recommended action to take.
Message Text Severity Recommended Action
(Error:) Non-zero return-code ($rc)
from dsmc (try this url … for
$cart_request.
Critical An IBM Tivoli Storage Manager (TSM)
failure occurred. Examine the return
error code and correct the problem.
AUTOCOPY FAILED: Request by:
$requestor ($retry_number) cannot
create directory $target (rc=$rc)
Critical No action is required. The task will be
retried.