On 17/02/16 15:15 +0200, Klechomir wrote: > Here is the output from your command: > > attrd: 609413 > cib: 609409 > corosync: 608778 > crmd: 609415 > lrmd: 609412 > pengine: 609414 > pacemakerd: 609407 > stonithd: 609411
This may mean that you are triggering this nasty bug in libqb: https://github.com/ClusterLabs/libqb/pull/162 (fixed in libqb-0.17.2) > Regarding using a newer version, that's what I've been thinking about, but > I've been using this combination of corosync/pacemaker for many years on a > different hardware and hever had similar problem. > The main difference is that I have stonith enabled only the problematic > cluster, but I also suspect that the node, which causes this problem may > have some hardware issues. Stonith/fencing should be configured at any cluster to satisfy fully what HA clusters are for, full stop. > BTW my last few tests with the newest corosync/pacemaker gave me very > annoying delay, when commiting configuration changes (maybe it's a known > problem?). Cannot comment on this but definitely good to be aware of possible performance regressions. -- Jan (Poki)
pgpZjq8RurGU_.pgp
Description: PGP signature
_______________________________________________ Users mailing list: [email protected] http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
