Chapter 4. Troubleshooting
20
<fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="600">
• If a node fails while the fenced daemon is not running, it will not be fenced. It will cause problems
if the fenced daemon is killed or exits while the node is using GFS. If the fenced daemon exits, it
should be restarted.
If you find that you are seeing error messages when you try to configure your system, or if after
configuration your system does not behave as expected, you can perform the following checks and
examine the following areas.
• Connect to one of the nodes in the cluster and execute the clustat(8) command. This command
runs a utility that displays the status of the cluster. It shows membership information, quorum view,
and the state of all configured user services.
The following example shows the output of the clustat(8) command.
[root@clusternode4 ~]# clustat
Cluster Status for nfsclust @ Wed Dec 3 12:37:22 2008
Member Status: Quorate
Member Name ID Status
------ ---- ---- ------
clusternode5.example.com 1 Online, rgmanager
clusternode4.example.com 2 Online, Local, rgmanager
clusternode3.example.com 3 Online, rgmanager
clusternode2.example.com 4 Online, rgmanager
clusternode1.example.com 5 Online, rgmanager
Service Name Owner (Last) State
------- --- ----- ------ -----
service:nfssvc clusternode2.example.com starting
In this example, clusternode4 is the local node since it is the host from which the command was
run. If rgmanager did not appear in the Status category, it could indicate that cluster services are
not running on the node.
• Connect to one of the nodes in the cluster and execute the group_tool(8) command. This
command provides information that you may find helpful in debugging your system. The following
example shows the output of the group_tool(8) command.
[root@clusternode1 ~]# group_tool
type level name id state
fence 0 default 00010005 none
[1 2 3 4 5]
dlm 1 clvmd 00020005 none
[1 2 3 4 5]
dlm 1 rgmanager 00030005 none
[3 4 5]
dlm 1 mygfs 007f0005 none
To Next Page
Loading...