Upgrade 2.3 to 2.7.2 issues with config restore
-
Similar to a few others, got some php errors I cannot identify when restoring my config on 2.7.2. All interfaces aren't mapped upon boot up and return to that state after a reboot.
PHP ERROR: Type: 1, File: /etc/inc/upgrade_config.inc, Line: 5444, Message: Uncaught TypeError: Cannot access offset of type string on string in /etc/inc/upgrade_config.inc:5444
Stack trace:
#0 /etc/inc/config.lib.inc(519): upgrade_172_to_173()
#1 /usr/local/pfSense/include/www/backup.inc(405): convert_config()
#2 /usr/local/www/diag_backup.php(63): execPost(Array, Array)
#3 {main}
thrown @ 2025-02-15 20:48:21config-20250215051619-donotbackuppackageor-rrd-data-sanitized-to-share.xml -
Hmm, interesting since you don't have any ppp interfaces. First thing I would try is simply removing the
<ppps/>line from your old config before importing it. -
@stephenw10
Thanks for the tip! I removed the entire <ppps><ppps/> line and no luck, same experience when restoring. -
Hmm, where did the sanitized config above come from then? I was assuming that's what you're trying to import? But that only has a single
<ppps/>line. -
It's mine. I took a backup before the upgrade. One with package and rrd data and one without them. Not sure which one i should be restoring with. I tried both at first. Neither one worked.
I only tried without package and rrd data with your modified suggestion so far. Which is the sanitized config.xml I shared.
Should I be restoring with package data and rrd data?
Thank you.
-
Hmm, it shouldn't make any difference.
Did you ever try importing it into any other version?
-
@stephenw10
I did not, yet. Couldn't find a recommended upgrade path for going between the versions, and read i should be able to restore from most any version.If there is a recommended upgrade path from 2.3.x to 2.7.x I would try to go down to something else in the iterim, if it helps at all?
-
Indeed, you should be able to import that directly.
Are you able to upload the full config to us to run some tests?
-
@stephenw10
Yes, full config meaning...un-sanitized? or not a config.xml?Is there a safe way to share that?
-
Yes the full config if you can. If not then at least soemthing that still hit's this error when you try to recover it.
You can upload files here: https://nc.netgate.com/nextcloud/s/myLNdL9CbWeKWqT
-
@stephenw10
Thank you! I dropped 2 unsantized config.xmls there, one with the package & rrd data and one without. -
@sneakking said in Upgrade 2.3 to 2.7.2 issues with config restore:
Any luck with my configs I uploaded?
Thank you.
-
@sneakking Hello, how do you are trying the update?
Did you try a clean install then a restore from gui? Instead updating an old version with conf on?
If doesn't work (you may need to refit interfaces) you may take the clean conf from new install, and take the parts of config you need from the old one and override the sections. -
Ah, sorry this got swamped. Let me test....
-
Yup seeing that error. Digging....
-
Ok so this is fixed in newer versions. It was fixed between 24.03 and 24.11 which means it will be fixed in 2.8 but that doesn't help much in 2.7.2! unfortunately there were a lot of changes went in at that time so it's not straight forward to patch in 2.7.2.
However I was able to workaround it by manually updating the vlan config format and removing the ppp line from the config file. It then imported successfully.
So replace
_vlanwith.and remove<ppps></ppps>.I have a modified file I can send you if you need it.
-
@stephenw10
Thank you! I have been running on a modified version of my old config that I updated to what I needed most, but afraid to reboot because of the issue I was seeing before.I exported my current modified config, edited the file with your suggestions to _vlan and ppps and it seems to hold the config now after being restored/rebooted. Darn that formatting.
Not seeing the PHP error anymore like I was persistently seeing.
Thank you again for all your help!
-
No worries. It is a legitimate bug. You should just be able to import it. But because it's already fixed it's unlikely to see much traction in 2.7.2. At least there's a relatively easy workaround.
