[Pacemaker] crm_simulate a resource failure
Jake Smith
jsmith at argotec.com
Thu Oct 25 13:34:27 UTC 2012
----- Original Message -----
> From: "Andrew Beekhof" <andrew at beekhof.net>
> To: "Jake Smith" <jsmith at argotec.com>
> Cc: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Wednesday, October 24, 2012 8:02:34 PM
> Subject: Re: [Pacemaker] crm_simulate a resource failure
>
> On Thu, Oct 25, 2012 at 1:51 AM, Jake Smith <jsmith at argotec.com>
> wrote:
> >
> > ----- Original Message -----
> >> From: "Andrew Beekhof" <andrew at beekhof.net>
> >> To: "Jake Smith" <jsmith at argotec.com>
> >> Cc: "The Pacemaker cluster resource manager"
> >> <pacemaker at oss.clusterlabs.org>
> >> Sent: Wednesday, October 24, 2012 5:36:13 AM
> >> Subject: Re: [Pacemaker] crm_simulate a resource failure
> >>
> >> On Wed, Oct 24, 2012 at 9:35 AM, Jake Smith <jsmith at argotec.com>
> >> wrote:
> >> > Ubuntu 12.04
> >> >
> >> > pacemaker 1.1.6-2ubuntu3
> >> >
> >> > If I run crm_simulate -L I get this:
> >> >
> >> > root at Vulture:~# crm_simulate -L
> >> > *** glibc detected *** crm_simulate: double free or corruption
> >> > (out): 0x0000000001fc2e00 ***
> >>
> >> [snip]
> >>
> >> >
> >> > Maybe just cause I'm not giving it enough parameters??
> >>
> >> No. Unfortunately there was a bug in 1.1.6
> >> Is there nothing newer available?
> >
> > Not from Ubuntu packaged for 12.04.
> >
> > 12.10 has 1.1.7 but we prefer to stick with LTS releases
>
> While I understand the theory behind this line of thinking, isn't the
> whole point behind the S in LTS that you're supposed to get bugfixes?
I agree with you on that.
> A distro that leaves crash bugs unfixed for over a year doesn't sound
> very desirable.
> You'd get the same effect by installing any random distro and never
> running an update.
You mean like the fedora 3/4 servers this cluster replaced?!? ;-)
>
>
> Btw. In case it helps, the fix for this crash was:
> https://github.com/beekhof/pacemaker/commit/2bdb230
Thanks! It should - I'll pursue getting it fixed.
Jake
More information about the Pacemaker
mailing list