pavan tc <pavan...@gmail.com> writes: > Hi, > > I have now hit this issue twice in my setup. > I see the following github commit addressing this issue: > https://github.com/ClusterLabs/pacemaker/commit/03f6105592281901cc10550b8ad19af4beb5f72f
Hi, I'm also impacted by this issue. (running pcmk 1.1.7 and corosync 1.4.4) there's a closed bug report here : http://bugs.clusterlabs.org/show_bug.cgi?id=5040 as far as i understand it's an issue with coroync. Pacemaker 1.1.8 is supposed to have workarounds for it, but I was still able to reproduce the bug when running it with corosync 1.4.4 It's ok with pcmk 1.1.8 and corosync 2.1.0. But I do have some issues with 1.1.8 that make it unsuitable for production env yet. -- Laurent _______________________________________________ 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
