On 11/07/2013, at 5:09 PM, Johan Huysmans <johan.huysm...@inuits.be> wrote:
> Hi, > > Sorry about the missing info, here it is: > OS: CentOS 6.4 > CoroSync: 1.4.1-15 > Pacemaker: 1.1.10-1.el6-3463b39 (rc6) > > > Any more info needed to investigate this error? Could you set PCMK_trace_functions=apply_xml_diff ( http://blog.clusterlabs.org/blog/2013/pacemaker-logging/ ) and re-test? I've been trying to reproduce locally without success. You'll need to send the cluster _log_ file, not _syslog_. Look out for a syslog message like: pacemakerd[1823]: notice: crm_add_logfile: Additional logging available in /var/log/cluster/corosync.log which tells you where it is. > > On 10-07-13 16:23, Andreas Mock wrote: >> Hi Johan, >> >> I do forget it also often, but more than years ago >> you have to give detailed informations about your stack: >> - OS >> - corosync version (or heartbeat) >> - pacemaker version >> - agent version >> - etc. >> >> Best regards >> Andreas >> >> >> -----Ursprüngliche Nachricht----- >> Von: Johan Huysmans [mailto:johan.huysm...@inuits.be] >> Gesendet: Mittwoch, 10. Juli 2013 15:17 >> An: The Pacemaker cluster resource manager >> Betreff: [Pacemaker] cib_process_diff: Failed application of an update diff >> >> Hi All, >> >> Every time a resource fails or recovers or any other action is performed >> I see following messages in my log. >> Which can be the cause for this problem, how can I see more information >> about this message (view the patch / diff which is failing). >> >> >> >> stonith-ng[25994]: warning: cib_process_diff: Diff 0.90.29 -> 0.90.30 >> from local not applied to 0.90.29: Failed application of an update diff >> stonith-ng[25994]: notice: update_cib_cache_cb: [cib_diff_notify] >> Patch aborted: Application of an update diff failed (-206) >> >> >> thx! >> Johan Huysmans >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org > > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org