Ok, that looks better. Both nodes show up as being memebers using cman_tool status and cman_tool nodes. Also, seems I forgot to start rgmanager. Once I started it, the "test" service I configured started up. stopping rgmanager, openais, cman in that order on the second node, caused node1 to fence node2. clustat still doesn't report correct status for me, but at least I am getting some status back. Thanks Corey -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Lon Hohberger Sent: Wednesday, September 13, 2006 11:29 AM To: linux clustering Subject: Re: RHEL5 cluster problem... On Wed, 2006-09-13 at 11:26 -0400, Kovacs, Corey J. wrote: > Good morning.. > > Some oddness regarding clusterring on RHEL5beta1 (could be me) > > I have a two node cluster and the cluster components installed. > I have two nics in each node, the second of which I want to use for > openais. > > I have my cluster.conf pointing to the primary nic and I have openais > pointing to 192.168.0.0 (my second nics are on 192.168.0.1 and 2) > > Things seem to start ok on both nodes but they don't appear to be > talking to eachother. > For instance, clustat on the first node shows both nodes active even > if node2 is down. > > Actually, openais seems to be doing fine, but cman looks to be acting > up. > > This config was created using s-c-cluster and indeed it looks good. Am > I missing some new fundemental thing with the new cluster versions? > > I've been running RHCS/GFS on RHEL3 and RHEL4 for some time now but > this is my first attempt at the new (openais based) clusterring. > > > Any thoughts? For a start, you can always try cman_tool status / cman_tool nodes, just to take clustat out of the picture. -- Lon -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
