"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
-
Hmm, that's odd.
I would try to remove then reinstall pfBlocker. You may need to kill those pkg processes to allow that.
-
Hello
I have the same error and problem on my PFSense 6100 Max.
I have upgrade to the las version of pfBlockerNG 3.2.0_12.
I have reboot, re-install PFSense, try to delete the package nothing to do....
The package pfBlockerNG 3.2.0_12 is always present.
How we can reinitalize the PFSense and in the same time delete all the packages forcefully?
Thanks
Best regards
Laurent -
You are still seeing the pkg upgrade process running?
-
@stephenw10 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:
You are still seeing the pkg upgrade process running?
no, there is no upgrade process running
worse, I am haven't access to the package manager ... Always work in progress to display the packages
Is it possible to format all the PFSense to reset all without packages?
I think it's the better solution to fix the problem today... -
I mean as shown above there are no stuck pkg processes in system activity or output of
ps aux?You can remove pkgs from the CLI.
You can reset the config if required.
-
Yes but on my PFSense, impossible to delete the package.
The processus start but block at one moment and not continue....
I don't understand why... -
Try removing it from the command line with:
pkg remove pfSense-pkg-pfBlockerNG
See what errors you get. If any. -
Hello
I Have execute many time the command and after multi iterration, I have finally removed pfBlocker...
I have wait a very long time between the execution and the waiting the system said me the remove it's done or in error...
Very strange this version 12 of pfBlocker...
The next time, I will wait many time before upgrade my version..
Laurent -
-
@Hirugoba
Eventually I did "factory reset" and after some poking around "/etc/inc/util.inc" error happened couple times more.Reinstalled appliance from image (24.03) and re-configured it manually (I mean not from back-up).
-
@Gertjan Hello
I have juste do a update the PFBlocker when I have see the button "Update" on the package manager for a version available....
I don't know if it's a dev or release version...
On my PFSense I am in 24.03 also but at one moment in june or may there is this package available... and after a lot of problems...
Bug? Maybe .... -
AFAIK that would only ever have been available in 24.08-dev. If you somehow selected the dev branch and then didn't upgrade to 24.08 you might have seen the update the pfBlocker. If you then tried to upgrade to that without first upgrading to 24.08 it would probably have failed.
If you are running ZFS I would roll back to the last good BE and upgrade again to 24.03 (if needed). -
For my part, I never use a dev version, only a stable.
So for the probability of the selection of dev branch is very very low... -
@rabbiwan
Ok, thanks for the feedback.AFAIK, the pfSense Packet Manager offers today, for me pfBlockerng-devel version 3.2.0_10 - the _12 has not been released yet. It is in the works, though.
If you remove / de install this _12 version and _12 is proposed upon install again, consider your system 'not well'.
As stated above, as you have ZFS, roll back to a more stable situation - the real pfSense '24.03'.
See it like this : you don't want Microsoft 11 updates if you have Windows 10 installed, that will break your system. -
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.
