======================================================= MCSG: Troubleshooting a hung cluster reformation: ======================================================= :Title: MCSG: Troubleshooting a hung cluster reformation: :Author: Douglas O'Leary :Description: MCSG: Troubleshooting a hung cluster reformation: :Date created: 06/2007 :Date updated: 07/2008 :Disclaimer: Standard: Use the information that follows at your own risk. If you screw up a system, don't blame it on me... For the most part, these seem to be caused by someone issueing a cmrunnode to start a cluster verses the cmruncl. Doing this causes the node to look for a cluster that doesn't exist. Apparently, the cmcld daemon doesn't quite have the smarts to realize that something's amiss, so it waits... and waits... There's a few things you can try to get around this mess. #. ``cmhaltcl -f``. This probably won't work, but it's worth a try. #. Enter ``cmrunnode`` on another node to see if the two can link up. #. Reboot the affected node. #. kill cmcld as a last resort