** Description changed: + 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
** Package changed: corosync (Ubuntu) => sysvinit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525911 Title: wrong stop order of corosync and pacemacer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1525911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
