Contents
Abstract
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. Use this chapter to get some ideas how to solve your issues.
If you have difficulties installing the packages or in bringing the cluster online, proceed according to the following list.
The packages needed for configuring and managing a cluster are
included in the High Availability installation
pattern, available with the High Availability Extension.
Check if High Availability Extension is installed as an add-on to SUSE Linux Enterprise Server 11 on each of the cluster nodes and if the pattern is installed on each of the machines as described in Section 3.1, “Installing the High Availability Extension”.
In order to communicate with each other, all nodes belonging to the
same cluster need to use the same bindnetaddr,
mcastaddr and mcastport as
described in
Section 3.2, “Initial Cluster Setup”.
Check if the communication channels and options configured in
/etc/ais/openais.conf are the same for all
cluster nodes.
In case you use encrypted communication, check if the
/etc/ais/authkey file is available on all cluster
nodes.
mcastport?
If the mcastport used for communication between the cluster nodes is
blocked by the firewall, the nodes cannot see each
other. When configuring the initial setup with YaST as described in
Section 3.1, “Installing the High Availability Extension”, the firewall
settings are usually automatically adjusted.
To make sure the mcastport is not blocked by the firewall, check the
settings in /etc/sysconfig/SuSEfirewall2 on each
node. Alternatively, start the YaST firewall module on each cluster
node. After clicking +, add the mcastport to the
list of allowed and confirm your changes.
Check the OpenAIS status on each cluster node with /etc/init.d/openais status. In case OpenAIS is not running, start it by executing /etc/init.d/openais start.