I restarted Gmetad on the headnode (the only place it is running) I
restarted Gmond on the headnode. but it still reports x86 instead of x86_64
.
And I am not sure when it will ever update this "static" info. on one node,
gmond has been running for
machine_type x86 os_name Linux os_release 2.6.18-8.el5 uptime 55 days,
12:31:50
55 days and it still reports the wrong architecture (x86..)
It seems determined....
Thanks for your help in advance..
On 5/12/08, Brad Nicholes <[EMAIL PROTECTED]> wrote:
>
> > I upgraded some cluster nodes, from 32 bit OS RHEL4 to 64 bit RHEL5.1,
> but
> > the ganglia node monitor still seems to remember that the old node (with
> the
> > same name....) was x86
> >
> >>From Ganglia: Software
> >
> > OS: Linux 2.6.18-53.el5 (x86)
> >
> > logging into the node, and using uname -m
> >
> > x86_64 <- the correct installation..
> >
> > I deleted the rrd file for this node, but x86 was not stored there...
> >
> > So how can I fix this? Or is it a ganglia bug for going from 32 bits to
> 64
> > bits on the same nodename?
>
> Did you restart Gmetad? Since it really doesn't make any sense to store
> constant metrics in an RRD file, all of the constant metrics are stored and
> reported from memory by Gmetad. I believe that constant metrics are
> refreshed occasionally and eventually the correct constant metric will show
> up. However if you want to see it immediately, you will probably have to
> restart Gmetad.
>
>
--
-----------------------
Thanks
Tom
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Ganglia-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-general
