Bug #354

RRD upgrade code problems

Added by Chris Buechler over 10 years ago. Updated about 10 years ago.

RRD Graphs
Target version:
Start date:
Due date:
% Done:


Estimated time:
2.00 h
Affected Version:
Affected Architecture:


The traffic and packets graphs at a minimum are not upgraded correctly from 1.2.x to 2.0.,22532.0.html

Associated revisions

Revision c9ba2835 (diff)
Added by Seth Mos about 10 years ago

Move RRD quality databases to reflect the gateway name instead of the interface name. This should prevent a flurry of duplicate but
unused RRD files on 2.0 where we use the gateway names for the RRD file. Fix ticket #354


#1 Updated by Seth Mos about 10 years ago

  • Estimated time set to 2.00 h

I just made a replica of my entire work infrastructure in ESX with both the internal carp and the external carp cluster.
I installed them with 1.2-RELEASE, then upgraded to 1.2.3-RELEASE and then to 2.0-BETA1 2010-05-11 21:57.

Both the traffic and packets graphs on all 4 machines (5 including the dummy NAT box to get internet) when installed with 1.2 and then upgraded to 2.0-BETA1 have visible data over the timespan of a few days.

There is a issue with the Quality graphs though. The file naming with regards to the gateway names and the interface names means they should be changed during upgrades.
The old Quality graph rrd file is wan-quality.rrd, the new one is gw_wan-quality.rrd
I'll see if I can add some code to the upgrade path we have in 042 to 043

#2 Updated by Seth Mos about 10 years ago

  • Status changed from New to Feedback

#3 Updated by Seth Mos about 10 years ago

Verified that system, traffic, packets and quality graphs have been succesfully upgraded and historic data has not been lost.

Edit: Ahem, added a NOT before the lost.

#4 Updated by Seth Mos about 10 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF