Resolved - Unsupported (?) Configuration version 22.9

[anthonys]

I have just done a clean re-install of 23.01 on a SG-1100.
Configuration was then imported/restored from backup taken from the previously installed 22.01.
I now go to Diagnostics->Backup & Restore->Config History and there a few entries listing Version 22.2 (matching the 22.01 config I imported), then several entries for Version 22.8, but then a jump to 22.9:

4/16/23 11:04:42 	22.9 	50 KiB 	(system): Installed cron job for /usr/local/bin/php /usr/local/www/pfblockerng/pfblockerng.php cron >> /var/log/pfblockerng/pfblockerng.log 2>&1 	
	4/16/23 11:04:40 	22.8 	49 KiB 	(system): pfBlockerNG: saving Aliases

If I download a backup of the configuration file now, the first few lines confirm 22.9:

<?xml version="1.0"?>
<pfsense>
	<version>22.9</version>
	<lastchange></lastchange>
	<system>

But, I note at [https://docs.netgate.com/pfsense/en/latest/releases/versions.html](link url)

that the Config Rev for pfsense+ 23.01 is listed as 22.8, and that the future 23.05 remains at 22.8

So, am I now going to have a problem importing a backup configuration file that claims to version 22.9, into system/s that are documented to support only (up to?) 22.8.

Regards,

[stephenw10]

Hmm, I see that on an 1100 here and am able to backup and restore without an issue.

It's interesting though. Something has bumped the latest config version. You can check it in: /etc/inc/globals.inc

That particular test box has access to 23.05 so may have pulled in something newer. Yours should not though. Do you see 23.05 dev offered in System > Updates?

Steve

[anthonys]

@stephenw10 /etc/in/globals.inc contains the line:
'latest_config' => '22.9',
System->Update does not offer a "dev" Branch, only "Latest Stable Version (23.01)", and both Current Base System and Latest Base System are listed as 23.01

[stephenw10]

What date do you see on that file? ls -ls /etc/inc/globals.inc

[anthonys]

@stephenw10
Apr 16, 10:55, which is around the time I performed the configuration restore:

9 -rw-r--r-- 1 root wheel 1295 Feb 11 06:04 functions.inc
25 -rw-r--r-- 1 root wheel 15265 Apr 16 10:55 globals.inc
25 -rw-r--r-- 1 root wheel 15265 Feb 11 06:04 globals.inc.orig

I note that Backup & Restore -> Config History lists an entry at 11:06:15 about updating the config version to 22.9

4/16/23 17:04:25 	22.9 	50 KiB 	admin@192.168.2.12 (Local Database): Creating restore point before package installation. 	
	4/16/23 11:06:15 	22.9 	50 KiB 	(system): Upgraded config version level from 22.8 to 22.9 	
	4/16/23 11:04:42 	22.9 	50 KiB 	(system): Installed cron job for /usr/local/bin/php /usr/local/www/pfblockerng/pfblockerng.php cron >> /var/log/pfblockerng/pfblockerng.log 2>&1 	
	4/16/23 11:04:40 	22.8 	49 KiB 	(system): pfBlockerNG: saving Aliases

[jimp]

If you have 22.9 then you may have applied the recommended patches from the system patches package. One of them alters the memory RRD file and thus bumps the version since it has to be triggered via upgrade code.

There is no difference in the format of config.xml between 22.8 and 22.9, though, so you could safely edit the config and put it back to 22.8 if need be.

But if you reapply the system patches on 23.01 then it'll be back on 22.9 and the error will go away.

[anthonys]

@jimp
Yes, I have some of the recommended patches applied, including the one you mentioned, so a version of 22.9 is expected.
I see that https://docs.netgate.com/pfsense/en/latest/releases/versions.html now documents 23.05 as config version 22.9.
Thank you for your clarifications to resolve my concern.
Regards.