PHP Crash Report

HPA_Support

i logged into our firewall and notice an orange banner saying "pfSense has detected a crash report or programming bug. Click here for more information" Any ideas on what is causing this?

Crash Report Details:
Crash report begins. Anonymous machine information:

amd64
11.2-RELEASE-p10
FreeBSD 11.2-RELEASE-p10 #9 10fea60fdde(factory-RELENG_2_4_4): Thu May 16 06:55:01 EDT 2019 root@buildbot1-nyi.netgate.com:/build/factory-crossbuild-244/obj/amd64/bwlyKhYx/build/factory-crossbuild-244/pfSense/tmp/FreeBSD-src/sys/pfSense

Crash report details:
PHP Errors:
[21-Jan-2021 13:58:01 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'readline.so' (tried: /usr/local/lib/php/20170718/readline.so (Shared object "libreadline.so.7" not found, required by "readline.so"), /usr/local/lib/php/20170718/readline.so.so (Cannot open "/usr/local/lib/php/20170718/readline.so.so")) in Unknown on line 0

No FreeBSD crash data found.

Gertjan

This :

@hpa_support said in PHP Crash Report:

11.2-RELEASE-p10

is the start of 'problems'.

Let's take an old blog post from the authors :
pfSense 2.4.5 : it says :

What happens :
First : the preparation : still unknown, but people stay at old versions .....
Then : they continue to upgrade packages, that could be based on newer PHP versions, like PHP 7.2 -> 7.3. When the package gets installed, dependencies are cheked : it sees the system has PHP 7.x and it want PHP 7.y, where y is higher : so PHP gets updated.
Now everything is set for the fireworks.

Consider your system broken.
Backup the config now !!
Upgrade pfSense to 2.4.5-p1 (february 2021).

If there is a reason to stay on an older version of pfSense : ok, up to you. But, do what the doc says : do not upgrade packages any more !

stephenw10

Yes, you should upgrade to 2.4.5p1. You may need to do this:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

Steve

HPA_Support

@gertjan ok thnx. looks like another IT person installed a package that im guessing is not fully supported with 2.4.4

stephenw10

It may or may not be but the important thing is if your package repo was still set to 'latest stable' and not '2.4.4 deprecated' it will have pulled in incompatible libraries causing the errors you're now seeing.
To be sure I would probably backup the config and install 2.4.5p1 clean. Or wait for 2.5 at this point and then install that clean.

Steve