Attempting to update to 23.01 DEVEL corrupts my pfSense installation
-
@stephenw10 any ETA on fix or dirty workaround yet?
I have the same issues when trying to update from 22.05 to 23.01.
-
@tomfrode
Its worse than just being able to upgrade to the beta version. You also cant add or remove packages. -
If you switch the pkg repo branch back to 22.05 (stable) int he GUI then run at the command line:
pkg-static install -f pfSense-upgrade
You will have access to packages again via the GUI.
Steve
-
@stephenw10
Thank you, This allowed me to update/install packages again after switching back to 22.05.
I am going to wait for the fix to become available before I attempt the upgrade to 23.01 again. -
Netgate, take your time. Find the issue(s).
Granted this might set back the release of 23.01(as there are far fewer Beta testers), but better to have less issues in the final product.
Thank you!A loyal user since 2014.
2100 work
4100 home
I know, I know, the 4100 should be the work model, but the guy who signs the checks is a penny pincher. -
got it updated, but now I cant access web gui (blank page) also certificate errors when running pkg-static update -f
"pkg-static: https://pfsense-plus-pkg-beta00.atx.netgate.com/pfSense_plus-master_ amd64-core/packagesite.txz: Authentication error"
Any need for reset the NDI on the server?
-
Any word on a fix yet? I wont be able to test until tomorrow so I wanted to know if any changes came about or are we still expecting? Thanks
-
Not committed yet. I guess there was more involved to do it right. Let me see what I can dig up...
-
Any updates as to the resolution for this issue? I was hoping to test the update this weekend.
Thanks -
Still not working for me either, asme error: Another instance of pfSense-upgrade is running.
-
@jjstecchino I'm getting the same error too.
-
-
-
@jjstecchino
iam also getting this error -
I have tried to install 23.01 devel on my home SG3100 Web upgrade did not work at all just long wait and then return to main upgrade page. Tried CLI install it did go through however during booting process I noticed a couple of PHP 8.1 .so libraries did not load ( thrown error message, Posibly wrong binaries for SG3100 CPU?) after booting main admin page just blank page. I have reverted back to 22.05 from recovery image.
-
A more complete fix was created and committed to resolve these issues. It took a while longer than expected but should be in a snapshot shortly.
-
@stephenw10
Thanks so much for the update. -
I was experiencing this since Christmas and have been watching this thread, can confirm I've successfully updated now to build 23.01.b.20230104.0600
Thanks guys :)
-
And I can't update from 23.01.b.20230102.0600 to 23.01.b.20230104.0600. Before that it was updated every day.
-
@viper_rus
t was not possible to determine pkg remote versionHow to fix it?
-
That isn't necessarily a show-stopping error. Try running
pfSense-upgrade -d
at the command line.Steve
-
@stephenw10
Upgrade went without issue, pulled everything and installed.
PFBlockerNG-Dev had some php issues that resolved with a reboot.Now I am seeing issues with Dynamic DNS. Deleted the info, replaced the info(just to make sure), still no dice. Not a deal breaker, but it's a BETA.
Jan 4 07:52:22 pfSense php-fpm[369]: /rc.dyndns.update: Dynamic DNS googledomains (pfsense.xxxxx.xx): Public IP address could not be extracted from Check IP Service
Jan 4 07:52:22 pfSense php-fpm[369]: /rc.dyndns.update: Dynamic DNS (pfsense.xxxxx.xx) There was an error trying to determine the public IP for interface - wan (ix3 ).
Jan 4 07:52:26 pfSense php-cgi[426]: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/system-sensors.rrd N:U:U:U' returned exit code '1', the output was 'ERROR: /var/db/rrd/system-sensors.rrd: expected 4 data source readings (got 3) from N'
Jan 4 07:52:26 pfSense php-cgi[426]: rc.bootup: Creating rrd update scriptServices like DNSBL doesn't show up, yet unbound does. Maybe it is supposed to be that way, IDK.
I've rebooted 5 times, just to make sure.
Do feel free to move this, as it was a "successful" update from 22.05 to 23.01DEV, but with issues.