Hey there. I used the script that I wrote to STOP all gmonds, STOP gmetad, then START All gmonds and START gmetads, and I still have non-cluster members reporting into the wrong clusters. Any other ideas that you may have would be appreciated!
-Regards Ron Cavallo Sr. Director, Infrastructure Saks Fifth Avenue / Saks Direct 12 East 49th Street New York, NY 10017 212-451-3807 (O) 212-940-5079 (fax) 646-315-0119(C) www.saks.com -----Original Message----- From: Seth Graham [mailto:[email protected]] Sent: Tuesday, March 22, 2011 12:05 PM To: Ron Cavallo Cc: Bostjan Skufca; Bernard Li; [email protected] Subject: Re: [Ganglia-general] Ganglia: Nodes showing up in wrong clusters in web frontend On Mar 22, 2011, at 10:53 AM, Ron Cavallo wrote: > > I see other examples where I have to go hunting around for cluster members that aren't reporting into the proper cluster. > > Any ideas? Double check the ports in use in the gmond.conf on the machines that are misbehaving. Also note that machines tend to linger in an old cluster they were reporting to, even if their config file says otherwise. If you look at the XML dump from the gmetad, you may find that a given machine appears twice. The web frontend gives fairly random results when this happens. These stale entries do eventually expire (default is 30 days I believe), but a restart of all gmond processes and gmetad will clean it up instantly. ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
