I know it's a bit late, but here's an explanation. Corosync in Lucid is
adopted to pacemaker, and this is true for all further releases. This
means that corosync is started on its own, spawning pacemaker services.
/etc/corosync/corosync.conf is adjusted for pacemaker too - if you wish
to run cman with corosync, you should stop corosync from starting on
boot and adopt corosync.conf - there are two examples in /etc/corosync.
I'll mark this as invalid since service needs to be configured before
it's started. If you feel this isn't correct, please reopen the bug and
suggest what should be done. Thanks.
** Changed in: redhat-cluster (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/538139
Title:
cman does not start ... corosync died
To manage notifications about this bug go to:
https://bugs.launchpad.net/server-papercuts/+bug/538139/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
