23.01 -> 23.05 upgrade failed
-
Upgraded the Jetway to 23.05 via the console this morning. Worked but I lost all of my add ons.
Note: I did this all live while swapping cables here leaving both firewalls on.Switched over to the Qotom which was at PFSense CE.
Updated that one over to 23.01 via the console. Took a while to update. Worked and all of my add ons were upgraded.Version 23.01-RELEASE (amd64) built on Fri Feb 10 20:06:33 UTC 2023 FreeBSD 14.0-CURRENT*** Welcome to Netgate pfSense Plus 23.01-RELEASE (amd64) on enigma ***Will wait a day or so to upgrade to 23.05. Will backup configuration and restore it to the Jetway.
-
@pete said in 23.01 -> 23.05 upgrade failed:
Worked but I lost all of my add ons.
Add ons ?
Stick a note on that box : Upgrade ? Use console ! ( ! ).
Because with the console, the same procedure looks far more cool (ok : joke).
And you've got a free bonus : if something goes wrong you would be the first to know the 'why' part.
Like, for example, "when pfSense reboots with the new kernel and thus new pfSense version, maybe it couldn't make the WAN connection work".
Then it proceeds with every installed "pfSense GUI package" :
remove it, and
re install it.The thing is : removing is easy, and can be done without any network active.
Re installing needs .... the WAN to be 'UP'.You would have made the WAN work, and - after a manual reboot, WAN would be up ... and now the "re install" would go on just fine.
All this is just my theory, as I'm upgrading pfSense using the console for the last 10 or more years now.
Waiting to see if something happens ...I guess I've been a victim of the second major advantage of the console access : When you are ready to see the error in the face .... you can't see it .... as it won't happen
So, go for that post-it.
Btw : pfSense GUI package info is still present in the config.
Just re install them.
Now you will confirm another golden rule : use as few as humanly possible.
Don't remember which ones ?
Open the config file : you can even use msword if you want to.
Look up the list, as it is in there.
Now, install them all one by one.
Do a reboot for good measures.
Re test them all.
Done.( don't forget the post-it )
-
Thank you. I meant packages. Yes here only have gone to the console when editing configuration files et al which I should never do anyhow.
Will back up running box and restore it to the Jetway in the next few days.
Historically though have used the GUI rather than the console.
It was easier on the WAF doing this at 4 AM this morning.
Now trying to update a generic 3865 6 port generic firewall with no markings on it. It has a hard time booting and I do not know why.
-
Updated Master to 23.05 via console. Upgrade worked fine:
Version 23.05-RELEASE (amd64) built on Mon May 22 15:04:36 UTC 2023 FreeBSD 14.0-CURRENT The system is on the latest version. Version information updated at Wed May 31 22:03:37 CDT 2023 -
@McPie this worked for me. Thanks!
-
Who has this errors when is trying to upgrade the pfsense from 23.01 to 23.05?
[23.01-RELEASE][admin@xqwer]/root: pfSense-upgrade >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: .. done pfSense-core repository update completed. 15 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: .......... done Processing entries: Processing entries............. done pfSense repository update completed. 549 packages processed. All repositories are up to date. >>> Upgrading pfSense-upgrade... done. pfSense-repoc-static: invalid signature failed to read the repo data. failed to update the repository settings!!! failed to update the repository settings!!!In the GUI I got this message:
Another instance of pfSense-upgrade is running. Try again laterI google it and I found this forum that is says that is solved but this is not working for me.
(SOLVED) pfSense+ Plus upgrade from 23.01 to 23.05Any one know why I cannot upgrade?
thanks.
-
@constantin Did you try the suggestions above or in the other thread?
System / Update
Update Settings / Click on Saveor
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errorsPre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
Upvote 👍 helpful posts! -
@SteveITS I did tried all those option without success.
-
On a rebuild here from scratch waited a day to update from 23.01 to 23.05 via the console. All repositories / updates worked after a day.
-
Something isn't right.
Downloads seems to stall at various pointsHave tried rebooting.
No internet issues too.pkg-static clean -ay ; pkg-static install -fy pkg pfSense-repo pfSense-upgrade The following package files will be deleted: /var/cache/pkg/pfSense-repo-23.05~9076a69f3e.pkg /var/cache/pkg/pkg-1.19.1_1~6eedfbfed3.pkg /var/cache/pkg/pfSense-repo-23.05.pkg The cleanup will free 9 MiB Deleting files: 100% All done Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 4 package(s) will be affected (of 0 checked): New packages to be INSTALLED: pfSense-repoc: 20230530_2 [pfSense] Installed packages to be UPGRADED: pfSense-repo: 23.01 -> 23.05 [pfSense] pfSense-upgrade: 1.0_58 -> 1.0_66 [pfSense] Installed packages to be REINSTALLED: pkg-1.19.1_1 [pfSense] Number of packages to be installed: 1 Number of packages to be upgraded: 2 Number of packages to be reinstalled: 1 The process will require 17 MiB more space. 14 MiB to be downloaded. [1/4] Fetching pfSense-repo-23.05.pkg: 100% 6 KiB 6.0kB/s 00:01 [2/4] Fetching pkg-1.19.1_1.pkg: 70% 6 MiB 6.0MB/s 00:00 ETAand
pkg-static clean -ay ; pkg-static install -fy pkg pfSense-repo pfSense-upgrade The following package files will be deleted: /var/cache/pkg/pfSense-repo-23.05~9076a69f3e.pkg /var/cache/pkg/pkg-1.19.1_1~6eedfbfed3.pkg /var/cache/pkg/pfSense-repo-23.05.pkg /var/cache/pkg/pkg-1.19.1_1.pkg /var/cache/pkg/pfSense-upgrade-1.0_66~c47029f80d.pkg /var/cache/pkg/pfSense-upgrade-1.0_66.pkg /var/cache/pkg/pfSense-repoc-20230530_2~16eda60f02.pkg The cleanup will free 14 MiB Deleting files: 100% All done Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 4 package(s) will be affected (of 0 checked): New packages to be INSTALLED: pfSense-repoc: 20230530_2 [pfSense] Installed packages to be UPGRADED: pfSense-repo: 23.01 -> 23.05 [pfSense] pfSense-upgrade: 1.0_58 -> 1.0_66 [pfSense] Installed packages to be REINSTALLED: pkg-1.19.1_1 [pfSense] Number of packages to be installed: 1 Number of packages to be upgraded: 2 Number of packages to be reinstalled: 1 The process will require 17 MiB more space. 14 MiB to be downloaded. [1/4] Fetching pfSense-repo-23.05.pkg: 100% 6 KiB 6.0kB/s 00:01 [2/4] Fetching pkg-1.19.1_1.pkg: 80% 7 MiB 6.3MB/s 00:00 ETA^CAre netgate servers under attack?
-
I am using AWS pfsense plus, there no internet issues.
and very strange that after running that command the upgrade worked. Last week that didn't worked.Here are my output of
pkg-static clean -ay ; pkg-static install -fy pkg pfSense-repo pfSense-upgradepkg-static: Repository pfSense-core has a wrong packagesite, need to re-create database pkg-static: Repository pfSense-core cannot be opened. 'pkg update' required The following package files will be deleted: /var/cache/pkg/pfSense-repo-23.01~6ab0bb83bb.pkg /var/cache/pkg/pkg-1.18.4_4~e5964fbef2.pkg /var/cache/pkg/pfSense-repo-23.01.pkg /var/cache/pkg/pkg-1.18.4_4.pkg /var/cache/pkg/pfSense-upgrade-1.0_61~4c43becbfa.pkg /var/cache/pkg/pkg-1.19.1_1~6eedfbfed3.pkg /var/cache/pkg/pfSense-upgrade-1.0_61.pkg /var/cache/pkg/pfSense-pkg-sudo-0.3_8~c582a59d93.pkg /var/cache/pkg/pfSense-pkg-sudo-0.3_8.pkg /var/cache/pkg/pkg-1.19.1_1.pkg /var/cache/pkg/pfSense-upgrade-1.0_66~c47029f80d.pkg /var/cache/pkg/pfSense-upgrade-1.0_66.pkg The cleanup will free 18 MiB Deleting files: 100% All done Updating pfSense-core repository catalogue... pkg-static: Repository pfSense-core has a wrong packagesite, need to re-create database Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 2 KiB 2.3kB/s 00:01 Processing entries: 100% pfSense-core repository update completed. 15 packages processed. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 3 package(s) will be affected (of 0 checked): Installed packages to be DOWNGRADED: pfSense-upgrade: 1.0_66 -> 1.0_61 [pfSense] pkg: 1.19.1_1 -> 1.18.4_4 [pfSense] Installed packages to be REINSTALLED: pfSense-repo-23.01 [pfSense] Number of packages to be reinstalled: 1 Number of packages to be downgraded: 2 9 MiB to be downloaded. [1/3] Fetching pfSense-repo-23.01.pkg: 100% 6 KiB 6.0kB/s 00:01 [2/3] Fetching pkg-1.18.4_4.pkg: 100% 9 MiB 9.5MB/s 00:01 [3/3] Fetching pfSense-upgrade-1.0_61.pkg: 100% 22 KiB 22.5kB/s 00:01 Checking integrity... done (0 conflicting) [1/3] Reinstalling pfSense-repo-23.01... [1/3] Extracting pfSense-repo-23.01: 100% [2/3] Downgrading pkg from 1.19.1_1 to 1.18.4_4... [2/3] Extracting pkg-1.18.4_4: 100% [3/3] Downgrading pfSense-upgrade from 1.0_66 to 1.0_61... [3/3] Extracting pfSense-upgrade-1.0_61: 100% You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.I don't have an explanation why that worked today and didn't last week.
thanks.
-
@SteveITS said in 23.01 -> 23.05 upgrade failed:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors
I toggled back to the previous branch (23.01)...waited...and then toggled back to (23.05)....waited... and it worked. I can see the upgrade button again. I will try to upgrade this weekend
Thanks!
-
@pfsense16v I am bumped into this discussion on google search - Can I upgrade from 23.01-RELEASE (arm64) to Version 23.05 without any issues? Are all the kinks worked out. I do not want to stuck by issues. Kindly advice
-
@netboy Not sure if you mean issues with the software, or issues with the upgrade process. There seem to be a stretch of people having "certificate" or other issues starting the upgrade. If you see that there are a few workarounds in this and other threads, basically getting it to update its repo info or certs or whatnot and proceed.
There are pre-release release notes for a 23.05.1 version, indicating that's coming in the relatively near future. That fixes a bad bug with importing aliases, though there is also a patch to fix it in the System Patches package after upgrading to 23.05.
-
@SteveITS Thanks as always.
I am talking about upgrade issues.
From your reply there seems to be something on the works to fix this
I get a sense I should wait for the upgrade.
I like my pfsense and help in this forum BUT why are there issues (mostly) during upgrade process.
I am a bit concerned of late pfsene upgrades always have some problems. Last upgrade was a problem too. Now this.
Would you advice for me to wait for the fix? -
@netboy It’s up to you really. I generally try to wait a week before our first/test upgrade and another week or two before upgrading any clients just to watch the forums. Generally have had no serious issues as a result.
-
@SteveITS I upgraded from 23.01 to 23.05 without a hitch! FYI
-
Putting this out there in case it helps others.
I kept dorking at this, tried again when 23.05.1 came out, but still couldn't get the upgrade to work. I opened a support case online, truthfully not expecting a lot of help (I have the free home-lab style license, no support).
Netgate TAC responded very quickly to the ticket (maybe 15 minutes), reviewed my notes, and requested remote access if I was ok with that. I didn't have an issue with it, provided them access, and after some digging, they found an issue with how I was loading my Solarflare 10gbe NIC.
I found two ways to do this, one using /conf/config.xml with <earlyshellcmd> and the other was in /boot/loader.conf.local. I chose to use config.xml because I used that for something else, it was easy enough.
The issue was in how the NDI was being calculated; the 10gbe NICs were not being included in the calculation.
TAC stated that the proper way to load the NIC driver was with loader.conf.local. They made that change, I rebooted, and had a new NDI. I already had a reg key I created a month ago because I thought it was a license key issue. I stuck that on, and upgrade was good to go.
This was my first exposure to Netgate TAC, and I was really impressed. They were very quick to respond, even though it was limited to the ticket (not live/phone/chat, because, I don't have a support contract). Also taking into account, this was my hardware (Dell R210ii), not a Netgate box.
