Bug #14405: PHP Crash report - pfSense Packages - pfSense bugtracker

Actions

Copy link

Bug #14405

open

PHP Crash report

Added by Jens Kristensen 11 months ago. Updated 11 months ago.

Status:

New

Priority:

Normal

Assignee:

Category:

pfBlockerNG

Target version:

Start date:

Due date:

% Done:

Estimated time:

Plus Target Version:

Affected Version:

Affected Plus Version:

Affected Architecture:

Description

Report attached. All I have. Let me know if you need more.
ver. 23.01.

Files

Download all files

PHP_errors.log (603 Bytes) PHP_errors.log		Jens Kristensen, 05/22/2023 10:16 PM
Log-settings.png (101 KB) Log-settings.png		Jens Kristensen, 05/23/2023 09:55 AM
FilterLogs.zip (342 KB) FilterLogs.zip		Jens Kristensen, 05/23/2023 05:56 PM
PHP_errors.log (591 Bytes) PHP_errors.log		Jens Kristensen, 06/02/2023 02:28 PM

Actions

Copy link

Updated by Jim Pingle 11 months ago

Project changed from pfSense to pfSense Packages
Category changed from PHP Interpreter to pfBlockerNG
Release Notes deleted (~~Default~~)

[22-May-2023 23:15:15 Europe/Rome] PHP Fatal error:  Uncaught ValueError: escapeshellarg(): Argument #1 ($arg) must not contain any null bytes in /usr/local/pkg/pfblockerng/pfblockerng.inc:3816
Stack trace:
#0 /usr/local/pkg/pfblockerng/pfblockerng.inc(3816): escapeshellarg('^83\\.92\\.5\\.1\x00\x00...')
#1 /usr/local/pkg/pfblockerng/pfblockerng.inc(5647): find_reported_header('83.92.5.1\x00\x00\x00\x00\x00\x00...', '/var/db/pfblock...', false)
#2 /usr/local/pkg/pfblockerng/pfblockerng.inc(1031): pfb_daemon_filterlog()
#3 {main}
  thrown in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3816

Actions

Copy link

Updated by BBcan177 . 11 months ago

What firewall log type are you using? "syslog" or "BSD"?

For some reason there are "\x00" characters in the pfSense firewall log CSV where the IP is segmented.

Actions

Copy link

Updated by Jens Kristensen 11 months ago

File Log-settings.png Log-settings.png added

I'm using BSD. Don't think I ever changed any logging settings.

Actions

Copy link

Updated by BBcan177 . 11 months ago

If this error persists, we need to get the line in the firewall log "/var/log/filter.log" that corresponds to the error so that we can do some further debugging.

When you upgraded pfsense did you have any issues? It could be that the filter log binary wasn't updated properly and is in a mismatch state?

Actions

Copy link

Updated by Jens Kristensen 11 months ago

File FilterLogs.zip FilterLogs.zip added

I am by no means a pfSense or BSD expert, but I managed to get the filter.log files (there are several) attached.

About my upgrade experience:

Backup + delete packages + reboot of v. 23.01.

Got an "Upgrade already in progress" - error, a couple of times. Google didn't help.

Had my 22.05 from right before I upgraded to 23.01 (in February) in Boot Environments. Made a copy, booted into that, and upgraded it to 23.01 and then to 23.05 with no problems. Packages installed fine as well.

Waited a little, then forced a reload of pfBlockerNG (devel).

I'm not sure when the error notification appeared, but I sent it right away.

I have no idea if the filter log binary was updated properly and/or is in a mismatched state - nor how to find out. If you can guide me, I'll do my best to get you the info.

Actions

Copy link