Version 2.5.2 Upgrade > 2.6.0 or 2.7.0

Delodien

Hey all,

We have a number of 2.5.2 virtual appliances setup and live, we had to leave them on this version due to an issue with RSC on the 2.6.0 version that caused our throughput to tank when it was installed.

2.7.0 fixes this and we want to obviously get to this version however none of our 2.5.2 boxes can update at all, whether it be to 2.6.0 or 2.7.0.

We thought this might have been a config issue so I've built a fresh 2.5.2 box completely separate to our networks and see the same issue, manifests in two ways depending on whether I use the WebUI or shell.

So from the WebUI, I can see the previous version and stable release (2.6.0 and 2.7.0 respectively) and clicking either of them in the drop down does yield a change, it supposedly finds it etc. and I get the Confirm Update button, I click this and a minute or two later it takes me to the "Updating System" screen, however this just shows a message "Please wait while the update system initializes" and it sits there indefinitely. I've left this about 20 minutes, same message.

From the shell (option 13 on the console) I get the below lines after hitting the option:

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!!!

The above is when the branch is set to 2.6.0, for 2.7.0 the message is essentially the same however I don't get the top two lines, it starts at the invalid signature message.

I've been through the troubleshooting KB but nothing seems to match our issue, however I've ran some of the refresh commands, cleaned the packages etc. but no joy.

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...

stephenw10

Hmm, it should be possible to upgrade from 2.5.2 to 2.7.0, I tested that myself. Let me restest.....

stephenw10

Hmm, still works here.
Try running pfSense-upgrade -d see if that gives you any more error info.

Invalid signature like that implies it might be trying to use the wrong repo. Try running pkg-static -d update and make sure it isn't.

Steve

Delodien

@stephenw10

So I ran pfSense-upgrade -d and I received the same error as my original post, no change there.

I ran pkg-static -d update it fetched some libraries and ended with:

pfSense repository is up to date
All repositories are up to date

For good measure I range the pfSense-upgrade -d command after this but still the same error.

stephenw10

Where is it fetching from when it succeeds with the pkg update?

What is the exact output from pfSense-upgrade -d ?

Also try running pfSense-repoc-static -D and see where that fails.

Delodien

@stephenw10

So interestingly the output of the pkg update has changed since I did it this morning (the box has been doing nothing as this is a fresh install)

DBG(1)[91478]> pkg initialized
pkg-static: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
Updating pfSense-core repository catalogue...
DBG(1)[91478]> PkgRepo: verifying update for pfSense-core
DBG(1)[91478]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[91478]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/meta.conf
DBG(1)[91478]> opening libfetch fetcher
DBG(1)[91478]> Fetch > libfetch: connecting
DBG(1)[91478]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/meta.conf with opts "i"
DBG(1)[91478]> Fetch: fetcher chosen: https
DBG(1)[91478]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/packagesite.pkg
DBG(1)[91478]> opening libfetch fetcher
DBG(1)[91478]> Fetch > libfetch: connecting
DBG(1)[91478]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/packagesite.pkg with opts "i"
DBG(1)[91478]> Fetch: fetcher chosen: https
DBG(1)[91478]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/packagesite.txz
DBG(1)[91478]> opening libfetch fetcher
DBG(1)[91478]> Fetch > libfetch: connecting
DBG(1)[91478]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/packagesite.txz with opts "i"
DBG(1)[91478]> Fetch: fetcher chosen: https
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[91478]> PkgRepo: verifying update for pfSense
DBG(1)[91478]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[91478]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/meta.conf
DBG(1)[91478]> opening libfetch fetcher
DBG(1)[91478]> Fetch > libfetch: connecting
DBG(1)[91478]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/meta.conf with opts "i"
DBG(1)[91478]> Fetch: fetcher chosen: https
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
DBG(1)[91478]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.pkg
DBG(1)[91478]> opening libfetch fetcher
DBG(1)[91478]> Fetch > libfetch: connecting
DBG(1)[91478]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.pkg with opts "i"
DBG(1)[91478]> Fetch: fetcher chosen: https
Fetching packagesite.pkg: 100%  156 KiB 159.4kB/s    00:01
DBG(1)[91478]> PkgRepo: extracting packagesite.yaml of repo pfSense
DBG(1)[91709]> PkgRepo: extracting signature of repo in a sandbox
DBG(1)[91478]> Pkgrepo, reading new packagesite.yaml for '/var/db/pkg/repo-pfSense.sqlite'
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!

I also get this when I run pfSense-repoc-static -D

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
OS: FreeBSD
OS Version: 12.2-STABLE
Platform: amd64
Product: pfSense
Version: 2.5.2-RELEASE
FS type: ufs
Language: (null)
Model: *unknown hardware*
NDI: 841ad12ddd0f415f1204
Package prefix: pfSense-pkg-
Serial: (null)
Repo path: /usr/local/etc/pfSense
Request query: {"platform":"*unknown hardware*","os":"FreeBSD","osver":"12.2-STABLE","fstype":"ufs","prod":"pfSense","ver":"2.5.2-RELEASE","ed":"Community","pkgs":"[]"}
POST data: uid=841ad12ddd0f415f1204&language=en_US&serial=&version=%7B%22platform%22%3A%22%2Aunknown+hardware%2A%22%2C%22os%22%3A%22FreeBSD%22%2C%22osver%22%3A%2212.2-STABLE%22%2C%22fstype%22%3A%22ufs%22%2C%22prod%22%3A%22pfSense%22%2C%22ver%22%3A%222.5.2-RELEASE%22%2C%22ed%22%3A%22Community%22%2C%22pkgs%22%3A%22%5B%5D%22%7D&arch=amd64
pfSense-repoc-static: invalid signature
failed to read the repo data.

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.

Version 2.5.2 Upgrade > 2.6.0 or 2.7.0

–-------------------------------------------------------------- Multible Alix 2D13, APU1,APU2,APU3 - pfSense 2.4.x 64bit Multible Vmware vSphere - pfSense 2.4.x 64bit

–--------------------------------------------------------------
Multible Alix 2D13, APU1,APU2,APU3 - pfSense 2.4.x 64bit
Multible Vmware vSphere - pfSense 2.4.x 64bit