VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Chapter 3, Error Messages

vxconfigd Error Messages

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 speciﬁed, but a

running conﬁguration daemon process could not be killed. A conﬁguration daemon

process, for purposes of this discussion, is any process that opens the

/dev/vx/config device (only one process canopen that device at a time). If there is

a conﬁguration 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 conﬁguration daemon process, the above error message is displayed.

◆ Action: This error can result from a kernel error that has made the conﬁguration

daemon process unkillable, from some other kind of kernel error, or from some other

user starting another conﬁguration 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 systemerror related to the failure is given inreason. A system error of “Nosuch

ﬁle or directory” indicates that one of the preﬁx 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 ﬁle or directory

locations are speciﬁed 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

◆ Description: The /dev/vx/config device couldnot beopened. vxconfigd uses this

device to communicate with the VERITAS Volume Manager kernel drivers. The most

likely reason is “Deviceis already open.” Thisindicates that someprocess(most likely

vxconfigd) already has /dev/vx/config open. Less likely reasons are “No such

ﬁle or directory” or “No such device or address.” For either of these reasons, likely

causes are: