Veritas Volume Manager 5.0 Troubleshooting Guide, HP-UX 11i v3, First Edition, May 2008

83Error messages
Understanding messages
VxVM vxconfigd ERROR V-5-1-1589 enable failed:
t ransactions are
disabled
■ Description: Regular startup of vxconfigd failed. This error can also result
from the command vxdctl enable.
vxconfigd is continuing to run, but no configuration updates are possible
until the error condition is repaired.
Additionally, this may be followed with:
VxVM vxconfigd ERROR V-5-1-579 Disk group group: Errors in some
configuration copies:
Disk device, copy number: Block bno: error ...
Other error messages may be displayed that further indicate the underlying
problem.
■ Action: Evaluate the error messages to determine the root cause of the
problem. Make changes suggested by the errors and then try rerunning the
command.
If the “Errors in some configuration copies” error occurs again, that may
indicate the real problem lies with the configuration copies in the disk
group. You can recreate a disk group configuration by using the procedures
given in “Restoring a disk group configuration” on page 49.
V-5-1-2020
VxVM vxconfigd ERROR V-5-1-2020 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 reappears, contact
Veritas Technical Support.