In case anybody comes across this on Google, the solution for me was-
In /etc/corosync/corosync.conf, enable the "ring recovery protocol"-
> totem {
> > ...
> > rrp_mode: active
> > ...
> }
Additionally, my IPaddr2's (with their near-instant start/stop times) were
reaching an INFINITY failcount
Andrew Beekhof writes:
> I've written this up for the wiki:
>http://clusterlabs.org/wiki/RHEL
For reference, I ran into a similar problem, except that I have the further
constraint that I can't use outside repositories.
As mentioned in this thread, the RHEL 6.x install media does come with
Dan Frincu writes:
Thanks, this gives me a great entrypoint for research.
Alex
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started:
I have a two node Pacemaker/Corosync cluster with no resources configured yet.
I'm running RHEL 6.1 with the official 1.1.5-5.el6 package.
While doing various network configuration, I happened to notice that if I issue
a "service network restart" on one node, then approx. four seconds later issue
