On 7-10-2013 21:23, [email protected] wrote:
>> What you can try is dumping the old 2.0 config with RRD data, and then
>> restore that after upgrade. Try that.
>>
>> It should also retrigger a config upgrade at that point and upgrade the
>> databases.
>
> Thanks for your suggestion. I tried backing up just RRD data and restoring
> that, and a complete config backup including RRD data and restoring that,
> neither of which caused the issue to fix itself. Obviously this is all
> post-upgrade, having already upgraded 2.0.3 to 2.1.
> Have you any more suggestions please?
No, you need to supply the 2.0 config with RRD data, otherwise it won't
work. The 2.1 config is of no use as it considers the data to already be
upgraded.
You should have a full backup from before you started the upgrade, right?
Alternatively you can try this:
Go to the command prompt page
include("shaper.inc")
include("upgrade_config.inc")
include("rrd.inc")
upgrade_080_to_081();
Make sure to backup beforehand.
Kind regards,
Seth
>> No idea why it isn't doing that for you. I only know of issues on nanobsd.
>
> I'm seeing this on the 7 upgrades I've done so far.
>
> Thanks
>
>
>
> _______________________________________________
> List mailing list
> [email protected]
> http://lists.pfsense.org/mailman/listinfo/list
>
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list
