** Changed in: server-papercuts
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 bu
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 w
The totem hint worked for me on Lucid. It was not necessary on Maverick.
--
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
--
ubuntu-bugs mailing li
** Also affects: server-papercuts
Importance: Undecided
Status: New
--
cman does not start ... corosync died
https://bugs.launchpad.net/bugs/538139
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Hi!
I got a little help. Just for completeness:
The solution is to set consensus and token in /etc/cluster/cluster.conf
...
.. and not to start corosync on its own, as It is started automatically by cman.
Is this explanded anywhere?
I think the redhat-cluste
** Description changed:
Versions:
Ubuntu10.04 Alpha-3
redhat-cluster-suite 3.0.2-2ubuntu2
cman 3.0.2-2ubuntu2
corosync 1.2.0-0ubuntu1
/etc/init.d/cman start
Starting cluster:
-Global setup... [ OK ]
-Loading ker
** Description changed:
Versions:
Ubuntu10.04 Alpha-3
redhat-cluster-suite 3.0.2-2ubuntu2
cman 3.0.2-2ubuntu2
corosync 1.2.0-0ubuntu1
/etc/init.d/cman start
Starting cluster:
Global setup... [ OK ]
Loading ker
