|
|
Explanation: A request to ltid cannot be serviced. (ltid is the Media Manager device daemon on UNIX and Linux or the NetBackup Device Manager service on Windows.) ltid is probably not running. If ltid is still running, its process lock file may have been removed. Also, message queues may not function correctly on the system.
If ltid is not running, start ltid and try the operation again. On UNIX and Linux, run /usr/openv/volmgr/bin/ltid, and on Windows, start the NetBackup Device Manager service.
If ltid is already running, check for the existence and permissions of the lock file itself and the lock file directory, which are as follows: /usr/openv/volmgr/misc/.ltipid (UNIX and Linux) or install_path\ Volmgr\misc\.ltipid (Windows). Terminate the ltid process if it is running. Create the lock directory or folder and adjust the permissions as needed so that ltid can obtain the lock.
On UNIX and Linux, check the msgget man page and look for suggestions on how to troubleshoot the system message queues.