I am not sure what was the issue, but restarting the services for ganglia did the trick. Thanks for the reply, Abhi.
Ofer Inbar wrote: > There's a bug in gmond 3.1 (possibly fixed by now, I don't know) such > that when a gmond is rebooted, it can take a long time before it gets > notified of the other nodes already running. Each gmond broadcasts > its presence once at startup, so the gmond that's been up the longest > will have the right count of all the others (so if you reboot the > whole cluster, that's the first one that starts up), but the rest will > take a while, you just have to wait. > > We had several threads about this last year, you can look in the list > archives. > -- Cos > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
