VERITAS Volume Manager 3.1 Reference Guide

62 Chapter2
Error Messages
Volume Manager Configuration Daemon Error Messages
open. Other less likely reasons are “No such file or directory”or
“No such device or address.” For either of these two reasons, the
two likely causes are:
• The Volume Manager package installation did not complete
correctly.
• The device node was removed by the administrator or by an errant
shell script.
• Action
For the reason “Device is already open,” if you really want to run
vxconfigd, then stop or kill the old one. You can kill whatever
process has vxconfigd open by running the command:
vxdctl -k stop
For other failure reasons, consider reinstalling the base Volume
Manager software. This will reconfigure the device node and reinstall
the Volume Manager kernel device drivers. See the VERITAS Volume
Manager 3.1 for HP-UX Release Notes for information on how to
install the software on HP-UX 11i systems. If you cannot reinstall the
package, then contact Customer Support for more information.
enable failed
vxvm:vxconfigd: ERROR: enable failed: reason
• Description
Regular startup of vxconfigd failed for the stated reason. This error
can also result from the command vxdctl enable. This error may
include the following additional text:
additional-reason ; aborting
This message indicates that the failure was fatal and that vxconfigd
is forced to exit. The most likely cause that results in an abort is
inability to create IPC channels for communicating with other
utilities.
additional-reason ; transactions are disabled
This message indicates that vxconfigd is continuing to run, but no
configuration updates are possible until the error condition is
repaired.
Additionally, this may be followed with: