"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
-
@stephenw10 You, Sir, are a lifesaver
-
@stephenw10 What's the difference between the normal version 3.2.09 and the devel version 3.2.0_15 ?
Lucky running pfSense as a VM I have a backup before the update mess.
-
Thank you!
@stephenw10 -
It's a good thing I found your suggestion here @stephenw10!
My box was running hot for the past few hours!
-
What I'm asking myself right now is the reason why that package remains there for update.
It needs to be pulled out asap.. -
Hmmm....
Seeing PHP using up a lot of CPU usage still...
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
97521 root 1 135 0 69M 46M CPU1 1 80:11 100.16% php
93401 root 1 135 0 69M 46M CPU2 2 140:02 100.16% php
80957 root 1 135 0 69M 46M CPU0 0 111:35 99.82% php
19662 root 1 21 0 146M 55M accept 2 0:16 0.32% php-fpm
44487 root 1 20 0 14M 3812K CPU3 3 0:00 0.08% topI will try a reboot...
-
I had to reboot. pfBlocker cron job was stuck at 100% before that.
-
@stephenw10 the pfsense box upon reboot is stuck on this line:
[fib_algo] inet.0 (bsearch4#20) rebuild_fd_flm: switching algo to radix4_lockless
line. ie not able to get into terminal - is this expected from this bug or is the box suffering from some other issue before this pfblockerng issue?
May require a complete reinstall of pfsense???
-
Nope that looks like something different. That line is not actually an error, that's always shown.
Try hitting
ctl+tand see if it responds with whatever process is stuck. -
@stephenw10 Thank you for this! What an unmitigated clusterfornication this has been. Well, that's not true, you've helped mitigate it! But wow.
-
Mmm, this is the devel package where new code is added for testing. So normally this should not affect that many people but in pfBlocker the dev pkg has almost become the default so.....
We are working on it....
-
@stephenw10 Definitely understood and appreciated! The whole situation with the "devel" and "normal" packages becoming (to my knowledge) equivalent was always confusing. Much credit for addressing this and getting help out incredibly rapidly!
-
@stephenw10 indeed, after a netflix episode it is back to the interface list / numbered menu again...
but how do i do the uninstall per above screen cap - given can't get into the GUI now? is there a CL command to uninstall as you described above?
-
Yup as shown in the above post: https://forum.netgate.com/post/1185688
-
@TheNarc 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:
whole situation with the "devel" and "normal" packages becoming (to my knowledge) equivalent was always confusing
Driving on by, from what I've seen the not-devel was not being updated much for a while so everyone started using -devel. I know we had to at one point to get MaxMind to work on all our clients. We moved back to not-devel when they became equivalent, since we follow the recommendations and uninstall packages like that during upgrades, anyway. The maintainer has posted he's going to use -devel as more like a beta version, which I think was the original intent (?). Stuff like:
@BBcan177 said in pfBlockerNG-devel v3.2.0_15:
Once these changes have baked for a few days in pfBlockerNG-devel, I will push these changes to pfBlockerNG.
-
Yup, exactly.
-
@wufwuf
found out how by searching:https://forums.freebsd.org/threads/questions-about-installing-removing-packages.93430/
now there is version _16 - being installed now...
with message 'package database is busy while closing!'
-
Version _16 reverts the last change but it appears the issue is deeper than that...
-
@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:
Version _16 reverts the last change but it appears the issue is deeper than that...
Heh, heh, classic programming...introduce bug, completely revert code, bug still exists. ٩(͡๏̯͡๏)۶
-
Ha, yup. Testing _17....
