Looking at the mercurial repository for pacemaker (http://hg.clusterlabs.org/pacemaker/) I do not see any check-ins since 1.1.6 was tagged two months ago.
Does this mean the timeout bug has been fixed outside of the mercurial repository? This bug is a huge show-stopper for me, and if there is fixed code that needs testing I'm more than willing to throw it on a test cluster to see if it performs as expected. Thanks, Hal On Thu, Nov 24, 2011 at 6:42 AM, Ulrich Windl <[email protected]> wrote: >>>> Andrew Beekhof <[email protected]> schrieb am 24.11.2011 um 01:14 in >>>> Nachricht > <CAEDLWG3kw=t=k0hOLzf58KYdfJUC1Y0wOyz6Qd55f-za0rAU=w...@mail.gmail.com>: >> On Thu, Nov 24, 2011 at 1:42 AM, Hal Martin <[email protected]> wrote: >> > [...] >> > # stonith -t external/sbd sbd_device=/dev/mapper/qa-test-sbd -S >> > info: external/sbd device OK. >> > >> > Relevant portions of crm config: >> > primitive stonith-sbd stonith:external/sbd \ >> > meta is-managed="true" target-role="Started" >> >> Looks like you forgot to specify the sbd_device parameter. > > Hi! > > Interestingly this parameter (at least in SLES11 SP1: > /usr/lib64/stonith/plugins/external/sbd) is not required: > <parameter name="sbd_device" unique="1"> > > (a good question is why this unusual path is selected for a shell script) > > [...] > > Ulrich > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
