Troubleshooting guide

Chapter 3, Using the Logs and Reports 69
Media Manager Logs
On UNIX
Media Manager on a UNIX system automatically records robotic and network errors in
the system logs by using syslogd. System log entries are also made when robotically
controlled drives change between UP and DOWN states.
Note You must enable system logging to troubleshoot ltid or robotic software. See the
syslogd(8) man page for information on setting up system logs.
If a problem requires more information, enable debug logging to the system logs by
including the verbose option (-v) on the command that you use to start a daemon. This
command can be:
◆ The ltid command that started the device management processes. If the -v option is
included on the ltid command, all daemons started as a result also have the -v
option in effect. (if you are using xvmadm and xdevadm, note that their options for
starting ltid do not enable debug logging.)
or
◆ A command to start a specific daemon (for example, acsd -v). Alternatively, put a
VERBOSE entry in the Media Manager configuration file,
/usr/openv/volmgr/vm.conf, and restart ltid (create the vm.conf file if
necessary).
See the syslogd man page for the locations of system log messages. Errors are logged
with LOG_ERR, warnings with LOG_WARNING, and debug information with
LOG_NOTICE. The facility type is daemon.
To enable debug logging for the Media Manager Volume daemon (vmd), create the
following directories before starting vmd (or stop and restart vmd after creating them):
/usr/openv/volmgr/debug/daemon
(Debug information on the daemon)
/usr/openv/volmgr/debug/reqlib
(Debug information on the process requesting the daemon)
If you are using xvmadm, you can enable debug logging for it by creating the following
directory:
/usr/openv/volmgr/debug/xvmadm
Media Manager creates one log per day in each of the debug directories with file names of
the form:
log.mmddyy
For example: