Top
PRIMECLUSTER  Cluster Foundation Configuration and Administration Guide 4.5
FUJITSU Software

5.2.2 Caused by staying in the kernel debugger too long

In the figure below, 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.

  2. While Node C is down, 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. Bring Node C back up. It will rejoin the cluster as part of its reboot process.