Actions
Regression #13697
closed
pfSense - Feature #13446: Upgrade PHP from 7.4 to 8.1
pfBlockerNG alerts error on 2.7.0 devel and PHP 8.1
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Affected Version:
2.7.0
Affected Plus Version:
Affected Architecture:
amd64
Description
Getting the following error:
Crash report begins. Anonymous machine information:
amd64
14.0-CURRENT
FreeBSD 14.0-CURRENT #0 devel-main-n255802-8d2600d5897c: Thu Oct 20 06:30:27 UTC 2022 root@freebsd:/var/jenkins/workspace/pfSense-CE-snapshots-master-main/obj/amd64/BmxMzMyh/var/jenkins/workspace/pfSense-CE-snapshots-master-main/sources/FreeBSD-src-de
Crash report details:
PHP Errors:
[23-Nov-2022 22:51:46 America/Regina] PHP Fatal error: Uncaught TypeError: fclose(): Argument #1 ($stream) must be of type resource, bool given in /usr/local/www/pfblockerng/pfblockerng_alerts.php:4043
Stack trace:
#0 /usr/local/www/pfblockerng/pfblockerng_alerts.php(4043): fclose(false)
#1 {main}
thrown in /usr/local/www/pfblockerng/pfblockerng_alerts.php on line 4043
No FreeBSD crash data found.
This is from a 2.6.0-devel system upgraded to 2.7.0-devel
Files
| Screenshot from 2022-12-09 18-22-37.png (172 KB) Screenshot from 2022-12-09 18-22-37.png | pfblocker dashboard widget | ||
| Screenshot from 2022-12-09 18-28-46.png (279 KB) Screenshot from 2022-12-09 18-28-46.png | top page php errors |
Updated by Jim Pingle almost 2 years ago
- Tracker changed from Bug to Regression
- Parent task set to #13446
Updated by Reid Linnemann almost 2 years ago
- Status changed from New to Feedback
This should be fixed in CE as of e912a45 for all logfiles. Merge to plus forthcoming.
Updated by Chris W almost 2 years ago
- File Screenshot from 2022-12-09 18-22-37.png Screenshot from 2022-12-09 18-22-37.png added
- File Screenshot from 2022-12-09 18-28-46.png Screenshot from 2022-12-09 18-28-46.png added
Not seeing the original error anymore with -devel version 3.1.0_14 on:
2.7.0-DEVELOPMENT (amd64)
built on Fri Dec 09 06:13:30 UTC 2022
FreeBSD 14.0-CURRENT
However I do get PHP errors at the top of the page after navigating some of the sub-pages of Firewall > PfBlockerNG. The full message is displayed in the pfBlocker dashboard widget:
array(4) { [0]=> string(7) "pfsense" [1]=> string(17) "installedpackages" [2]=> string(11) "pfblockerng" [3]=> string(6) "config" } array(1) { [0]=> array(17) { ["enable_cb"]=> string(2) "on" ["pfb_keep"]=> string(2) "on" ["pfb_interval"]=> string(1) "1" ["pfb_min"]=> string(1) "0" ["pfb_hour"]=> string(1) "0" ["pfb_dailystart"]=> string(1) "0" ["skipfeed"]=> string(1) "0" ["log_max_log"]=> string(5) "20000" ["log_max_errlog"]=> string(5) "20000" ["log_max_extraslog"]=> string(5) "20000" ["log_max_ip_blocklog"]=> string(5) "20000" ["log_max_ip_permitlog"]=> string(5) "20000" ["log_max_ip_matchlog"]=> string(5) "20000" ["log_max_dnslog"]=> string(5) "20000" ["log_max_dnsbl_parse_err"]=> string(5) "20000" ["log_max_dnsreplylog"]=> string(5) "20000" ["log_max_unilog"]=> string(5) "20000" } } array(4) { [0]=> string(7) "pfsense" [1]=> string(17) "installedpackages" [2]=> string(11) "pfblockerng" [3]=> string(6) "config" } array(1) { [0]=> array(17) { ["enable_cb"]=> string(2) "on" ["pfb_keep"]=> string(2) "on" ["pfb_interval"]=> string(1) "1" ["pfb_min"]=> string(1) "0" ["pfb_hour"]=> string(1) "0" ["pfb_dailystart"]=> string(1) "0" ["skipfeed"]=> string(1) "0" ["log_max_log"]=> string(5) "20000" ["log_max_errlog"]=> string(5) "20000" ["log_max_extraslog"]=> string(5) "20000" ["log_max_ip_blocklog"]=> string(5) "20000" ["log_max_ip_permitlog"]=> string(5) "20000" ["log_max_ip_matchlog"]=> string(5) "20000" ["log_max_dnslog"]=> string(5) "20000" ["log_max_dnsbl_parse_err"]=> string(5) "20000" ["log_max_dnsreplylog"]=> string(5) "20000" ["log_max_unilog"]=> string(5) "20000" } }
MaxMind:
Updated by Jim Pingle almost 2 years ago
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
Those other errors were unrelated and were corrected a few snaps ago.
Actions