RRD errors at boot

[biggsy]

Anyone know what might cause these errors at boot?

2013-10-10 20:07:19	User.Error	192.168.11.1	Oct 10 20:05:00 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/wan-traffic.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 12 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
2013-10-10 20:07:19	User.Error	192.168.11.1	Oct 10 20:05:00 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/wan-packets.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 12 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
2013-10-10 20:07:19	User.Error	192.168.11.1	Oct 10 20:05:00 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/lan-traffic.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: could not lock RRD'
2013-10-10 20:07:19	User.Error	192.168.11.1	Oct 10 20:05:00 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/lan-packets.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 12 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
2013-10-10 20:07:19	User.Error	192.168.11.1	Oct 10 20:05:00 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/ipsec-traffic.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 12 data source readings (got 8) from N:U:U:U:U:U:U:U:U'
2013-10-10 20:07:19	User.Error	192.168.11.1	Oct 10 20:05:00 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/ipsec-packets.rrd N:U:U:U:U:U:U:U:U' returned exit code '1', the output was 'ERROR: expected 12 data source readings (got 8) from N:U:U:U:U:U:U:U:U'

[biggsy]

I searched back through logs and it looks like a result of switching architecture from 32-bit to 64-bit but that was back when I installed 2.1 beta.

Strange that the error suddenly changed from "This RRD was created on other architecture" which I had never noticed.

Reset the RRD data and all appears to be OK.