Tips to troubleshoot the error message, "ERROR: IPC Failure: Configuration daemon is not accessible", when running regular VERITAS Volume Manager commands.
| Article:TECH15607 | | | Created: 2001-01-31 | | | Updated: 2010-01-08 | | | Article URL http://www.symantec.com/docs/TECH15607 |
Problem
Tips to troubleshoot the error message, "ERROR: IPC Failure: Configuration daemon is not accessible", when running regular VERITAS Volume Manager commands.
Error
vxvm:xxxx: ERROR: IPC Failure: Configuration daemon is not accessible
Solution
The above mentioned error message means either
vxconfigd is not running or needs to be reset. First check to see if
vxconfigd is
running:
# ps -ef | grep vxconfigd
If it is not running (or it's running, but probably stuck), then enter the following to start it
# vxconfigd -k -x syslog
While trying to start the vxconfigd daemon, it is possible to get error messages like these: cannot open /dev/vx/config or volboot file not loaded. In this case, bring up VxVM manually as follows:
# vxiod set 10
# vxconfigd -m disable -x syslog
# vxdctl init
# vxdctl initdmp (Use this if Dynamic Multi-pathing (DMP) certified arrays are being used.)
# vxdctl enable
# ps -ef | grep vxconfigd
If it is not running (or it's running, but probably stuck), then enter the following to start it
# vxconfigd -k -x syslog
While trying to start the vxconfigd daemon, it is possible to get error messages like these: cannot open /dev/vx/config or volboot file not loaded. In this case, bring up VxVM manually as follows:
# vxiod set 10
# vxconfigd -m disable -x syslog
# vxdctl init
# vxdctl initdmp (Use this if Dynamic Multi-pathing (DMP) certified arrays are being used.)
# vxdctl enable
NOTE: VxVM
commands should now be available. If the problem continues, please contact
Symantec Technical Services.
|
|
Legacy ID
239247
Article URL http://www.symantec.com/docs/TECH15607
Terms of use for this information are found in Legal Notices
Thank you.