Product SiteDocumentation Site

4.3. Verify Pacemaker Installation

Now that we have confirmed that Corosync is functional, we can check the rest of the stack. Pacemaker has already been started, so verify the necessary processes are running:
[root@pcmk-1 ~]# ps axf
  PID TTY      STAT   TIME COMMAND
    2 ?        S      0:00 [kthreadd]
...lots of processes...
 1362 ?        Ssl    0:35 corosync
 1379 ?        Ss     0:00 /usr/sbin/pacemakerd -f
 1380 ?        Ss     0:00  \_ /usr/libexec/pacemaker/cib
 1381 ?        Ss     0:00  \_ /usr/libexec/pacemaker/stonithd
 1382 ?        Ss     0:00  \_ /usr/libexec/pacemaker/lrmd
 1383 ?        Ss     0:00  \_ /usr/libexec/pacemaker/attrd
 1384 ?        Ss     0:00  \_ /usr/libexec/pacemaker/pengine
 1385 ?        Ss     0:00  \_ /usr/libexec/pacemaker/crmd
If that looks OK, check the pcs status output:
[root@pcmk-1 ~]# pcs status
Cluster name: mycluster
WARNING: no stonith devices and stonith-enabled is not false
Stack: corosync
Current DC: pcmk-2 (version 1.1.18-11.el7_5.3-2b07d5c5a9) - partition with quorum
Last updated: Mon Sep 10 16:37:34 2018
Last change: Mon Sep 10 16:30:53 2018 by hacluster via crmd on pcmk-2

2 nodes configured
0 resources configured

Online: [ pcmk-1 pcmk-2 ]

No resources


Daemon Status:
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/enabled
Finally, ensure there are no start-up errors from corosync or pacemaker (aside from messages relating to not having STONITH configured, which are OK at this point):
[root@pcmk-1 ~]# journalctl -b | grep -i error

Note

Other operating systems may report startup errors in other locations, for example /var/log/messages.
Repeat these checks on the other node. The results should be the same.