PHP Crash Report
-
Those seem to be consistent with one thing we'd see when it runs out of disk space during the upgrade. We have some safety belts to prevent that but there are still some ways it can happen unexpectedly mid-upgrade if it's borderline before starting.
If you have ZFS boot environments, make sure there aren't so many that it's filling up the disk. If you are regularly tracking snapshots it's easy for those to pile up. Go in and clean out all but the last few.
-
@jimp I'm getting the same errors after upgrading to 23.01, as seen here: PHP_errors.log.txt
Space doesn't seem to be an issue thought, as I have ~400 GB of free space left on my disk.
The errors stop appearing, when I disable the pfSense integration for home assistant that pulls the pfSense for statistics.
-
Then it's possible the code in that Home Assistant feature needs updated to reflect changes in pfSense Plus 23.01, the base OS (FreeBSD 14), or the new PHP version (8.1).
-
Upon bumping to beta from 22.05 I also got a php error. Most likely unimportant. Checking the package manager it showed an update available for pfblockerng.
Including error for due diligence:Crash report begins. Anonymous machine information: amd64 14.0-CURRENT FreeBSD 14.0-CURRENT #0 plus-devel-main-n255998-693fad75fe3: Fri Jan 6 06:28:49 UTC 2023 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/obj/amd64/0khU7V4C/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBS Crash report details: PHP Errors: [25-Jan-2023 17:59:36 America/Denver] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/widgets/widgets/pfblockerng.widget.php:473 Stack trace: #0 /usr/local/www/widgets/widgets/pfblockerng.widget.php(987): pfBlockerNG_get_failed() #1 /usr/local/www/index.php(430): include('/usr/local/www/...') #2 {main} thrown in /usr/local/www/widgets/widgets/pfblockerng.widget.php on line 473 [25-Jan-2023 18:00:48 America/Denver] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/widgets/widgets/pfblockerng.widget.php:473 Stack trace: #0 /usr/local/www/widgets/widgets/pfblockerng.widget.php(987): pfBlockerNG_get_failed() #1 /usr/local/www/index.php(430): include('/usr/local/www/...') #2 {main} thrown in /usr/local/www/widgets/widgets/pfblockerng.widget.php on line 473 No FreeBSD crash data found.
-
Hehe...as the error is in the silly widget on the front dashboard...well things are a little difficult. Upon triggering that error, can't really click the bell for other alerts or any of the rest of the interface.
Ok I give up; how does one remove a borked widget from the dashboard via command line? With the php errors; the web interface is completely useless.Update w/workaround:
/usr/local/www/widgets/include/ mv widget-pfblockerng.inc widget-pfblockerng.inc.bakk /usr/local/www/widgets/widgets mv pfblockerng.widget.php pfblockerng.widget.php.bakk
Interface now normal and can set about reinstalling things properly.
-
There were known issues with pfBlockerNG on 23.01 which have been corrected in the repo but aren't in public builds yet. Once we publish RC builds you can upgrade and add that back.
-
@jimp rock on.
-
-
[26-Jan-2023 19:33:00 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 [26-Jan-2023 19:33:00 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 [26-Jan-2023 19:33:00 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
-
-
This is not a catch-all topic for any errors people see. Please start your own threads for different error messages.