Comment 5 for bug 1434684

Hello,

Well, elbandi have found the answer to your question : pacemaker now needs to be started as a separate service. To quote the document :

"Pacemaker used to obtain membership and quorum from a custom Corosync plugin. This plugin also had the capability to start Pacemaker automatically when Corosync was started.
Neither behavior is possible with Corosync 2.0 and beyond as support for plugins was removed. Instead, Pacemaker must be started as a separate service."

Looks like the services are correctly setup as pacemaker starts normally at boot time. If you want to manually stop your cluster, you will have to issue :

$ service corosync stop
$ service pacemaker stop