NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
Robotic Error Codes
These status codes are returned if a robotic daemon/process was started from the
command line and an error occurs. For example, if the administrator executes the
following:
/usr/openv/volmgr/bin/tl8d
and no robots are configured, the following may be returned:
TL8: No robots are configured
These status codes are also logged to the system log.
Usually, robotic daemons/processes are not started from the command line, but are
started automatically, as needed, when ltid starts.
Chapter 5, Media Manager Status Codes and Messages 359
Status Codes
Robot Error Status Code: 1
Message: You must be ROOT to start daemon
Explanation: A robotic daemon was started by a user other than root. This applies to
UNIX systems only.
Recommended Action: Log on as the root user before starting robotic daemons. Allow
robotic daemons to be started automatically as needed by ltid (the device daemon).
Robot Error Status Code: 2
Message: LTI Daemon may not be running
Explanation: On an attempt to start a robotic daemon/process, an attempt to connect to
the ltid message queue failed, indicating that ltid (the device daemon / NetBackup
Device Manager service), may not be running.
Recommended Action:
1. Start ltid so that shared memory can be initialized, allowing the robotic
daemon/process to function.
2. If problems persist, examine command output (if available), debug logs, and system
logs for messages related to the error.
a. Enable debug logging by creating the necessary directories/folders. Increase the
level of verbosity by adding the VERBOSE option in the vm.conf file and
restarting the daemons/services, or execute the command’s verbose option, if
available.
b. Retry the operation and examine the logs.
NetBackup 4.5 Troubleshooting Guide for Windows