Moving RRDs from one version of rrdtool to another
I wish to move a Hobbit monitor that has been running for quite some time on a Solaris platform, to a new Linux server that I setup. I did not want to lose the history for the hosts so I copied the data directory to the new host, but it seems the rrd files are not compatible as I have missing graph links. I checked the permissions and they are okay.
Hmm I checked rrdtool versions and here's what I found: Solaris: rrdtool version 1.0.49 Linux: rrdtool version 1.2.18-1
- Now I am assuming that the problem is the difference in the rrdtool versions. I don't really want to roll back to an older version on the linux box.
- After some research it looks like rrdtool has an option to dump an rrd to XML. You can then import that XML to another rrdtool version. I will try that and report if it works or not.
Note: I'm not asking a specific question in this post...I'm mostly just "thinking out loud" in case my problem and resolution helps others who search the mailing list.
-Charles
Charles Jones wrote :
- Now I am assuming that the problem is the difference in the rrdtool versions. I don't really want to roll back to an older version on the linux box.
Hi,
I had the same problem, the cause is that Sparc and Intel/PC hardware have different endianess.
What I did is what you suggest, dump, copy, restore. The trick is you have to restore on the target host. Installing two versions of rrdtool on the solaris box won't do.
Regards,
-- Charles Goyard - charles.goyard at orange-ftgroup.com - (+33) 1 45 38 01 31 Orange Business Services - online multimedia // ingénierie
Indeed...it should be simple, but of course I'm having some unknown problem :)
/usr/local/rrdtool-1.0.49/bin/rrdtool xport la.rrd
ERROR: can't parse 'la.rrd'
ls -l la.rrd
-rw-r--r-- 1 hobbit other 19572 May 29 09:02 la.rrd
I truss'd the command and don't see any reason for it to fail. the last thing that happens before the failure is checking my timezone: 18476: open("/usr/share/lib/zoneinfo/US/Arizona", O_RDONLY) = 3 18476: fstat64(3, 0xFFBE68F0) = 0 18476: read(3, " T Z i f\0\0\0\0\0\0\0\0".., 130) = 130 18476: close(3) = 0 18476: time() = 1180454799 18476: fstat64(2, 0xFFBE6548) = 0 ERROR: 18476: write(2, " E R R O R : ", 7) = 7 can't parse 'la.rrd'18476: write(2, " c a n ' t p a r s e ".., 20) = 20
Meh. -Charles
Charles Goyard wrote:
Charles Jones wrote :
- Now I am assuming that the problem is the difference in the rrdtool versions. I don't really want to roll back to an older version on the linux box.
Hi,
I had the same problem, the cause is that Sparc and Intel/PC hardware have different endianess.
What I did is what you suggest, dump, copy, restore. The trick is you have to restore on the target host. Installing two versions of rrdtool on the solaris box won't do.
Regards,
Wow. Yet again I figure something out immediately after I click *send*. Looks like I needed to use "dump" instead of "xport". xport was the option in the older version, which I thought I had. :)
-Charles
Charles Jones wrote:
Indeed...it should be simple, but of course I'm having some unknown problem :)
/usr/local/rrdtool-1.0.49/bin/rrdtool xport la.rrd
ERROR: can't parse 'la.rrd'
ls -l la.rrd
-rw-r--r-- 1 hobbit other 19572 May 29 09:02 la.rrd
I truss'd the command and don't see any reason for it to fail. the last thing that happens before the failure is checking my timezone: 18476: open("/usr/share/lib/zoneinfo/US/Arizona", O_RDONLY) = 3 18476: fstat64(3, 0xFFBE68F0) = 0 18476: read(3, " T Z i f\0\0\0\0\0\0\0\0".., 130) = 130 18476: close(3) = 0 18476: time() = 1180454799 18476: fstat64(2, 0xFFBE6548) = 0 ERROR: 18476: write(2, " E R R O R : ", 7) = 7 can't parse 'la.rrd'18476: write(2, " c a n ' t p a r s e ".., 20) = 20
Meh. -Charles
Charles Goyard wrote:
Charles Jones wrote :
- Now I am assuming that the problem is the difference in the rrdtool versions. I don't really want to roll back to an older version on the linux box.
Hi,
I had the same problem, the cause is that Sparc and Intel/PC hardware have different endianess.
What I did is what you suggest, dump, copy, restore. The trick is you have to restore on the target host. Installing two versions of rrdtool on the solaris box won't do.
Regards,
Unfortunately RRD files are architecture dependant, you'll have to do an rrdtool dump transfer xml files to new server then rrdtool restore on each file to get it into the arch type.
http://oss.oetiker.ch/rrdtool/doc/rrddump.en.html
Mike
-----Original Message----- From: Charles Jones [mailto:jonescr at cisco.com] Sent: 29 May 2007 16:44 To: hobbit at hswn.dk Subject: [hobbit] Moving RRDs from one version of rrdtool to another
I wish to move a Hobbit monitor that has been running for quite some time on a Solaris platform, to a new Linux server that I setup. I did not want to lose the history for the hosts so I copied the data directory to the new host, but it seems the rrd files are not compatible
as I have missing graph links. I checked the permissions and they are okay.
Hmm I checked rrdtool versions and here's what I found: Solaris: rrdtool version 1.0.49 Linux: rrdtool version 1.2.18-1
- Now I am assuming that the problem is the difference in the rrdtool versions. I don't really want to roll back to an older version on the linux box.
- After some research it looks like rrdtool has an option to dump an rrd to XML. You can then import that XML to another rrdtool version. I will try that and report if it works or not.
Note: I'm not asking a specific question in this post...I'm mostly just "thinking out loud" in case my problem and resolution helps others who search the mailing list.
-Charles
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
This email has been scanned for all viruses by the MessageLabs service.
This email has been scanned for all viruses by the MessageLabs service.
participants (3)
-
charles.goyard＠orange-ftgroup.com
-
jonescr＠cisco.com
-
Mike.Rowell＠Rightmove.co.uk