2016-01-11 12:53:10 |
Martin Thomas |
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 |
It seems that update-rc.d does not use the information which is given in the header of the init script. We realized this with the corosync/packemaker init script.
The Start order which is given in the header of the init script was not taken into account by update-rc.d.
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 |
|