Manualshelf

VERITAS Volume Manager 4.1 Troubleshooting Guide

ManualsBrandsHP ManualsSoftwareHP-UX 11i Volume Management (LVM/VxVM) Software
919293949596979899100
Error Messages
Understanding Messages
Chapter 694
• 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.
V-5-1-2197
VxVM vxconfigd ERROR V-5-1-2197 node N: missing vxconfigd
• Description: The vxconfigd daemon is not running on the indicated cluster node.
• Action: Restart the vxconfigd daemon.
V-5-1-2198
VxVM vxconfigd ERROR V-5-1-2198 node N: vxconfigd not ready
• Description: The vxconfigd daemon is not responding properly in a cluster.
• Action: Stop and restart the vxconfigd daemon on the node indicated.
V-5-1-2274
VxVM vxconfigd ERROR V-5-1-2274 volume:vxconfigd cannot boot-start RAID-5
volumes
• Description: A volume that vxconfigd should start immediately upon booting the system
(that is, the volume for the /usr file system) has a RAID-5 layout. The /usr file system
should never be defined on a RAID-5 volume.
• Action: It is likely that the only recovery for this is to boot VxVM from a network-mounted
root file system , and reconfigure the /usr file system to be defined on a regular
non-RAID-5 volume.
V-5-1-2290
VxVM vxdmpadm ERROR V-5-1-2290 Attempt to enable a controller that is
not available