Product SiteDocumentation Site

Chapter 4. Start and Verify Cluster

Table of Contents

4.1. Start the Cluster
4.2. Verify Corosync Installation
4.3. Verify Pacemaker Installation

4.1. Start the Cluster

Now that corosync is configured, it is time to start the cluster. The command below will start corosync and pacemaker on both nodes in the cluster. If you are issuing the start command from a different node than the one you ran the pcs cluster auth command on earlier, you must authenticate on the current node you are logged into before you will be allowed to start the cluster.
[root@pcmk-1 ~]# pcs cluster start --all
pcmk-1: Starting Cluster...
pcmk-2: Starting Cluster...


An alternative to using the pcs cluster start --all command is to issue either of the below command sequences on each node in the cluster separately:
# pcs cluster start
Starting Cluster...
# systemctl start corosync.service
# systemctl start pacemaker.service


In this example, we are not enabling the corosync and pacemaker services to start at boot. If a cluster node fails or is rebooted, you will need to run pcs cluster start nodename (or --all) to start the cluster on it. While you could enable the services to start at boot, requiring a manual start of cluster services gives you the opportunity to do a post-mortem investigation of a node failure before returning it to the cluster.