Comment 2 for bug 1322899

I have a problem with using the update-rc.d to generate the rc*.d links. Even though pacemaker gets sequence number 20 and corosync number 19. It appears that corosync is not fully started when pacemaker gets started.

The result is that pacemaker starts up without a connection to the peer. And resources such as DRBD gets in a split brain state.

When removing the rc*.d links for pacemaker and starting pacemaker manually there is no problem. So apperantly it is not enough to wait for the corosync init script to launch. corosync needs to get properly connected before it is safe to start pacemaker.

On earlier verisions this was not a problem as the corosync plugin started pacemaker when corosync was ready.