[Pacemaker] pcmk 1.1.8, some issues

[David Vossel]

----- Original Message -----
> From: "Andrew Beekhof" <andrew at beekhof.net>
> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Friday, December 7, 2012 2:45:56 PM
> Subject: Re: [Pacemaker] pcmk 1.1.8, some issues
> 
> 
> On 08/12/2012, at 3:45 AM, David Vossel <dvossel at redhat.com> wrote:
> 
> > 
> > 
> > ----- Original Message -----
> >> From: laurent+pacemaker at u-picardie.fr
> >> To: "The Pacemaker cluster resource manager"
> >> <pacemaker at oss.clusterlabs.org>
> >> Sent: Friday, December 7, 2012 10:13:59 AM
> >> Subject: Re: [Pacemaker] pcmk 1.1.8, some issues
> >> 
> >> David Vossel <dvossel at redhat.com> writes:
> >> 
> >>> ----- Original Message -----
> >>>> From: laurent+pacemaker at u-picardie.fr
> >>>> To: pacemaker at oss.clusterlabs.org
> >>>> Sent: Friday, December 7, 2012 9:48:12 AM
> >>>> Subject: [Pacemaker] pcmk 1.1.8, some issues
> >>>> 
> >>>> 
> >>>> Hi,
> >>>> 
> >>>> I quite like 1.1.8 but I have some issues with it.
> >>>> 
> >>>> 
> >>>> 1) something wrong with stonith-timeout
> >>>> 
> >>>> stonith-ng[24816]:    error: get_capable_devices:
> >>>> stonith-timeout
> >>>> duration 0 is too low, raise the duration to 80 seconds
> >>>> 
> >>>> with <nvpair id="cib-bootstrap-options-stonith-timeout"
> >>>> name="stonith-timeout" value="120s" />
> >>> 
> >>> When do you see this?  Is pacemaker fencing a node when this
> >>> occurs, or are you manually doing it using stonith_admin?
> >> 
> >> oh sorry i forgot to say.
> >> triggering it by stonith_admin -l nodename
> > 
> > Yeah, looking at the code that should still work.  Can you file a
> > bug at bugs.clusterlabs.org in the fencing section for this.  I'll
> > have a look when I get a chance.
> 
> stonith_admin probably isn't passing a timeout in.

It should be.  If no timeout is given I believe it is hard-coded to default to 120 seconds.

-- Vossel

> > 
> > -- Vossel
> > 
> >> I need to reinstall 1.1.8 on this test setup, i'm pretty sure the
> >> fencing was also failing for no apparent reason.
> >> But that's something to be expected with a timeout that low.
> >> 
> >> --
> >> Laurent
> >> 
> >> _______________________________________________
> >> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >> 
> >> Project Home: http://www.clusterlabs.org
> >> Getting started:
> >> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> >> Bugs: http://bugs.clusterlabs.org
> >> 
> > 
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> > 
> > Project Home: http://www.clusterlabs.org
> > Getting started:
> > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs: http://bugs.clusterlabs.org
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started:
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>