The start order in the init scripts is not taken into account. -- 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/1525911
Title: wrong stop order of corosync and pacemacer Status in corosync package in Ubuntu: New Bug description: In case of e reboot, poweroff or "service corosync stop" corosync stops before pacemacer this leads to an inconsistent state. As a communication between the nodes is only possible as long as corosync is running. My current work around is: # fix order of corosync/pacemaker startup! pacemaker must be stopped first update-rc.d -f corosync remove update-rc.d -f corosync defaults 19 20 update-rc.d -f pacemaker remove update-rc.d -f pacemaker defaults 20 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1525911/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
