PHP Error on update from 2.4p2 to 2.5 in /etc/inc/certs.inc and /etc/inc/config.lib.inc
-
Filed redmine bug: https://redmine.pfsense.org/issues/9431
-
Bump :)
-
Actually it isn't the PHP errors causing the problem, those are only a symptom.
I updated the Redmine issue. What packages do you have installed on systems that hit this?
-
Same as now :)
Attached.
-
What does this output?
pkg info -r aws-sdk-php73
-
@jimp said in PHP Error on update from 2.4p2 to 2.5 in /etc/inc/certs.inc and /etc/inc/config.lib.inc:
pkg info -r aws-sdk-php73
[2.4.5-DEVELOPMENT][root@.local]/root: pkg info -r aws-sdk-php73
pkg: No package(s) matching aws-sdk-php73 -
Did you have a different package installed before attempting the upgrade that is missing now? The
aws-sdk
package wasn't installed before (it was listed as new to install) so it must have been pulled in as a dependency of something.It also wants to install
postgresql95-client
which is not a base system requirement and wasn't on there before, so it must be coming from a package.Also the problem stated 2.4.4 to 2.5.0, not 2.4.5. 2.4.5 could be something different.
-
No, I have same packages as when I tried the upgrade.
I can try to upgrade again since this is VM it can be done very quickly :)
Will try in 1-2 hours when I return home. -
Same error...upg.txt
-
@maverick_slo said in PHP Error on update from 2.4p2 to 2.5 in /etc/inc/certs.inc and /etc/inc/config.lib.inc:
Same error...upg.txt
That didn't include the actual error from the next boot.
I checked all the package dependencies and I don't see any for CE that require aws-sdk-php73 so I'm still puzzled as to how it's deciding that is necessary to pull that in on the next boot.
We're shifting things to the next quarterly ports branch today, so it may be worth trying the upgrade again once a new snapshot shows up later today / tomorrow.
EDIT: Something else to try would be to remove all pfSense packages (
pkg delete pfSense-pkg-\*
) and then try the upgrade again. Then add the packages back if that worked. If that does work then it has to be from a package, then we just need to figure out which one... -
Yeah ok, will wait :)
-
Same issue here as well from 2.4.4_2 to the latest 2.5 snapshot as of April 10.
RRD and VMTools packages installed. RRD looks to be the common one from above.
-
Hi!
I have:
a) Removed all packages via GUI and upgraded, same error
b) Used command "pkg delete pfSense-pkg-*", same errorI don
t think it
s a package thing. -
@maverick_slo Unfortunately I was coming to the same conclusion and had opened a ticket and was sited as a duplicate. I was working off of a fresh install, all packages uninstalled and then executing an upgrade. Seems to only be tied to any of my arm based systems to me. All of my Intel based ones seem to be working just fine. I abandoned the upgrading on any of my arm systems and am sticking with 2.4.4-p2 for now.
Fatal error: Uncaught Error: Call to undefined function gettext() in /etc/inc/certs.inc:46 Stack trace: #0 /etc/inc/functions.inc(32): require_once() #1 /etc/ecl.php(21): require_once('/etc/inc/functi...') #2 {main} thrown in /etc/inc/certs.inc on line 46
-
For me it`s a Hyper-V machineso no arm...
-
There was a bug in pfSense-upgrade. It should be fixed on version 0.67
-
@rbgarga
Great!
So next snap should be ok? -
@maverick_slo said in PHP Error on update from 2.4p2 to 2.5 in /etc/inc/certs.inc and /etc/inc/config.lib.inc:
@rbgarga
Great!
So next snap should be ok?yes
-
@rbgarga said in PHP Error on update from 2.4p2 to 2.5 in /etc/inc/certs.inc and /etc/inc/config.lib.inc:
@maverick_slo said in PHP Error on update from 2.4p2 to 2.5 in /etc/inc/certs.inc and /etc/inc/config.lib.inc:
@rbgarga
Great!
So next snap should be ok?yes
Excellent, thank you!
-
Just had a very similar, if not the same problem today, after deciding to test out 2.5.
From 2.4.4-p2, using the gui to upgrade.
System rebooted, but threw all manner of issues on the boot, leaving the system broken.Root cause was at some point during the initial boot php-fpm crashed, and tried to write its core dump to /var/run/php-fpm.core
/var/run however is a 3.4MB ramdisk, so it failed to write the dump, and subsequently a lot of the upgrade process failed due to lack of disk space.