*** This bug is a duplicate of bug 1052449 ***
https://bugs.launchpad.net/bugs/1052449
** This bug has been marked a duplicate of bug 1052449
corosync hangs due to missing pacemaker shutdown scripts
--
You received this bug notification because you are a member of Ubuntu
Server, which is
See related bug 1727063
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1322899
Title:
pacemaker init script
After some more checking I found that my issue was not with the startup
order but the shutdown order.
At install of corosync, the shutdown is linked with K01corosync. Using
update-rc.d pacemaker defaults will create the shutdown link
K20pacemaker.
This causes corosync to be shutdown before pacema
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pacemaker (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bug
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 res
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I guess that update-rc.d can be run by hand as a workaround? In this
case, setting Importance: Medium as a workaround is available.
** Changed in: pacemaker (Ubuntu)
Importance: Undecided => Medium
--
You rec
