Hello everyone!
Some problems occured with synchronisation CIB configuration to disk.
I have this errors in pacemaker's logfile:
/May 14 13:29:13 iblade6 cluster: error: validate_cib_digest: Digest
comparision failed: expected 2c91194022c98636f90df9dd5e7176c6
(/var/lib/heartbeat/crm/cib.Zm249H), calculated bc1
60870924630b3907c8cb1c3128eee
May 14 13:29:13 iblade6 cluster: error: retrieveCib: Checksum of
/var/lib/heartbeat/crm/cib.a024wF failed! Configuration contents ignored!
May 14 13:29:13 iblade6 cluster: error: retrieveCib: Usually this is
caused by manual changes, please refer to
http://clusterlabs.org/wiki/FAQ#cib_changes_detected
May 14 13:29:13 iblade6 cluster: error: crm_abort:
write_cib_contents: Triggered fatal assert at io.c:662 :
retrieveCib(tmp1, tmp2, FALSE) != NULL
May 14 13:29:13 iblade6 pengine[2852]: notice: process_pe_message:
Transition 41: PEngine Input stored in: /var/lib/pengine/pe-input-452.bz2
May 14 13:29:13 iblade6 cib[2848]: error: cib_diskwrite_complete:
Disk write failed: status=134, signo=6, exitcode=0
May 14 13:29:13 iblade6 cib[2848]: error: cib_diskwrite_complete:
Disabling disk writes after write failure/
I didn't find anything about it, at this link:
http://clusterlabs.org/wiki/FAQ#cib_changes_detected
What can be the reason of this error?
Why the checksum of a cib file can be wrong?
Is it a problem of a hdd, or pacemaker bug or something else? (there are
no disk or filesystem errors in syslog)
I had a pair of such incidents during the last week.
My cluster installation: CentOS 6.4 x86_64, pacemaker 1.1.7, corosync 2.3.0
Thank you in advance!
Ivan Khalezov.
_______________________________________________
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
