Error Code details
V-5-1-684
Severity: Error 
Component: Volume Manager 
Message:
IPC failure: Configuration daemon is not accessible IPC failure: Permission denied
Description:

The first message displays when the Veritas Volume Manager (VxVM) command line interface (CLI) cannot communicate with the configuration daemon, vxconfigd. The reason could be that the daemon is running in disabled mode or is not running.  Another possible reason is that the daemon is available but a non-root user is running the privileged command, which might also provoke the second message.

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2012-12-24 01:00:13 PDT
Platform: Red Hat Enterprise Linux 5 (x86-32), Red Hat Enterprise Linux 5 (x86-64), Red Hat Enterprise Linux 5 (POWER)
Release: 5.0MP3
Content:

Solution 1 applies only to the first message.

 

To resolve this issue:

  1. Check the status of the configuration daemon. Enter:

    /sbin/vxdctl mode
     
  2. Based on the output of step 1, do one of the following:
  • The mode could be disabled if  vxconfigd was started in disabled mode to prevent any configuration changes for maintenance, or it could not be enabled successfully. To make vxconfigd run in enabled mode, enter:

    /sbin/vxdctl enable
     
  • If the mode was killed or not started, vxconfigd may not be running. To start it, enter:

    /sbin/vxconfigd

    Note: To start vxconfigd the first time after you install VxVM, enter:

    vxinstall
Solution 2 Vote: [Useful] [Not useful]
Last Modified: 2012-12-24 01:08:45 PDT
Platform: Red Hat Enterprise Linux 5 (x86-32), Red Hat Enterprise Linux 5 (x86-64), Red Hat Enterprise Linux 5 (POWER)
Release: 5.0MP3
Content:

See www.symantec.com/docs/TECH67777.


This TechNote applies only to the first error message.

Solution 3 Vote: [Useful] [Not useful]
Last Modified: 2012-12-24 01:08:57 PDT
Platform: Red Hat Enterprise Linux 5 (x86-32), Red Hat Enterprise Linux 5 (x86-64), Red Hat Enterprise Linux 5 (POWER)
Release: 5.0MP3
Content:

Login or sudo as root, and then rerun the command.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service