Top
PRIMECLUSTER  Cluster Foundation Configuration and Administration Guide 4.6
FUJITSU Software

5.2.2 Caused by staying in the kernel debugger too long

If the break point is set by the kernel debugger to suspend the operation of OS kernel, the heartbeat of CF will stop. In the following figure, Node C was placed in the kernel debugger too long so it appears as a hung node. Nodes A and B decided that Node C's state was LEFTCLUSTER.

Figure 5.3 Node C placed in the kernel debugger too long

To recover from this situation, you would need to do the following:

  1. Shut down Node C, and bring it back up.

  2. If Node C fails to join the cluster and remains in the LEFTCLUSTER state after being shut down and coming back up, start up the Cluster Admin on Node A or B. Use Mark Node Down from the Tools pull-down menu in the CF portion of the GUI to mark Node C DOWN.

  3. The node should successfully join the cluster.