Red Hat ENTERPRISE LINUX 5 - CONFIGURATION NFS OVER GFS Configuration Manual page 28

Chapter 7. Troubleshooting
The state of the group should be none. The numbers in the brackets are the node ID numbers of
the cluster nodes in the group. The clustat shows which node IDs are associated with which
nodes. If you do not see a node number in the group, it is not a member of that group. For example,
if a node ID is not in dlm/rgmanager group, it is not using the rgmanager dlm lock space (and
probably is not running rgmanager).
The level of a group indicates the recovery ordering. 0 is recovered first, 1 is recovered second, and
so forth.
• Connect to one of the nodes in the cluster and execute the cman_tool nodes -f command This
command provides information about the cluster nodes that you may want to look at. The following
example shows the output of the cman_tool nodes -f command.
[root@clusternode1 ~]# cman_tool nodes -f
Node Sts Inc
1 M 752
2 M 752
3 M 760
4 M 756
5 M 744
The Sts heading indicates the status of a node. A status of M indicates the node is a member of
the cluster. A status of X indicates that the node is dead. The Inc heading indicating the incarnation
number of a node, which is for debugging purposes only.
• Check whether the cluster.conf is identical in each node of the cluster. If you configure your
system with Conga, as in the example provided in this document, these files should be identical, but
one of the files may have accidentally been deleted or altered.
• In addition to using Conga to fence a node in order to test whether failover is working properly
Chapter 6, Testing the NFS Cluster
as described in
connection between cluster members. You might try disconnecting one, two, or three nodes, for
example. This could help isolate where the problem is.
• If you are having trouble mounting or modifying an NFS volume, check whether the cause is one of
the following:
• The network between server and client is down.
• The storage devices are not connected to the system.
• More than half of the nodes in the cluster have crashed, rendering the cluster inquorate. This
stops the cluster.
• The GFS file system is not mounted on the cluster nodes.
• The GFS file system is not writable.
• The IP address you defined in the cluster.conf is not bounded to the correct interface / NIC
(sometimes the ip.sh script does not perform as expected).
18
Joined
2008-10-27 11:17:15
2008-10-27 11:17:15
2008-12-03 11:28:44
2008-12-03 11:28:26
2008-10-27 11:17:15
Name
clusternode5.example.com
clusternode4.example.com
clusternode3.example.com
clusternode2.example.com
clusternode1.example.com
Service, you could disconnect the ethernet