rrd update error after 4.2 install
list Rich Smrcina
I installed a new 4.2 system today and copied all of the old history and rrd files from a 4.1.2 system. All of the history seems just fine, but updating the rrd files seems problematic. For each host and test that causes an rrd update of a copied file, I get the following in /var/log/hobbit/rrd-status.log: 2006-08-26 21:46:02 RRD error updating /home/hobbit/data/rrd/vtpsrv/memory.actual.rrd from 172.17.0.12: rrd->ds_def malloc The old system was architecture s390 (which is 32-bit) the new system is architecture s390x (which is 64-bit). Is that the difference, or are there other reasons that rrd files not transportable? Thanks. -- Rich Smrcina VM Assist, Inc. Phone: XXX-XXX-XXXX Ans Service: XXX-XXX-XXXX user-61add9955ef9@xymon.invalid Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007
list Henrik Størner
▸
On Sat, Aug 26, 2006 at 09:51:04PM -0500, Rich Smrcina wrote:
All of the history seems just fine, but updating the rrd files seems problematic. For each host and test that causes an rrd update of a copied file, I get the following in /var/log/hobbit/rrd-status.log: 2006-08-26 21:46:02 RRD error updating /home/hobbit/data/rrd/vtpsrv/memory.actual.rrd from 172.17.0.12: rrd->ds_def malloc The old system was architecture s390 (which is 32-bit) the new system is architecture s390x (which is 64-bit). Is that the difference, or are there other reasons that rrd files not transportable?
In general you cannot move rrd files across different platforms without doing an "rrdtool dump" on the old system and "rrdtool restore" on the new one. I have never seen this particular error before, but it is something from the rrdtool library, so I would suspect that this is the problem. Regards, Henrik
list Rich Smrcina
I expected as much and will work on a mass dump and restore script. Thanks.
▸
Henrik Stoerner wrote:On Sat, Aug 26, 2006 at 09:51:04PM -0500, Rich Smrcina wrote:All of the history seems just fine, but updating the rrd files seems problematic. For each host and test that causes an rrd update of a copied file, I get the following in /var/log/hobbit/rrd-status.log: 2006-08-26 21:46:02 RRD error updating /home/hobbit/data/rrd/vtpsrv/memory.actual.rrd from 172.17.0.12: rrd->ds_def malloc The old system was architecture s390 (which is 32-bit) the new system is architecture s390x (which is 64-bit). Is that the difference, or are there other reasons that rrd files not transportable?In general you cannot move rrd files across different platforms without doing an "rrdtool dump" on the old system and "rrdtool restore" on the new one. I have never seen this particular error before, but it is something from the rrdtool library, so I would suspect that this is the problem. Regards, Henrik
-- Rich Smrcina VM Assist, Inc. Phone: XXX-XXX-XXXX Ans Service: XXX-XXX-XXXX user-61add9955ef9@xymon.invalid Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007
list Francesco Duranti
I moved some times ago from a rhel3-32bit to rhel4-64 bit and I had to export the data on the 32 bit machine and reimport on the 64 bit to have working rrd files for hobbit and mrtg... It's just a bit long but you only need to do a dump/restore of them. Francesco
▸
-----Original Message----- From: Rich Smrcina [mailto:user-cf452ff334e0@xymon.invalid] Sent: Sunday, August 27, 2006 4:51 AM To: user-ae9b8668bcde@xymon.invalid Subject: [hobbit] rrd update error after 4.2 install I installed a new 4.2 system today and copied all of the old history and rrd files from a 4.1.2 system. All of the history seems just fine, but updating the rrd files seems problematic. For each host and test that causes an rrd update of a copied file, I get the following in /var/log/hobbit/rrd-status.log: 2006-08-26 21:46:02 RRD error updating /home/hobbit/data/rrd/vtpsrv/memory.actual.rrd from 172.17.0.12: rrd->ds_def malloc The old system was architecture s390 (which is 32-bit) the new system is architecture s390x (which is 64-bit). Is that the difference, or are there other reasons that rrd files not transportable? Thanks. -- Rich Smrcina VM Assist, Inc. Phone: XXX-XXX-XXXX Ans Service: XXX-XXX-XXXX user-61add9955ef9@xymon.invalid Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007
list Rich Smrcina
Yes, as I expected. Thanks.
▸
Francesco Duranti wrote:I moved some times ago from a rhel3-32bit to rhel4-64 bit and I had to export the data on the 32 bit machine and reimport on the 64 bit to have working rrd files for hobbit and mrtg... It's just a bit long but you only need to do a dump/restore of them. Francesco-----Original Message----- From: Rich Smrcina [mailto:user-cf452ff334e0@xymon.invalid] Sent: Sunday, August 27, 2006 4:51 AM To: user-ae9b8668bcde@xymon.invalid Subject: [hobbit] rrd update error after 4.2 install I installed a new 4.2 system today and copied all of the old history and rrd files from a 4.1.2 system. All of the history seems just fine, but updating the rrd files seems problematic. For each host and test that causes an rrd update of a copied file, I get the following in /var/log/hobbit/rrd-status.log: 2006-08-26 21:46:02 RRD error updating /home/hobbit/data/rrd/vtpsrv/memory.actual.rrd from 172.17.0.12: rrd->ds_def malloc The old system was architecture s390 (which is 32-bit) the new system is architecture s390x (which is 64-bit). Is that the difference, or are there other reasons that rrd files not transportable? Thanks. -- Rich Smrcina VM Assist, Inc. Phone: XXX-XXX-XXXX Ans Service: XXX-XXX-XXXX user-61add9955ef9@xymon.invalid Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007
-- Rich Smrcina VM Assist, Inc. Phone: XXX-XXX-XXXX Ans Service: XXX-XXX-XXXX user-61add9955ef9@xymon.invalid Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007