[Pacemaker] Pacemaker 0.7.3: How to use pingd clone resource and constraints

Andrew Beekhof beekhof at gmail.com
Mon Oct 6 13:29:01 UTC 2008


On Fri, Sep 26, 2008 at 22:15, Andrew Beekhof <beekhof at gmail.com> wrote:
> On Fri, Sep 26, 2008 at 16:42, Andrew Beekhof <beekhof at gmail.com> wrote:
>> On Fri, Sep 26, 2008 at 09:37, Andrew Beekhof <beekhof at gmail.com> wrote:
>>> Most likely you've found a bug :-(
>>> Would you be able to create a bugzilla entry for this?
>>> On Sep 25, 2008, at 9:33 PM, Bruno Voigt wrote:
>>>
>>> Wow.. these warnings are even shown for 127.0.0.1 ?!
>>> Do I need to finetune the IP stack options somewhere like in sysctl.conf
>>> to have these warnings of pingd fixed?
>>
>> I looked into this, and for localhost the cause is me not filtering
>> out the ICMP_ECHO packet.
>> I'll patch that now.
>>
>> For remote hosts, there seems to be something else going on
>
> In short - pingd in 0.7 is/was completely broken on linux (but worked
> great on Darwin).
> Sorry :(
>
> The good news is that I have it basically functioning properly now - I
> just need to clean up the patch before I commit (which I'll do over
> the weekend).
>

Would you be able to verify that pingd in the new packages (0.7.3-2.1)
behaves properly?

Btw. You can also run it from the command line (with no cluster
present) by supplying the -U option.
Instead of trying to update attrd, it will instead output the message
it would have sent.




More information about the Pacemaker mailing list