Product SiteDocumentation Site

3.2. Verify Pacemaker Installation

Now that we have confirmed that Corosync is functional we can check the rest of the stack.
[root@pcmk-1 ~]# grep pcmk_startup /var/log/messages
Aug 27 09:05:35 pcmk-1 corosync[1540]:   [pcmk  ] info: pcmk_startup: CRM: Initialized
Aug 27 09:05:35 pcmk-1 corosync[1540]:   [pcmk  ] Logging: Initialized pcmk_startup
Aug 27 09:05:35 pcmk-1 corosync[1540]:   [pcmk  ] info: pcmk_startup: Maximum core file size is: 18446744073709551615
Aug 27 09:05:35 pcmk-1 corosync[1540]:   [pcmk  ] info: pcmk_startup: Service: 9
Aug 27 09:05:35 pcmk-1 corosync[1540]:   [pcmk  ] info: pcmk_startup: Local hostname: pcmk-1
Now verify the Pacemaker processes have been started
[root@pcmk-1 ~]# ps axf
  PID TTY      STAT   TIME COMMAND
    2 ?        S<     0:00 [kthreadd]
    3 ?        S<     0:00  \_ [migration/0]
... lots of processes ...
 2166 pts/0    SLl    0:01 /usr/sbin/corosync
 2172 ?        SLs    0:00  \_ /usr/lib64/heartbeat/stonithd
 2173 pts/0    S      0:00  \_ /usr/lib64/heartbeat/cib
 2174 pts/0    S      0:00  \_ /usr/lib64/heartbeat/lrmd
 2175 pts/0    S      0:00  \_ /usr/lib64/heartbeat/attrd
 2176 pts/0    S      0:00  \_ /usr/lib64/heartbeat/pengine
 2177 pts/0    S      0:00  \_ /usr/lib64/heartbeat/crmd
And finally, check for any ERRORs during startup, there shouldn’t be any, and display the cluster’s status.
[root@pcmk-1 ~]# grep ERROR: /var/log/messages | grep -v unpack_resources
[root@pcmk-1 ~]# crm_mon
============
Last updated: Thu Aug 27 16:54:55 2009
Stack: openais
Current DC: pcmk-1 - partition with quorum
Version: 1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7
2 Nodes configured, 2 expected votes
0 Resources configured.
============

Online: [ pcmk-1 pcmk-2 ]