PHP Fatal error - 900 seconds exceeded in /etc/inc/util.inc on line 3852

matosc

Getting a crash

PFsense = 23.01.a.20221118.0600

=============================

Crash report begins. Anonymous machine information:

amd64
14.0-CURRENT
FreeBSD 14.0-CURRENT #0 plus-devel-main-n255985-7d61a46cc73: Fri Nov 18 06:28:36 UTC 2022 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/obj/amd64/SeP3HOn9/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBS

Crash report details:

PHP Errors:
[20-Nov-2022 19:25:03 Europe/London] PHP Fatal error: Maximum execution time of 900 seconds exceeded in /etc/inc/util.inc on line 3852

No FreeBSD crash data found.

jimp

Not sure why it would be timing out there, but it's trying to do idn_to_ascii() on some component of an alias. Could be you have an odd hostname in there somewhere that's breaking the idn conversion bit.

matosc

@jimp Not sure why i'm getting the error. All of my configurations looks correct, so no way to triage.

Here are the crash reports:

==================

Crash report begins. Anonymous machine information:

amd64
14.0-CURRENT
FreeBSD 14.0-CURRENT #0 plus-devel-main-n255985-7d61a46cc73: Fri Nov 18 06:28:36 UTC 2022 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/obj/amd64/SeP3HOn9/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBS

Crash report details:

PHP Errors:
[20-Nov-2022 19:25:03 Europe/London] PHP Fatal error: Maximum execution time of 900 seconds exceeded in /etc/inc/util.inc on line 3852
[21-Nov-2022 19:40:05 Europe/London] PHP Fatal error: Maximum execution time of 900 seconds exceeded in /etc/inc/pfsense-utils.inc on line 2442

No FreeBSD crash data found.

jimp

So that's trying to update a URL table alias from the looks of it. Maybe the whole process is just taking a long time and happens to fail at that point? Hard to say for sure, but it's definitely a problem with one of your aliases.

matosc

@jimp Ah ... firewall aliases!! I just cleaned out a number of aliases that no longer resolve. Lets see if this does the trick.

jimp

Turns out there was a regression there, not a problem in the alias data:

https://redmine.pfsense.org/issues/13685

https://github.com/pfsense/pfsense/commit/af61346825f5507889d66c142c78babee837f6e4

Fix will be in snapshots tomorrow, or you can install the System Patches package and then create an entry for af61346825f5507889d66c142c78babee837f6e4 to apply the fix.

matosc

@jimp Thank you!! Looking forward to the next snapshot.