I could re-paste the whole thing, but its easier to just throw up the link:
http://theclusterguy.clusterlabs.org/post/205886990/advisory-dont-use-pacemaker-on-corosync-yet
On Thu, Sep 24, 2009 at 4:56 PM, Remi Broemeling wrote:
> I posted this to the OpenAIS Mailing List (
> open...@lists.linu
Steven Dake wrote:
Likely a defect. We will have to look into it. Please file a bug as
per instructions on the corosync wiki at www.corosync.org.
FWIW:
Cluster with three nodes, pace-1, pace-2 and pace-3.
pace-1:
Sep 26 10:33:40 pace-1 crmd: [2716]: info: do_shutdown_req: Sending
shutdow
Ok, thanks for the note Steven. I've filed the bug, it is #525589.
Steven Dake wrote:
Remi,
Likely a defect. We will have to look into it. Please file a bug as
per instructions on the corosync wiki at www.corosync.org.
On Thu, 2009-09-24 at 16:47 -0600, Remi Broemeling wrote:
Remi,
Likely a defect. We will have to look into it. Please file a bug as
per instructions on the corosync wiki at www.corosync.org.
On Thu, 2009-09-24 at 16:47 -0600, Remi Broemeling wrote:
> I've spent all day working on this; even going so far as to completely
> build my own set of packages
I've spent all day working on this; even going so far as to completely
build my own set of packages from the Debian-available ones (which
appear to be different than the Ubuntu-available ones). It didn't have
any effect on the issue at all: the cluster still freaks out and
becomes a split-brai
I posted this to the OpenAIS Mailing List
(open...@lists.linux-foundation.org) yesterday, but haven't received a
response and upon further reflection I think that maybe I chose the
wrong list to post it to. That list seems to be far less about user
support and far more about developer communic
