Veritas Volume Manager 5.0 Troubleshooting Guide Guide (September 2006)

45Logging commands and transactions
Logging transactions
Fri Oct 17 13:23:30 2003
Clid = 23460, PID = 21240, Part = 0, Status = 0, Abort Reason = 0
DA_GET Disk_0
DISK_GET_ATTRS Disk_0
DISK_DISK_OP Disk_0 8
DEVNO_GET Disk_0
DANAME_GET 0x160045 0x160072
GET_ARRAYNAME Disk DISKS
CTLR_PTOLNAME 11-08-01
GET_ARRAYNAME Disk DISKS
CTLR_PTOLNAME 21-08-01
DROPPED <no request data>
The first line of each log entry is the time stamp of the transaction. The Clid field
corresponds to the client ID for the connection that the command opened to
vxconfigd.
The PID field shows the process ID of the utility that is requesting the operation. The
Status and Abort Reason fields contain error codes if the transaction does not
complete normally. The remainder of the record shows the data that was used in
processing the transaction.
Note: The client ID is the same as that recorded for the corresponding command line in the
command log. See “Logging commands” on page 41 and “Associating command and
transaction logs” on page 46 for more information.
If there is an error reading from the settings file, transaction logging switches to its built-in
default settings. This may mean, for example, that logging remains enabled after being
disabled using
vxtranslog -m off command. If this happens, use the vxtranslog
utility to recreate the settings file, or restore the file from a backup.