What to do with Diagnostic Crash Report
-
Hi
I saw this in Diagnostic Creash Reporter after I was trying to map a new network interface but after some searching I can't see what to do with it:
The firewall has encountered an error
Debugging output can be collected to share with pfSense developers or others providing support or assistance.Crash report begins. Anonymous machine information: amd64 14.0-CURRENT FreeBSD 14.0-CURRENT amd64 1400094 #1 RELENG_2_7_2-n255948-8d2b56da39c: Wed Dec 6 20:45:47 UTC 2023 root@freebsd:/var/jenkins/workspace/pfSense-CE-snapshots-2_7_2-main/obj/amd64/StdASW5b/var/jenkins/workspace/pfSense-CE-snapshots-2_7_2-main/sources/F Crash report details: PHP Errors: [20-Mar-2025 22:17:10 Europe/London] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #2 ($path) must be of type string, null given, called in /usr/local/www/interfaces.php on line 1320 and defined in /etc/inc/util.inc:3573 Stack trace: #0 /usr/local/www/interfaces.php(1320): array_get_path(Array, NULL) #1 {main} thrown in /etc/inc/util.inc on line 3573 [20-Mar-2025 22:17:35 Europe/London] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #2 ($path) must be of type string, null given, called in /usr/local/www/interfaces.php on line 1320 and defined in /etc/inc/util.inc:3573 Stack trace: #0 /usr/local/www/interfaces.php(1320): array_get_path(Array, NULL) #1 {main} thrown in /etc/inc/util.inc on line 3573 [20-Mar-2025 22:17:47 Europe/London] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #2 ($path) must be of type string, null given, called in /usr/local/www/interfaces.php on line 1320 and defined in /etc/inc/util.inc:3573 Stack trace: #0 /usr/local/www/interfaces.php(1320): array_get_path(Array, NULL) #1 {main} thrown in /etc/inc/util.inc on line 3573 [20-Mar-2025 22:20:14 Europe/London] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #2 ($path) must be of type string, null given, called in /usr/local/www/interfaces.php on line 1320 and defined in /etc/inc/util.inc:3573 Stack trace: #0 /usr/local/www/interfaces.php(1320): array_get_path(Array, NULL) #1 {main} thrown in /etc/inc/util.inc on line 3573 [20-Mar-2025 22:23:18 Europe/London] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #2 ($path) must be of type string, null given, called in /usr/local/www/interfaces.php on line 1320 and defined in /etc/inc/util.inc:3573 Stack trace: #0 /usr/local/www/interfaces.php(1320): array_get_path(Array, NULL) #1 {main} thrown in /etc/inc/util.inc on line 3573 [20-Mar-2025 22:40:22 Europe/London] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #2 ($path) must be of type string, null given, called in /usr/local/www/interfaces.php on line 1320 and defined in /etc/inc/util.inc:3573 Stack trace: #0 /usr/local/www/interfaces.php(1320): array_get_path(Array, NULL) #1 {main} thrown in /etc/inc/util.inc on line 3573 No FreeBSD crash data found. -
Sorry, I don't have an answer. Just replying so I can follow this topic.
I have a fresh Netgate installed, and after a few configuration changes, I got a crash report about PHP, so I'm also curious what to do with it:
[25-Mar-2025 18:41:02 <Timezone>] PHP Fatal error: str_ireplace(): Cannot use output buffering in output buffering display handlers in /usr/local/www/csrf/csrf-magic.php on line 165
-
@mr-brunes said in What to do with Diagnostic Crash Report:
PHP Errors:
[20-Mar-2025 22:17:10 Europe/London] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #2 ($path) must be of type string, null given, called in /usr/local/www/interfaces.php on line 1320 and defined in /etc/inc/util.inc:3573
Stack trace:
#0 /usr/local/www/interfaces.php(1320): array_get_path(Array, NULL)
#1 {main}
thrown in /etc/inc/util.inc on line 3573What exactly did you do? Do you have any steps to replicate it?
-
@stephenw10 said in What to do with Diagnostic Crash Report:
@mr-brunes said in What to do with Diagnostic Crash Report:
PHP Errors:
[20-Mar-2025 22:17:10 Europe/London] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #2 ($path) must be of type string, null given, called in /usr/local/www/interfaces.php on line 1320 and defined in /etc/inc/util.inc:3573
Stack trace:
#0 /usr/local/www/interfaces.php(1320): array_get_path(Array, NULL)
#1 {main}
thrown in /etc/inc/util.inc on line 3573What exactly did you do? Do you have any steps to replicate it?
IIRC I'd just added a new interface and I was trying to assign it. It happened twice and my WAN link was down so recording exact steps wasn't exactly my priority.
TBH most times I've seen this type of diagnostics on systems there's an easy subsequent way to submit it plus logs etc. to dev.
But in this case that appears to be lacking. -
So you added a new NIC and that caused your WAN to go down. I assume it was the WAN interface/NIC you added. You replaced an existing NIC?
-
@stephenw10 no my WAN was down and I was trying to add a new interface to act as a backup.
But TBH this is a side issue, the main point is that there is no guidance on how to submit diagnostic crash reports, despite the UI nagging about their presence. -
There is no official method for doing so. Waay back in the day there was a button on page to automatically submit them to our crash-reporter but it became impractical to continue using it.
For php errors like this there is often only the error shown there. Other logs might be in the main system log surrounding it showing what was happening at that time.
Are you able to replicate it?
-
@stephenw10 ah OK. Shame that feature has gone, but the expectation of submission was left in UI.
Replication is an issue as it entails downtime which is pretty difficult ATM. I suspect it may be related in some way to the USB Wifi adapters I was using and that FreeBSD support is not great in that space. -
Ah, yes indeed that could well have contributed at least. Still shouldn't have thrown an error though.
