VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)

Error Messages
vxconfigd Error Messages
Chapter 3
61
vxconfigd Error Messages
An error message from the configuration daemon, vxconfigd, indicates a problem with
the operation of VxVM that may prevent it from running effectively. Action should be
taken to correct the problem immediately.
vxvm:vxconfigd: ERROR: Cannot get all disks from the kernel: reason
vxvm:vxconfigd: ERROR: Cannot get all disk groups from the kernel: reason
vxvm:vxconfigd: ERROR: Cannot get kernel transaction state: reason
vxvm:vxconfigd: ERROR: Cannot get private storage from kernel: reason
vxvm:vxconfigd: ERROR: Cannot get private storage size from kernel: reason
vxvm:vxconfigd: ERROR: Cannot get record record_name from kernel: reason
• Description: These internal errors should not occur unless there is a bug in VxVM.
• Action: Contact Customer Support.
vxvm:vxconfigd: ERROR: Cannot kill existing daemon, pid= process_ID
• Description: The -k (kill existing vxconfigd process) option was specified, but a
running configuration daemon process could not be killed. A configuration daemon
process, for purposes of this discussion, is any process that opens the
/dev/vx/config device (only one process can open that device at a time). If there is
a configuration daemon process already running, then the -k option causes a
SIGKILL signal to be sent to that process. If, within a certain period of time, there is
still a running configuration daemon process, the above error message is displayed.
• Action: This error can result from a kernel error that has made the configuration
daemon process unkillable, from some other kind of kernel error, or from some other
user starting another configuration daemon process after the SIGKILL signal. This
last condition can be tested for by running vxconfigd -k again. If the error message
appears again, contact Customer Support.
vxvm:vxconfigd: ERROR: Cannot make directory directory_path : reason
• Description: vxconfigd failed to create a directory that it expects to be able to create.
Directories that vxconfigd might try to create are: /dev/vx/dsk, /dev/vx/rdsk,
and /var/vxvm/tempdb. Also, for each disk group, /dev/vx/dsk/ diskgroup and
/dev/vx/rdsk/ diskgroup directories are created. The system error related to the
failure is given in reason . A system error of “No such file or directory” indicates that
one of the prefix directories (for example, /var/vxvm) does not exist.
This type of error normally implies that the Veritas Volume Manager packages were
installed incorrectly. Such an error can also occur if alternate file or directory
locations are specified on the command line, using the -x option. The
_VXVM_ROOT_DIR environment variable may also relocate to a directory that lacks a
var/vxvm subdirectory.
• Action: Try to create the directory manually and then issue the command vxdctl
enable. If the error is due to incorrect installation of the Veritas Volume Manager
packages, try to add the packages again.
vxvm:vxconfigd: ERROR: cannot open /dev/vx/config: reason