Mailing List Archive: apply_xml_diff: Digest mis-match

apply_xml_diff: Digest mis-match

Aug 13, 2012, 6:39 AM

Post #1 of 3 (1746 views)

Hi!

In pacemaker-1.1.6-1.29.1 (SLES11 SP2 x86_64) I see this for an idle cluster with just one stonith resource being running when doing some unrelated change:

Aug 13 15:33:19 h3 cib: [31938]: info: apply_xml_diff: Digest mis-match: expected 466ee3cf78eec0772f78b6fc965e9601, calculated e8d85a1134f84f8b6eb8dff8ff598f71
Aug 13 15:33:19 h3 cib: [31938]: notice: cib_process_diff: Diff 0.14.77 -> 0.15.1 not applied to 0.14.77: Failed application of an update diff
Aug 13 15:33:19 h3 cib: [31938]: info: cib_server_process_diff: Requesting re-sync from peer

I have the feeling there's something wrong in either generating the diff, or applying the diff.

Regards,
Ulrich

_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Re: apply_xml_diff: Digest mis-match [ In reply to ]

andrew at beekhof

Aug 16, 2012, 4:51 PM

Post #2 of 3 (1679 views)

Permalink

On Mon, Aug 13, 2012 at 11:39 PM, Ulrich Windl
<Ulrich.Windl@rz.uni-regensburg.de> wrote:
> Hi!
>
> In pacemaker-1.1.6-1.29.1 (SLES11 SP2 x86_64) I see this for an idle cluster with just one stonith resource being running when doing some unrelated change:
>
> Aug 13 15:33:19 h3 cib: [31938]: info: apply_xml_diff: Digest mis-match: expected 466ee3cf78eec0772f78b6fc965e9601, calculated e8d85a1134f84f8b6eb8dff8ff598f71
> Aug 13 15:33:19 h3 cib: [31938]: notice: cib_process_diff: Diff 0.14.77 -> 0.15.1 not applied to 0.14.77: Failed application of an update diff
> Aug 13 15:33:19 h3 cib: [31938]: info: cib_server_process_diff: Requesting re-sync from peer
>
> I have the feeling there's something wrong in either generating the diff, or applying the diff.

I would only expect this if either:
- you're changing the order of resources in a group (which you aren't), or
- when a node first comes online and sees the other node.

In the latter case, the diff applies cleanly, but the digest alerts us
to the fact that we are missing other (unrelated) changes.

>
> Regards,
> Ulrich
>
>
> _______________________________________________________
> Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
> Home Page: http://linux-ha.org/
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Re: apply_xml_diff: Digest mis-match [ In reply to ]

lmb at suse

Aug 17, 2012, 4:19 AM

Post #3 of 3 (1674 views)

Permalink

On 2012-08-13T15:39:22, Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> wrote:

> Hi!
>
> In pacemaker-1.1.6-1.29.1 (SLES11 SP2 x86_64) I see this for an idle cluster with just one stonith resource being running when doing some unrelated change:

What is the "unrelated change" you are doing?

Does this always occur when you change the CIB, or is it a rare
occurrence?

Regards,
Lars

--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/