01-18-2011 06:23 AM
I have Volume Manager 4.1 running on a Solaris 10 with Sun Cluster. This is a 2 node cluster and one node is fine, however on the second node vxconfigd fails to start on reboot. The odd part is that vxconfigd starts and works fine if I manually start it once the system has booted up.
The Oracle/Sun support folks have suggested re-installing Veritas, and I've located some install disks so I'm ready to try that, but I'm wondering if there is anything else I can try first?
Solved! Go to Solution.
01-18-2011 11:52 AM
I had already checked for the presence of the install-db file, and it did not exist. And, there were no errors on startup except ones that said vxconfigd was not running. Nothing from vxconfigd itself.
Oracle/Sun had suggested installing a patch 124358-08 which I was finally able to download and after installing this patch vxconfigd started correctly. This may not have been a patch issue in particular, but just replaced whatever file or binary was broken.
At least I did not have to re-install VxVM.
Thanks for the suggestions . . .
01-18-2011 11:00 AM
is there a file called /etc/vx/reconfig.d/state.d/install-db ?
if install-db file exists, it will prevent volume manager to startup ..
remove the file & volume manager should start automatically..
Gaurav
01-18-2011 11:28 AM
Agree with Gaurav. Any error messages at boot time?
See http://www.symantec.com/docs/TECH69680
01-18-2011 11:52 AM
I had already checked for the presence of the install-db file, and it did not exist. And, there were no errors on startup except ones that said vxconfigd was not running. Nothing from vxconfigd itself.
Oracle/Sun had suggested installing a patch 124358-08 which I was finally able to download and after installing this patch vxconfigd started correctly. This may not have been a patch issue in particular, but just replaced whatever file or binary was broken.
At least I did not have to re-install VxVM.
Thanks for the suggestions . . .