2.6. Testing the Configuration
The specifics of a procedure for testing your cluster configuration will depend on the high availability application you are running in the cluster, but in general you can check whether the application is running and whether it fails over as follows.
- Verify that the service you created is running with the
clustat
command, which you can run on either cluster node. In this example, the serviceexample_apache
is running onnode1.example.com
.#
clustat
Cluster Status for exampleHA @ Thu Sep 29 12:17:39 2011 Member Status: Quorate Member Name ID Status ------ ---- ---- ------ node1.example.com 1 Online, Local node2.example.com 2 Online Service Name Owner (Last) State ------ ---- ----- ------ ----- service:example_apache node-01.example.com started - Check whether the service is operational. How you do this depends on the application. For example, if you are running an Apache web server, point a browser to the URL you defined for the server to see if the display is correct.
- Shut down the cluster software on the node on which the service is running, which you can determine from the
clustat
display.- Click on the cluster name beneath luci page. This displays the nodes that constitute the cluster.from the menu on the left side of the
- Select the node you want to leave the cluster by clicking the check box for that node.
- Select thefunction from the menu at the top of the page. This causes a message to appear at the top of the page indicating that the node is being stopped.
- Refresh the page to see the updated status of the node.
- Run the
clustat
command again to see if the service is now running on the other cluster node. If it is, check again to see if the service is still operational. For example, if you are running an apache web server, check whether you can still display the website. - Make sure you have the node you disabled rejoin the cluster by returning to the cluster node display, selecting the node, and selecting.