From: Whit Blauvelt <[email protected]> > On Sat, May 28, 2011 at 11:12:50PM +0200, Valentin Vidic wrote: >> If there is a second node, perhaps you can make it appear? And >> after the primary finishes with the boot adjust the startup timeouts >> from the default values. > Sadly, the second node is up. But the node that's stuck was dumb > enough to try to start drbd before networking was up. No idea why > the init.d script is behaving so badly in that regard, but
If you can ssh to the bad machine, fix the /etc/init.d/drbd script so that it starts *after* all the NICs are running. This should be pretty easy (change one number at the top of the script) on Redhat-derived distros, then chkconfig remove drbd && chkconfig add drbd or edit the symlinks in /etc/rc.d/rc3.d/ manually. The script should be fine as is on Gentoo since that has "need net; after sshd" in the depend() section. Then either reboot the bad node or "init S ; init 3" to get everything back to normal (probably). Adjust if this thing is defaulted to runlevel 5, or if you're running Slack. In all of our CentOS DRBD clusters, the drbd init script is never called by init. init calls heartbeat, and heartbeat does all the DRBD stuff. Are you running DRBD without a cluster manager, or something? -- Matt G / Dances With Crows The Crow202 Blog: http://crow202.org/wordpress/ There is no Darkness in Eternity/But only Light too dim for us to see _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
