Attempting to update to 23.01 DEVEL corrupts my pfSense installation
-
OK, got it.. Thanks
-
Updated this morning and everything looks to have gone well after a few reboots and reloads to make pfblocker happy.
However, I noticed that I no longer have any selections for Branch
I was also expecting to now see an RC option but do not see that.
-
Most likely your NDI changed from that originally registered. Did you change the hardware?
-
@stephenw10 said in Attempting to update to 23.01 DEVEL corrupts my pfSense installation:
Most likely your NDI changed from that originally registered. Did you change the hardware?
Nope same exact hardware no changes. Was setup about a week and a half ago updated to plus and was waiting for the RC so I did the update this morning with no changes to hardware.
I can provide my ID if needed.
-
Yes, PM me your NDI so I can check it.
-
On Netgate 1100 upgrade from 22.05 to 23.01 didn't go well. After changing the update branch to Latest Development Snapshots, 23.01.b.20230106.0600 was offered and accepted. Gui showed the following errors early on, but other than that, upgrade seemed to go through:
Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: .......... done Processing entries: pkg-static: Newer FreeBSD version for package wol: To ignore this error set IGNORE_OSVERSION=yes - package: 1400073 - running kernel: 1203506 pkg-static: repository pfSense contains packages for wrong OS version: FreeBSD:14:aarch64 Processing entries... done Unable to update repository pfSense Error updating repositories!When 1100 restarted, Crash report greeted me:
Crash report begins. Anonymous machine information: arm64 14.0-CURRENT FreeBSD 14.0-CURRENT #0 plus-devel-main-n255998-693fad75fe3: Fri Jan 6 06:26:59 UTC 2023 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/obj/aarch64/VbZl2vrO/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/Free Crash report details: PHP Errors: [10-Jan-2023 12:00:31 UTC] PHP Warning: Failed loading Zend extension 'opcache.so' (tried: /usr/local/lib/php/20210902/opcache.so (/usr/local/lib/php/20210902/opcache.so: Undefined symbol "zend_inheritance_cache_get"), /usr/local/lib/php/20210902/opcache.so.so (Cannot open "/usr/local/lib/php/20210902/opcache.so.so")) in Unknown on line 0 [10-Jan-2023 12:00:31 UTC] PHP Warning: PHP Startup: session: Unable to initialize module Module compiled with module API=20210902 PHP compiled with module API=20190902 These options need to match in Unknown on line 0 [10-Jan-2023 12:00:31 UTC] PHP Warning: PHP Startup: bcmath: Unable to initialize module Module compiled with module API=20210902 PHP compiled with module API=20190902 These options need to match in Unknown on line 0 . . . 10-Jan-2023 12:03:06 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'xmlreader.so' (tried: /usr/local/lib/php/20210902/xmlreader.so (/usr/local/lib/php/20210902/xmlreader.so: Undefined symbol "dom_node_class_entry"), /usr/local/lib/php/20210902/xmlreader.so.so (Cannot open "/usr/local/lib/php/20210902/xmlreader.so.so")) in Unknown on line 0 [10-Jan-2023 14:03:06 Europe/Helsinki] PHP Fatal error: Uncaught TypeError: Return value of g_get() must be an instance of mixed, string returned in /etc/inc/globals.inc:411 Stack trace: #0 /etc/inc/globals.inc(129): g_get('product_version') #1 /etc/inc/config.inc(29): require_once('/etc/inc/global...') #2 /usr/local/pkg/wireguard/includes/wg_service.inc(24): require_once('/etc/inc/config...') #3 {main} thrown in /etc/inc/globals.inc on line 411 [10-Jan-2023 14:03:17 Europe/Helsinki] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/pkg/pfblockerng/pfblockerng.inc:1475 Stack trace: #0 /usr/local/pkg/pfblockerng/pfblockerng.inc(7241): pfb_build_if_list(true, false) #1 /usr/local/pkg/pfblockerng/pfblockerng.inc(10790): sync_package_pfblockerng() #2 /etc/inc/pkg-utils.inc(781) : eval()'d code(1): pfblockerng_php_pre_deinstall_command() #3 /etc/inc/pkg-utils.inc(781): eval() #4 /etc/inc/pkg-utils.inc(1093): eval_once('pfblockerng_php...') #5 /etc/rc.packages(80): delete_package_xml('pfBlockerNG-dev...', 'deinstall') #6 {main} thrown in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 1475 No FreeBSD crash data found.Checking update version failed, so before recovering back to 22.05 there was no harm in trying these commands mentioned earlier in this thread:
[22.05-RELEASE][root@plusdev-3.stevew.lan]/usr/local/libexec: rm /usr/local/etc/pkg/repos/pfSense.conf [22.05-RELEASE][root@plusdev-3.stevew.lan]/usr/local/libexec: ln /usr/local/share/pfSense/pkg/repos/pfSense-repo-devel.conf /usr/local/etc/pkg/repos/pfSense.confAfter that update indicated that 23.01.r.20230108.1514 was available and that went through to 23.01-RC without errors.
-
Hmm, yeah those errors you see are the result of an incomplete upgrade for some reason.
I would guess it was because pfBlocker failed to complete it's uninstall script.
The initial error is expected the pfSense-upgrade script allows it to continue past the ABI mismatch.
-
Upgraded from 22.05 to 23.01-BETA last month without any trouble pfBlogger being the same version as today (3.1.0_9).
-
Hmm, could be a new bug caused by some other changes then. The errors you see before that though show a PHP version mismatch.
-
@stephenw10 said in Attempting to update to 23.01 DEVEL corrupts my pfSense installation:
Yes, PM me your NDI so I can check it.
Sent via Chat function
-
Just updated to 23.01-BETA. Was expecting to see 23.01-RC. Even after a few reboots, update checks, and brach changes the option does not exist. Any guidance would be greatly appreciated.
-
There is some work happening the backend repos right now, that's expected.
-
@stephenw10 Thank you!
-
@stephenw10
Do we know if the rc is now available for install? I plan to test tonight.
Thanks -
It isn't. The Jan 6th beta snap is the current 23.01 image.
-
As you can see from the attached photo, I've updated to the RC. Has there been any further development? If there has been, how do I obtain it? I check daily through the cli, with no changes noted.
-
Not yet, we are testing internally. There will be some announcement when we have an RC snap ready for testing.
Steve
