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
** Changed in: corosync (Ubuntu)
Status: Confirmed => Invalid
** Changed in: corosync (Ubuntu Trusty)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434684
Title:
Pacemaker is not started and stopped automatically with Corosync
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1434684/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
