[Pacemaker] Re: Understanding rules: location, colocation, order. Using with Master/Slave

Andrew Beekhof beekhof at gmail.com
Wed Oct 29 06:08:54 EDT 2008


On Wed, Oct 29, 2008 at 09:39, Adrian Chapela
<achapela.rexistros at gmail.com> wrote:
> Andrew Beekhof escribió:
>>> OK, but Adrew said me this morning that bug was fixed in last stable
>>> code. I
>>> have downloaded Pacemaker-1-0-79d2ba7e502f but pingd seems broken as
>>> well.
>>>
>>
>> I'm pretty sure it works - but its a good idea to log a bug (and add a
>> hb_report tarball) anyway
>>
>
> Yes I know. I will test with a two clean systems today (If I can...). If for
> me it stills not working I will open a bug.

I just tested this and pingd is updating the cib as I'd expect.

node-182:~ # cibadmin -Ql | grep status-.*-pingd
          <nvpair id="status-node-182-pingd" name="pingd" value="100"/>
node-182:~ # ip addr add dev eth0 192.168.9.123
node-182:~ # cibadmin -Ql | grep status-.*-pingd
          <nvpair id="status-node-182-pingd" name="pingd" value="200"/>
node-182:~ # ip addr del dev eth0 192.168.9.123
node-182:~ # cibadmin -Ql | grep status-.*-pingd
          <nvpair id="status-node-182-pingd" name="pingd" value="100"/>

Possibly your rules aren't quite right and thats what is preventing
the resources from starting.




More information about the Pacemaker mailing list