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
** Changed in: corosync (Ubuntu Trusty)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1434684
Title:
Pace
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: corosync (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu
** Changed in: corosync (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1434684
Title:
Pacemaker i
look the important section:
http://clusterlabs.org/doc/fr/Pacemaker/1.1-pcs/html/Clusters_from_Scratch/_configuring_corosync.html
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/
same problem in ubuntu 14.04
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1434684
Title:
Pacemaker is not started and stopped automatically with Corosync
Status in co
Same problem here. temporarily fix with this :
service pacemaker start
update-rc.d pacemaker defaults
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1434684
Title:
Pace
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: corosync (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpa
** Description changed:
In Ubuntu 12.04 with:
# dpkg -l |egrep "pacemaker|corosync"
ii corosync 1.4.2-2ubuntu0.2
Standards-based cluster framework (daemon and modules)
ii pacemaker1.1.6-2ubuntu3.3 HA
clus
9 matches
Mail list logo