Crash report or programming bug v2.7.2

ntllanbase

Hi,

we have a pfsense VM in production several years ago...

we have a warning in the appliance... "pfSense has detected a crash report or programming bug. Click here for more information" PHP error.

we add log file: PHP_errors.zip

We don't know what can happen.

Can you help us, please ?

Thanks

stephenw10

Duplicated PHP error:

[25-Jan-2024 17:24:36 Europe/Madrid] PHP Fatal error:  Uncaught TypeError: array_path_enabled(): Argument #1 ($arr) must be of type array, int given, called in /etc/inc/config.lib.inc on line 1250 and defined in /etc/inc/util.inc:3662
Stack trace:
#0 /etc/inc/config.lib.inc(1250): array_path_enabled(-1, 'notifications/s...', 'disable')
#1 /etc/inc/notices.inc(379): config_path_enabled('notifications/s...', 'disable')
#2 /etc/inc/notices.inc(662): notify_via_smtp('pfSense is rest...')
#3 /etc/inc/notices.inc(151): notify_all_remote('pfSense is rest...')
#4 /etc/inc/config.lib.inc(239): file_notice('config.xml', 'pfSense is rest...', 'pfSenseConfigur...', '')
#5 /etc/inc/config.lib.inc(695): restore_backup('/cf/conf/backup...')
#6 /usr/local/www/pkg_edit.php(233): write_config('')
#7 {main}
  thrown in /etc/inc/util.inc on line 3662
[25-Jan-2024 17:24:36 Europe/Madrid] PHP Fatal error:  Uncaught TypeError: array_path_enabled(): Argument #1 ($arr) must be of type array, int given, called in /etc/inc/config.lib.inc on line 1250 and defined in /etc/inc/util.inc:3662
Stack trace:
#0 /etc/inc/config.lib.inc(1250): array_path_enabled(-1, 'notifications/s...', 'disable')
#1 /etc/inc/notices.inc(379): config_path_enabled('notifications/s...', 'disable')
#2 /etc/inc/notices.inc(662): notify_via_smtp('PHP ERROR: Type...')
#3 /etc/inc/notices.inc(151): notify_all_remote('PHP ERROR: Type...')
#4 /etc/inc/config.lib.inc(1154): file_notice('phperror', 'PHP ERROR: Type...', 'PHP errors')
#5 [internal function]: pfSense_clear_globals()
#6 {main}
  thrown in /etc/inc/util.inc on line 3662

Not seeing any reference to that specifically. Any idea what triggered that? Any other errors logged?

Steve

ntllanbase

Thanks for your answer...

We don't have any previous errors.
The only intervention was a binding DNS record setup two days ago.

This bug is a long time.

BR

stephenw10

Something there is logging a lot to make the logs rotate every few minutes like that.