Kool! I did just that, but another additional thing (when wiping out the RRD
didnt help at all):
additional lines in gmond.conf for cluster-B
trusted_hosts = <IP Address of gmetad>
all_trusted = on
Now, IT WORKS!! THANKS A LOT FOLKS!! REALLY APPRECIATE YOUR PATIENCE AND
TIME!! :-)
--Nitin
On Wed, Mar 10, 2010 at 1:26 PM, Ofer Inbar <c...@aaaaa.org> wrote:
> Nitin Bharadwaj <west.ni...@gmail.com> wrote:
> > The output as of now: cluster-H has all machines in the cluster-H range
> > (10.1.0.33 to 10.1.0.45) and ONLY one host from Cluster-B range
> (10.1.1.33)
> > and that host is said to be down, although gmond is running on port 9989.
> Is
> > there still something I need to do to get this fixed?
>
> If you'd like to get a fresh start and remove all traces of former
> cluster memberships being "remembered", you may want to stop all of
> your gmetad's and gmond's, wipe out the RRD files on the gmetad host,
> and restart the cluster.
>
> You might be able to get away with simply tracking down the RRD files
> that are in the wrong cluster's subdirectory and deleting those, and
> restarting your gmetad and gmond's one by one, if you need to keep the
> cluster up. But it sounds like you're setting up a new Ganglia.
> -- Cos
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ganglia-general mailing list
Ganglia-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-general
