[Pacemaker] crm_attribte failed with Multiple attributes match

[Andrew Beekhof]

On Thu, Feb 4, 2010 at 8:20 AM,  <renayama19661014 at ybb.ne.jp> wrote:
> Hi Andrew,
>
> This problem occurred in our environment.
>
>  * RHEL5.4(x86) on Esxi 2node
>  * corosync 1.1.2
>  * Pacemaker-1-0-6f67420618b0.tar.gz
>
> It sometimes occurs when I carry out test.sh in long time.
>
> [root at srv01 ~]# ./test.sh
> (snip)
> scope=status  name=master-vmrd-res: value=132
> Multiple attributes match name=master-vmrd-res:
>  Value: 133    (id=status-srv01-master-vmrd-res:)
>  Value: 133    (id=status-srv01-master-vmrd-res:)
>  Value: 133    (id=status-srv01-master-vmrd-res:)
> scope=status  name=master-vmrd-res: value=134
> scope=status  name=master-vmrd-res: value=135
> scope=status  name=master-vmrd-res: value=136
> scope=status  name=master-vmrd-res: value=137
> Multiple attributes match name=master-vmrd-res:
>  Value: 138    (id=status-srv01-master-vmrd-res:)
>  Value: 138    (id=status-srv01-master-vmrd-res:)
>  Value: 138    (id=status-srv01-master-vmrd-res:)
> scope=status  name=master-vmrd-res: value=139
> scope=status  name=master-vmrd-res: value=140
> scope=status  name=master-vmrd-res: value=141
>
>
> I think that this problem is very important.
> The failure of the update of the attribute may cause the fail-over that we do not expect.
>
> After all is it a problem of libxml2?
> Is it necessary to update libxml2?

It seems so.
If I understood hj correctly, that was the only part he replaced in
order for it to function correctly.