Bug #2159
closed
Upgrade code breaks RRD databases on nano
100%
Description
Feb 1 20:28:40 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'inpass6' in '/var/db/rrd/wan-traffic.rrd'/usr/bin/nice -n20 /usr/local/bin/rrdtool graph /tmp/wan-traffic.rrd-day.png --start 1328038117 --end 1328124517 --vertical-label "bits/sec" --color SHADEA#eeeeee --color SHADEB#eeeeee --title "`hostname` - WAN :: Traffic - 1 day - 5 minutes average" --height 200 --width 620 DEF:wan-in_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass:AVERAGE DEF:wan-out_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass:AVERAGE DEF:wan-in_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock:AVERAGE DEF:wan-out_bytes_block=/var/db/rrd/wan-traffic.rrd:outblock:AVERAGE DEF:wan-in6_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass6:AVERAGE DEF:wan-out6_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass6:AVERAGE DEF:wan-in6_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock6:AVERAGE DEF:wan-out6_bytes_block=/var/db/rrd/wan-traffic.rrd:outblock6:AVERAGE CDEF:"wan-in_bits_pass=wan-in_byte
Upgrade code fails to upgrade RRD database on 2.1 which results in broken databases. This is a Alix with nanobsd
Updated by Seth Mos over 12 years ago
- Status changed from New to Resolved
This was fixed by the upgrade fixes that also affected 1.2.3 to 2.0 upgrades on alix systems.
Updated by Chris Buechler over 12 years ago
- Target version changed from 8 to 2.1
- Affected Version changed from 2.1-IPv6 to 2.1
Updated by Robert Keevil almost 12 years ago
I've just run into this after upgrading from 2.0 to 2.1 (WebGUI upgrade using pfSense-2.1-BETA1-1g-i386-nanobsd-upgrade-20121212-1059.img.gz). It's an Alix system.
Dec 14 00:25:19 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'inpass6' in '/var/db/rrd/wan-traffic.rrd'/usr/bin/nice -n20 /usr/local/bin/rrdtool graph /tmp/wan-traffic.rrd-day.png --start 1355379919 --end 1355466319 --vertical-label "bits/sec" --color SHADEA#eeeeee --color SHADEB#eeeeee --title "`hostname` - WAN :: Traffic - 1 day - 5 minutes average" --height 200 --width 620 DEF:wan-in_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass:AVERAGE DEF:wan-out_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass:AVERAGE DEF:wan-in_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock:AVERAGE DEF:wan-out_bytes_block=/var/db/rrd/wan-traffic.rrd:outblock:AVERAGE DEF:wan-in6_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass6:AVERAGE DEF:wan-out6_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass6:AVERAGE DEF:wan-in6_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock6:AVERAGE DEF:wan-out6_bytes_block=/var/db/rrd/wan-traffic.rrd:outblock6:AVERAGE CDEF:"wan-in_bits_pass=wan-in_byte
Updated by Anonymous over 11 years ago
I have also encountered this issue after upgrading tonight with 2.1-RC0 (i386) built on Tue Jul 23 09:56:03 EDT 2013. Not sure which snapshot broke it since I have updated multiple times this week and didn't notice until now.
/status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'inpass6' in '/var/db/rrd/wan-traffic.rrd'/usr/bin/nice -n20 /usr/local/bin/rrdtool graph /tmp/wan-traffic.rrd-month.png --start 1371957483 --end 1374635883 --step 3600 --vertical-label "bits/sec" --color SHADEA#eeeeee --color SHADEB#eeeeee --title "`hostname` - WAN :: Traffic - 1 month - 1 hour average" --height 200 --width 620 DEF:wan-in_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass:AVERAGE:step=3600 DEF:wan-out_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass:AVERAGE:step=3600 DEF:wan-in_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock:AVERAGE:step=3600 DEF:wan-out_bytes_block=/var/db/rrd/wan-traffic.rrd:outblock:AVERAGE:step=3600 DEF:wan-in6_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass6:AVERAGE:step=3600 DEF:wan-out6_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass6:AVERAGE:step=3600 DEF:wan-in6_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock6:AVERAGE:step=3600 DEF:wan-out6_bytes_bl
Updated by Anonymous over 11 years ago
I am also running nanobsd on a alix system
Updated by Chris Buechler about 11 years ago
- Status changed from Resolved to New
- Priority changed from Normal to High
this regressed at some point. Current status same as in original.
Updated by Renato Botelho about 11 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 42ec9337ea432906c7fa9ee99f763946fd974e3c.
Updated by Renato Botelho about 11 years ago
Applied in changeset 7ca8bef40e29d1a4ef7a641141401f51297cc101.