Volume Manager vxconfigd will not start during system startup if the file /etc/vx/reconfig.d/state.d/install-db exists
|Article:TECH156108|||||Created: 2011-03-21|||||Updated: 2014-01-02|||||Article URL http://www.symantec.com/docs/TECH156108|
Volume Manager does not start vxconfigd at system boot start-up if the file /etc/vx/reconfig.d/state.d/install-db exists.
No error will be reported during startup. The vxvm-startup script does a check for the install-db file and exits if it exists.
There are a number of possible reasons why install-db may have been created:
- VXVM patch scripts create the file during patch installation and may have failed to exist cleanly, leaving the file behind.
- Root disk encapsulation or un-encapsulation procedure creates this file and may have failed to remove it following completion of the encapsulation process.
- An engineer may have asked that that file be created during a support session and failed to request it be cleaned up at the end.
These are examples of the most common sources of this file. The file itself does not need to contain anything and usually doesn't.
Creating the /etc/vx/reconfig.d/state.d/install-db file is a safe and quick method to stop Volume Manager from starting during system boot-up.
Remove the install-db file to allow vxconfigd to start during system boot time:
# rm /etc/vx/reconfig.d/state.d/install-db
Article URL http://www.symantec.com/docs/TECH156108