<h1>Entered a bug.</h1><h1>Bugzilla Bug <a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=250811">250811</a>: clustat report wrong information about rgmanager on a GULM cluster </h1>Hope it will be solved soon, which can save some work of mine, since I can not trust/rely on clustat right now. Thanks, Siman <div>On 8/2/07, Lon Hohberger <<a href="mailto:lhh@redhat.com">lhh@redhat.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Tue, Jul 31, 2007 at 10:22:33AM -0400, siman hew wrote: > I found clustat report wrong information about rgmanager when a cluster is > GULM. > I setup a 3-node cluster on RHEL4U5, with GULM. There are one failover > domain, one resource and one service, just for testing. > I found clustat always report rgmanger is running after cluster is started. > With the configuration with DLM, clustat report correctly. > node4 is lock server, and all nodes report the same inaccurate information. GULM doesn't have a way to provide sub-groups really, except for users of lockspaces. Can you file a bugzilla about this? I wonder if we can get the information for "what nodes are in this lockspace" from GULM. If it's possible, we could probably fix it. -- Lon Hohberger - Software Engineer - Red Hat, Inc. -- Linux-cluster mailing list <a href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/linux-cluster"> https://www.redhat.com/mailman/listinfo/linux-cluster</a> </blockquote></div>