wrong stop order of corosync and pacemacer
Bug #1525911 reported by
Martin Thomas
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| sysvinit (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
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
| description: | updated |
| affects: | corosync (Ubuntu) → sysvinit (Ubuntu) |
To post a comment you must log in.
