VERITAS Volume Manager 4.1 Troubleshooting Guide

Logging Commands and Transactions
Associating Command and Transaction Logs
Chapter 4 57
NOTE The client ID is the same as that recorded for the corresponding command line
in the command log. See “Logging Commands” on page 53"and “Associating
Command and Transaction Logs” on page 57" 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-moff command. If this
happens, use the vxtranslog utility to recreate the settings file, or restore the
file from a backup.
Associating Command and Transaction Logs
The Client and process IDs that are recorded for every request and command assist you in
correlating entries in the command and transaction logs. To find out which command issued a
particular request in transaction log, use a command such as the following to search for the
process ID and the client ID in the command log:
# egrep -n PID cmdlog | egrep Clid
In this example, the following request was recorded in the transaction log:
Wed Feb 12 21:19:36 2003
Clid = 8309, PID = 2778, Part = 0, Status = 0, Abort Reason = 0
DG_IMPORT foodg
DG_IMPORT foodg
DISCONNECT <no request data>
To locate the utility that issued this request, the command would be:
# egrep -n 2778 cmdlog | egrep 8309
7310:# 8309, 2778, Wed Feb 12 21:19:36 2003
The output from the example shows a match at line 7310 in the command log. Examining
lines 7310 and 7311 in the command log indicates that the vxdg import command was run
on the foodg disk group:
# sed -e ’7310,7311!d’ cmdlog
# 8309, 2778, Wed Feb 12 21:19:36 2003 7311