Attempting to update to 23.01 DEVEL corrupts my pfSense installation
-
Ok, that looks like a bug: https://redmine.pfsense.org/issues/13831
Should be fixed in the next snap. -
@opit-gmbh Do you have any of the upgrade logs from that? Any other errors shown?
The chances of hitting that bug we found are extremely low.
-
@stephenw10
Fixed the situation like this.- I made a backup of the settings.
- Restored an older image (22.05),
- updated to the latest version of 23.01,
- restored setting from backup
-
@viper_rus Is this what you were getting?
I'm not sure it's really an issue though since it seems to complete the checks fine in the end?
This is running the pfSense-upgrade -d as Stephen suggested.
-
@chickendog
I was getting this error in the WEB interface and the installation process was interrupted. Perhaps it was possible to fix it with the proposed option, I'll use it next time :))) But at the moment I have the last snapshot ;) -
@viper_rus Ah ok I see, yeah I have no error in the web interface but have it via CLI. I'll see if it persists. I assume for now I'm on the latest build and there just hasn't been a new one since 23.01.b.20230104.0600
-
Upgrade completed successfully.
-
@stephenw10 all set. Cleared the .rrd file.
Reinstalled pfb-ng. Services now show.Dynamic DNS is still wonky. Using the default which is http://checkip.dyndns.org. It does resolve to my address. Will wait and see what the next snap brings us.
-
@stephenw10
where i can find this logs? and what can i do now to get my Netgate working ? ;) -
This post is deleted! -
@chickendog said in Attempting to update to 23.01 DEVEL corrupts my pfSense installation:
@viper_rus Ah ok I see, yeah I have no error in the web interface but have it via CLI. I'll see if it persists. I assume for now I'm on the latest build and there just hasn't been a new one since 23.01.b.20230104.0600
Confirming I've again upgraded successfully to 23.01.b.20230105.0600 from 23.01.b.20230104.0600. So looks like my pkg remote version errors are fixed - for now ;)
-
I also upgraded successfully to 23.01.b.20230105.0600 from 23.01.b.20230104.0600 in the web interface. And now there is not even a message that I do not have a plus license :)
Maybe someone will tell. For a long time now, when I load phsense, two lines appear
OpenVPN settings...done
route: route has not been found
route: route has not been found
Configuring firewall......done.Can't find the reason for these errors
-
Last night I was not able to upgrade a fresh install from 2.6.0 to plus. Kept getting package and cert errors. Can someone confirm if its an issue on my end or a netgate issue.
Thanks so much -
Failed upgrading from 2.6 to 22.01? Nothing has changed there AFAIK. Testing...
-
@stephenw10
Thanks for testing, hoping its just me... -
Upgrades still working as expected for me here. No change since I last tested it. Which is as expected since nothing has changed there.
-
Thanks for testing for me. Tonight I'll try again. I'm going to do a fresh install of 2.6 to plus to dev.
-
I updated successfully last night from 2.6 to plus 22.01 to 22.05 to 23.01 no problem.
Restored a test config containing haproxy and a few other apps to 23.01 and worked successfully.
No switch or script needed once on 23.01Any new news on when the RC will be? I'm gonna chalk up to the night before upgrade issues maybe some type of network issue. Thanks again for testing the upgrade for me.
-
'Real soon now'
No way to know for sure. There are still a few things we need to iron out before we can build an RC. But not many.
Steve
-
@yellowrain 23.01 upgrade success :
-GUI feels snappier
-Upload speed improved ;)23.01-BETA (amd64) built on Fri Jan 06 06:04:43 UTC 2023 FreeBSD 14.0-CURRENT
Had to :
-reverse to 22.05 branch,
-"pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade" (https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html),
-switch to 23.01 DEVEL
-upgrade.