Hello again, On Mon, 27 Mar 2006 13:24:39 -0500, Lon Hohberger wrote > On Sun, 2006-03-26 at 12:41 -0300, Celso K. Webber wrote: > > > We had many problems with quorum formation under this environment. If we > > booted both servers at the same time, quorum would be formed successfully. If > > after that we rebooted one of the servers, it would not rejoin the cluster > > until we stopped clumanager on both sides and restarted. > > Are you using disk-based or network-based tiebreaker? > I was using network-based tiebraker, and changing to broadcast heartbeating solved the problem. After doing some tests, I changed do disk-based heartbeating, although the GUI warned me that IP-based heartbeating was recommended for a 2-node configuration (I have 2 nodes). > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136553 > > I was never convinced that this was an iSCSI / RHCS3 interaction > problem, for what it's worth ;) > Yes, we are also not sure about these supposed iSCSI / CS3 problem, but the only references we encountered were those from the Bugzilla. > > http://people.redhat.com/lhh/network-stuff.html > I'll surely take a loot at it! Thanks! By the way, tell me if you think we should open a case on Red Hat support for this. Best regards, Celso. -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
