Virtual TapeServer 6.04.04 for NonStop Servers Operations and Administration Guide

Troubleshooting | 119
e. On the local system, verify that messages are being logged in the remote system. For
example, use the logger utility:
logger -p kern.info test message
This should result in an entry such as “Jun 29 15:29:51 vtsdev24 bill: test message”
appearing in the remote system's log file.
Note
The syslog.conf file on the remote system will determine if and where the
message is logged.
To test the remote logging, log in to the VTS system using SSH but specify an incorrect user
or password. Messages about this attempt should appear in the remote log. The log files in
which messages are placed on the remote system depends on its configuration.
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.
AUTOCOPY FAILED: Request by:
$requestor ($retry_number) cannot
reach $target/$filename (rc=$rc)
Critical No action is required. The task will be
retried.
AUTOCOPY FAILED: Requested
by: $requestor ($retry_number)
from $target/$filename(rc=$rc)
Critical The autocopy task failed. Correct the
problem and resubmit the job.