Version 2.5.2 Upgrade > 2.6.0 or 2.7.0

[stephenw10]

Hmm, that's an odd set of errors. It's pointing at the correct repo url but has the wrong ABI set.

Check: /usr/local/share/pfSense/pkg/repos/pfSense-repo.abi that should show 14.

Also check: /usr/local/etc/pkg.conf that should also list the abi and altabi which should both be 14. When you select the 2.7 branch those values should be copied into there.

Check what pkg versions you've ended up with. This is what I see:

[2.5.2-RELEASE][admin@cedev-3.stevew.lan]/root: pkg-static info -x pfsense
pfSense-2.5.2
pfSense-Status_Monitoring-1.7.11_4
pfSense-base-2.5.2
pfSense-default-config-2.5.2
pfSense-kernel-pfSense-2.5.2
pfSense-rc-2.5.2
pfSense-repo-2.7.0_2
pfSense-repoc-20230616
pfSense-upgrade-1.0_33
php74-pfSense-module-0.72

Steve

[old_man_noBS]

@stephenw10 getting the same error as the OP when I tried to upgrade from 2.5.2 to 2.7.

FreeBSD:14:amd64

pfSense-2.5.2
pfSense-Status_Monitoring-1.7.11_3
pfSense-base-2.5.2
pfSense-default-config-2.5.2
pfSense-kernel-pfSense-2.5.2
pfSense-pkg-System_Patches-2.2.4
pfSense-rc-2.5.2
pfSense-repo-2.7.0_2
pfSense-repoc-20230616
pfSense-upgrade-1.0_33
php74-pfSense-module-0.72

[old_man_noBS]

At this point, I just want to reinstall pfgblocker but it fails, probably the same error. Then I can just do a fresh install on another machine

[Finger79]

@Delodien said in Version 2.5.2 Upgrade > 2.6.0 or 2.7.0:

Any help would be appreciated! We can manually install 2.7.0 and copy the config over, which works, but we'd rather not do that to 30+ appliances...

This might still be the quickest and safest path to victory, plus it gives you a chance to reinstall as ZFS instead of UFS.

[SteveITS]

@old_man_noBS You can’t install pfBlocker if you’re on 2.5, there is not a path to do so. Previous Stable branch would be 2.6. Need to be installing for the version you have.

[old_man_noBS]

@SteveITS my repo stuff was messed up, in the GUI I set the update back to 2.6 and then ran the commands in this order:

• pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade

• pkg-static bootstrap -f

• pfSense-upgrade -d -c

This did the trick, then I upgrade to 2.6 and then 2.7, but pfblocker was missing some whitelists once I reinstalled it.

Thanks for the help

[Delodien]

@stephenw10

So both pfSense-repo.abi and pkg.conf both state "14".

When I run pkg-static info -x pfsense I get the below:

pkg-static: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
pfSense-2.5.2
pfSense-Status_Monitoring-1.7.11_3
pfSense-base-2.5.2
pfSense-default-config-2.5.2
pfSense-kernel-pfSense-2.5.2
pfSense-rc-2.5.2
pfSense-repo-2.7.0_2
pfSense-repoc-20230616
pfSense-upgrade-1.0_33
php74-pfSense-module-0.72

I thought I'd try the commands put forward by old_man_noBS while I was testing, this resulted in the below (sorry for the long snippets!)

