Error Code details
Severity: Error 
Component: Volume Manager 
Cannot kill existing daemon


Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:56 PST
Platform: Generic
Release: Generic
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 error message is displayed.

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.


User solutions
No user solutions yet.


Read and accept Terms of Service