"PHP Fatal error: Maximum execution time of 900 seconds exceeded in /etc/inc/util.inc on line 3728" after installing latest pfBlockerNG 3.2.0_12
-
However low the probability that's the only explanation I can think of. However it was selected though if 3.2.0_12 was available then other, incompatible, pkgs likely were and could have been pulled in when you tried to update pfBlocker.
-
i had the same crush on my PFsense appliance with intel n5105 and latest stable CE version
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: [23-Jul-2024 10:58:33 Etc/UTC] PHP Fatal error: Maximum execution time of 900 seconds exceeded in /etc/inc/util.inc on line 1990 [23-Jul-2024 11:01:40 Etc/UTC] PHP Fatal error: Maximum execution time of 900 seconds exceeded in /etc/inc/util.inc on line 1990 No FreeBSD crash data found.
-
That's in a different function though, executing a command rather than creating config. Did it happen when you were doing something specific?
-
@stephenw10 Not really, actually after the crash php-fpm was going crazy and fully utilizing the CPU to 100% till i rebooted.
After that i removed pfblocker, and been working stable since then. -
But but no changes preceding the crash?
-
@stephenw10 not at all, i was outside home when it crashed.
-
Hmm, I can only assume it was part of pfBlockers auto-update process then. Is that set to run around that time?
-
Chiming in; I'm also getting same error in title on a 2100 after selecting to upgrade pfSenseBlockerNG to ver. 3.2.0_13
= =
PHP ERROR: Type: 1, File: /etc/inc/util.inc, Line: 3728, Message: Maximum execution time of 900 seconds exceeded @ 2024-08-14 18:34:29
PHP ERROR: Type: 1, File: /etc/inc/util.inc, Line: 3728, Message: Maximum execution time of 900 seconds exceeded @ 2024-08-14 18:41:55
= =Eventually, I did a hard reset. I'm able to get back to the Setup Wizard. I removed packages for snort, wireguard, IPsec but removing blockerNG is a no-go.
Also I crashed with: 50x error
From package Manager, it hangs on 'reinstall BlockerNG' here:
Upgrading pfSense-pkg-pfBlockerNG...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):Installed packages to be DOWNGRADED:
pfSense-pkg-pfBlockerNG: 3.2.0_13 -> 3.2.0_10 [pfSense]Number of packages to be downgraded: 1
[1/1] Downgrading pfSense-pkg-pfBlockerNG from 3.2.0_13 to 3.2.0_10...
[1/1] Extracting pfSense-pkg-pfBlockerNG-3.2.0_10: .......... done
Removing pfBlockerNG components...
Menu items... done.
Services... done.
Loading package instructions...
= crickets = -
@Jericho46 said in "PHP Fatal error: Maximum execution time of 900 seconds exceeded in /etc/inc/util.inc on line 3728" after installing latest pfBlockerNG 3.2.0_12:
Installed packages to be DOWNGRADED:
pfSense-pkg-pfBlockerNG: 3.2.0_13 -> 3.2.0_10 [pfSense]Hmm, how did you get the _13 pkg version? Did you select 24.08-dev at some point?
I would uninstall it entirely and then install it clean.
-
@stephenw10 That version was available on my status page, and in Package manager, so I selected to (upgrade). That was super late Monday night / Tues after midnight. I usually check the status page every day and there was 4 or 5 updates that night, which is very unusual.
-
Hmm that should never have been available in 24.03 AFAIK. 3.2.0_10 is current version of the package in 24.03.
I would remove it entirely and then install it again clean.
-
This post is deleted! -
You also switched to 24.08?
If so remove it. Switch the branch back to 24.03 and reinstall 3.2.0_10.
-
@stephenw10 uhm hey, I'm getting this error on _15 tonight trying to upgrade from _08
PHP ERROR: Type: 1, File: /etc/inc/util.inc, Line: 3631, Message: Maximum execution time of 900 seconds exceeded
-
@incith The same has happened to me. The web UI is completely unresponsive; I rebooted and after another 15 minute timeout the console login prompt showed up. PHP is using 100% of the cpu. I tried reverting back to backup #5 (the one that was autocreated before updating pfblockerNG), then rebooting. No change; it’s as if it didn’t restore from the earlier backup at all. I’m now attempting to deinstall pfblockerNG from the command line and it’s been stuck at “loading package instructions” for many minutes.
-
@gigabitwanted said in "PHP Fatal error: Maximum execution time of 900 seconds exceeded in /etc/inc/util.inc on line 3728" after installing latest pfBlockerNG 3.2.0_12:
and it’s been stuck at “loading package instructions” for many minutes
Yep, that's what I saw ....
Interrupting it after 'PHP' staying at 100 % for half on hours or so, and still blocked on “loading package instructions”, pfSense started, to use a previous ZFS ! (I use Plus), so the GUI cert was to old, and because stupid me was using SHTS certs .... :( so locked out nicely.
SSH and console was still ok.
The previous ZFS was based upon the original 24.03 and 24.03_1 was available, so ok lets upgrade ... but no, that re installs packages also so when it reaches pfBlockerng ..... blocked again.
Nice rabbit hole.De-installed pfBlockerng for the moment.
-
G Gertjan referenced this topic on
-
similar experience going from _08 to _15 on 2.7.2 CE edition... can no longer get to \status\dashboard menu also, and uninstalling pfblockerng from package manager is unresponsive.
in the meantime internet access and other menus continue to work...
what is the best resolution out there at this moment please?
-
@wufwuf Same here, did an update before coming here. It just hangs until timeout.
>>> Upgrading pfSense-pkg-pfBlockerNG-devel... Updating pfSense-core repository catalogue... Fetching meta.conf: Fetching packagesite.pkg: pfSense-core repository is up to date. Updating pfSense repository catalogue... Fetching meta.conf: Fetching packagesite.pkg: pfSense repository is up to date. All repositories are up to date. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-pkg-pfBlockerNG-devel: 3.2.0_8 -> 3.2.0_15 [pfSense] Number of packages to be upgraded: 1 The operation will free 1 MiB. 2 MiB to be downloaded. [1/1] Fetching pfSense-pkg-pfBlockerNG-devel-3.2.0_15.pkg: ......... done Checking integrity... done (0 conflicting) [1/1] Upgrading pfSense-pkg-pfBlockerNG-devel from 3.2.0_8 to 3.2.0_15... [1/1] Extracting pfSense-pkg-pfBlockerNG-devel-3.2.0_15: .......... done Removing pfBlockerNG-devel components... Menu items... done. Services... done. Loading package instructions... Removing pfBlockerNG...grep: /var/unbound/pfb_dnsbl.conf: No such file or directory All customizations/data will be retained... done. Saving updated package information... overwrite! Loading package configuration... done. Configuring package components... Loading package instructions... -
I tried removing pfBlockerNG then reinstall it and it still hangs on update.
-
Mmm, OK seeing that in 2.7.2 with the devel package here too. Appears to be an issue with the pkg install/deinstall script. Digging....
