Sign In
Problem
Volume Manager does not start vxconfigd at system boot start-up if the file /etc/vx/reconfig.d/state.d/install-db exists.
Error Message
No error will be reported during startup. The vxvm-startup script does a check for the install-db file and exits if it exists.
Cause
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.
Solution
Remove the install-db file to allow vxconfigd to start during system boot time:
# rm /etc/vx/reconfig.d/state.d/install-db
Terms of use for this information are found in Legal Notices.
|
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.
