Hi Ron, Yes all the permissions were changed to match "nobody" for gmetad.
I'm now exploring the rrdtool dump and restore route and see if it will work. Will report after my experiment. Thanks for the suggestion. Steve -----Original Message----- From: Ron Wellnitz [mailto:ron.welln...@debeka.de] Sent: Tuesday, September 21, 2010 2:50 AM To: ganglia-general@lists.sourceforge.net Subject: Re: [Ganglia-general] rrds data mirgation from 3.0.2 to 3.1.7 Ganglia Hi Steve, the first (simple) idea ... After You have copy of the rrd-files, You have set up the rdd-file permissions for the gmetad user (e.g. nobody) ? You can also check the error_log from your web server, for errors like this. If this will not help, You can export (dump) your current data and import them to the new rrd-files. For these steps have a look at the manpages (website) from rrdtool. Regards, Ron Am 20.09.2010 16:32, schrieb CHU, STEPHEN H (ATTSI): > Hi all, > > In our production system we have Ganglia 3.0.2 running on Server A > (/var/lib/ganglia/rrds/abc) for about a year to monitor 64 3.0.2 gmond > clients so we've accumulated lots of historical data. Our plan is to > migrate the setup to the latest Ganglia 3.1.7. I recently installed > Ganglia 3.1.7 gmetad on Server B with rrdtool 1.4.4, selected one of the > 3.0.2 client (let's call it client 64), uninstalled 3.0.2 gmond and > installed 3.1.7 gmond. In addition to the 64 3.0.2 clients to be > migrated, I have 16 new 3.1.7 clients to start off with Server B. The > cluster name of the 16 new clients is "xyz". Starting up Server B gmetad > and the 16 clients created /var/lib/ganglia/rrds/xyz. No problem with > the webfrontend on Server B showing everything for the 16 clients, > including the graphs. I then stopped Server B gmetad. At this point I > have not started client 64 gmond yet. I then proceed to copy Server A's > /var/lib/ganglia/rrds/abc onto Server B's /var/lib/ganglia/rrds > directory. > Start up Server B gmetad, start up Client 64 gmond. Server B Webfrontend > will not display any graphs for cluster "abc" at all. Cluster "xyz" are > fine. > > I then proceed to try the "offline rrds" method by shutting down Server > B gmetad and Client 64 gmond. Moved /var/lib/ganglia/rrds/abc to > /var/lib/ganglia/rrds.offline/abc. Reproduce the webfrontend - copy > /var/www/html/ganglia to /var/www/html/ganglia.offline. Modified > /var/www/html/ganglia.offline/conf.php to point to > /var/lib/ganglia/rrds.offline. Start up Server B gmetad and Client 64 > gmond. http://Server-B/ganglia.offline showed both cluster "abc" and > "xyz" with no graphs. Back to http://Server-B/ganglia will show cluster > "xyz" with no problem. > > My suspicion is the incompatibility of rrds between the 3.0.2 and 3.1.7 > versions which make 3.1.7 refuse to show the graphs? Something to do > with some "timing parameters" mismatch inside the rrds between the old > and the new for the webfrontend to show? > > Any thoughts or suggestions are welcome before I stop spending more time > in this. Thanks. > > Steve > AT&T Labs CSO > > ------------------------------------------------------------------------ ------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Ganglia-general mailing list > Ganglia-general@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ganglia-general > > > ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Ganglia-general mailing list Ganglia-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-general