[2.5.2-RELEASE][admin@pfSense.home.arpa]/root: pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
pkg-static: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
The following package files will be deleted:
        /var/cache/pkg/pfSense-repo-2.5.2_3~fa1de5fcfd.txz
        /var/cache/pkg/pkg-1.17.5_3~b8e15d34b2.pkg
        /var/cache/pkg/pfSense-repo-2.5.2_3.txz
        /var/cache/pkg/pkg-1.17.5_3.pkg
        /var/cache/pkg/pfSense-repo-2.6.0_13~0d7a433338.pkg
        /var/cache/pkg/pfSense-upgrade-1.0_33~bc1ca8a51c.pkg
        /var/cache/pkg/pfSense-repo-2.6.0_13.pkg
        /var/cache/pkg/pfSense-upgrade-1.0_15~0cc5b4f75f.pkg
        /var/cache/pkg/pfSense-upgrade-1.0_15.pkg
        /var/cache/pkg/pfSense-repo-2.7.0_2~bbaf1ea8ca.pkg
        /var/cache/pkg/pfSense-repo-2.7.0_2.pkg
        /var/cache/pkg/pfSense-repoc-20230616~d7b634de39.pkg
        /var/cache/pkg/pfSense-upgrade-1.0_33.pkg
        /var/cache/pkg/libucl-0.8.2~2abcb45dce.pkg
        /var/cache/pkg/pfSense-repoc-20230616.pkg
        /var/cache/pkg/uclcmd-0.2.20211204.pkg
        /var/cache/pkg/libucl-0.8.2.pkg
        /var/cache/pkg/uclcmd-0.2.20211204~9a8a1b81fc.pkg
The cleanup will free 9 MiB
Deleting files: 100%
All done
pkg-static: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.pkg: 100%  156 KiB 159.4kB/s    00:01
Processing entries:   0%
pkg-static: Newer FreeBSD version for package zstd:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1400085
- running kernel: 1202504

pkg-static: repository pfSense contains packages for wrong OS version: FreeBSD:14:amd64
Processing entries: 100%
Unable to update repository pfSense
Error updating repositories!

[2.5.2-RELEASE][admin@pfSense.home.arpa]/root: pkg-static bootstrap -f
pkg-static: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
pkg(8) is already installed. Forcing reinstallation through pkg(7).
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg from pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0, please wait...
pkg: Error fetching https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/Latest/pkg.txz: Not Found
A pre-built version of pkg could not be found for your system.
Consider changing PACKAGESITE or installing it from ports: 'ports-mgmt/pkg'.

[2.5.2-RELEASE][admin@pfSense.home.arpa]/root: pfSense-upgrade -d -c
pfSense-repoc-static: si_get_packages: failed to run the pkg info command: /usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-\* 2>&1
pfSense-repoc-static: no pfSense packages installed
pfSense-repoc-static: invalid signature
failed to read the repo data.
failed to update the repository settings!!!
failed to update the repository settings!!!

[Delodien]

Sorry for the double post!

I've revisited this and following the steps old_man_noBS completed again, this time ensuring I was set to the 2.6.0 channel instead of 2.7.0.

I ran the commands mentioned and then clicked on update on the WebUI and the system went through the update process as expected.

Once it got to 2.6.0, it then went to 2.7.0 fine using the usual method.

Obviously not ideal but definitely better than doing it manually!

[arkanista]

@old_man_noBS Thanks, this solution worked perfectly.

[Clouseau]

@old_man_noBS Had exactly the same issue that you had and these commands fixed the situasion! Thank you for posting this!

[gimpyviper]

@old_man_noBS This worked like an absolute champ. Thanks!!

[SteveITS]

FWIW the 3 commands above are detailed here:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

pfSense-pkg-System_Patches-2.2.4

Was there a System Patches package for 2.5.2? If not and/or it was installed from a 2.6 or 2.7 repo that could well mess things up (per my sig). v2.2.4 is the version I have on my router with 23.05.1...it says it's out of date currently but it would have been current a few months ago.

[mikeisfly]

@old_man_noBS This did the trick for me, thanks.

[Sergei_Shablovsky]

@Finger79 said in Version 2.5.2 Upgrade > 2.6.0 or 2.7.0:

@Delodien said in Version 2.5.2 Upgrade > 2.6.0 or 2.7.0:

Any help would be appreciated! We can manually install 2.7.0 and copy the config over, which works, but we'd rather not do that to 30+ appliances...

This might still be the quickest and safest path to victory, plus it gives you a chance to reinstall as ZFS instead of UFS.

At this time I suggest starting to using Ansible. (Ansible great in case that You have also a lot of active network equipment. Because You still using 2.5… in 2023, so maybe You have a lot of CONSOLE-controlled equipment also ;)

Ansible help You saving a THOUSANDS of $/hour.

[wimlauwaert]

@old_man_noBS Tnx ! Worked like a charm.