Troubleshooting - Novell SUSE LINUX ENTERPRISE SERVER 10 SP2 HEARTBEAT Manual

Troubleshooting

Especially when starting to experiment with Heartbeat, strange problems may occur
that are not easy to understand. However, there are several utilities that may be used to
take a closer look at the Heartbeat internal processes.
What is the state of my cluster?
To check the current state of your cluster, use the program crm_mon. This displays
the current DC as well as all of the nodes and resources that are known to the current
node.
Several nodes of my cluster do not see each other.
For some reason, the connection between your nodes is broken. Most often, this is
the result of a badly configured firewall. This also may be the reason for a split
brain condition, where the cluster is partitioned.
I want to list my currently known resources.
Use the command crm_resource -L to learn about your current resources.
I configured a resource, but it always fails.
Try to run the resource agent manually. With LSB, just run scriptname start
and scriptname stop. To check an OCF script, set the needed environment
variables first. For example, when testing the IPaddr OCF script, you have to set
the value for the variable ip by setting an environment variable that prefixes the
name of the variable with OCF_RESKEY_. For this example, run the command:
export OCF_RESKEY_ip=<your_ip_address>
/usr/lib/ocf/resource.d/heartbeat/IPaddr validate-all
/usr/lib/ocf/resource.d/heartbeat/IPaddr start
/usr/lib/ocf/resource.d/heartbeat/IPaddr stop
8
Troubleshooting 107