The Heartbeat services are started just as you would any other system service on your machine. Depending on your system platform, you might be using one of the following commands:
/etc/init.d/heartbeat start
service heartbeat start
rcheartbeat start
Through the pacemaker entry in your
ha.cf, Heartbeat will now
start the Pacemaker daemon (named crmd for historical reasons) along
with the rest of its services. After a few seconds, you should be
able to detect Heartbeat processes in your process table:
# ps -AHfww | grep heartbeat root 2772 1639 0 14:27 pts/0 00:00:00 grep heartbeat root 4175 1 0 Nov08 ? 00:37:57 heartbeat: master control process root 4224 4175 0 Nov08 ? 00:01:13 heartbeat: FIFO reader root 4227 4175 0 Nov08 ? 00:01:28 heartbeat: write: bcast eth2 root 4228 4175 0 Nov08 ? 00:01:29 heartbeat: read: bcast eth2 root 4229 4175 0 Nov08 ? 00:01:35 heartbeat: write: mcast bond0 root 4230 4175 0 Nov08 ? 00:01:32 heartbeat: read: mcast bond0 102 4233 4175 0 Nov08 ? 00:03:37 /usr/lib/heartbeat/ccm 102 4234 4175 0 Nov08 ? 00:15:02 /usr/lib/heartbeat/cib root 4235 4175 0 Nov08 ? 00:17:14 /usr/lib/heartbeat/lrmd -r root 4236 4175 0 Nov08 ? 00:02:48 /usr/lib/heartbeat/stonithd 102 4237 4175 0 Nov08 ? 00:00:54 /usr/lib/heartbeat/attrd 102 4238 4175 0 Nov08 ? 00:08:32 /usr/lib/heartbeat/crmd 102 5724 4238 0 Nov08 ? 00:04:47 /usr/lib/heartbeat/pengine
Finally, you should also be able to confirm that the cluster is
working, via the Pacemaker crm_mon command:
# crm_mon -1 ============ Last updated: Mon Dec 13 14:29:36 2010 Stack: Heartbeat Current DC: alice (083146b9-6e26-4ac8-a705-317095d0ba57) - partition with quorum Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b 2 Nodes configured, unknown expected votes 24 Resources configured. ============ Online: [ alice bob ]