"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

I had to reboot. pfBlocker cron job was stuck at 100% before that.

wufwuf

@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???

stephenw10

Nope that looks like something different. That line is not actually an error, that's always shown.

Try hitting ctl+t and see if it responds with whatever process is stuck.

TheNarc

@stephenw10 Thank you for this! What an unmitigated clusterfornication this has been. Well, that's not true, you've helped mitigate it! But wow.

stephenw10

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....

TheNarc

@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!

wufwuf

@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?

stephenw10

Yup as shown in the above post: https://forum.netgate.com/post/1185688

SteveITS

@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.

stephenw10

Yup, exactly.

wufwuf

@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!'

stephenw10

Version _16 reverts the last change but it appears the issue is deeper than that...

SteveITS

@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. ٩(͡๏̯͡๏)۶

stephenw10

Ha, yup. Testing _17....

stephenw10

Looks good:

>>> Installing 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 12 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	gnugrep: 3.11 [pfSense]
	grepcidr: 2.0 [pfSense]
	iprange: 1.0.4 [pfSense]
	jq: 1.7_1 [pfSense]
	lighttpd: 1.4.72 [pfSense]
	lua54: 5.4.6 [pfSense]
	nettle: 3.9.1 [pfSense]
	pfSense-pkg-pfBlockerNG-devel: 3.2.0_17 [pfSense]
	py311-maxminddb: 2.4.0 [pfSense]
	py311-sqlite3: 3.11.6_8 [pfSense]
	rsync: 3.2.7 [pfSense]
	xxhash: 0.8.2 [pfSense]

Number of packages to be installed: 12

The process will require 18 MiB more space.
5 MiB to be downloaded.
[1/12] Fetching py311-sqlite3-3.11.6_8.pkg: ... done
[2/12] Fetching lighttpd-1.4.72.pkg: .......... done
[3/12] Fetching gnugrep-3.11.pkg: .......... done
[4/12] Fetching nettle-3.9.1.pkg: .......... done
[5/12] Fetching lua54-5.4.6.pkg: .......... done
[6/12] Fetching jq-1.7_1.pkg: .......... done
[7/12] Fetching grepcidr-2.0.pkg: . done
[8/12] Fetching xxhash-0.8.2.pkg: ...... done
[9/12] Fetching iprange-1.0.4.pkg: .. done
[10/12] Fetching rsync-3.2.7.pkg: .......... done
[11/12] Fetching pfSense-pkg-pfBlockerNG-devel-3.2.0_17.pkg: ........ done
[12/12] Fetching py311-maxminddb-2.4.0.pkg: .. done
Checking integrity... done (0 conflicting)
[1/12] Installing nettle-3.9.1...
[1/12] Extracting nettle-3.9.1: .......... done
[2/12] Installing lua54-5.4.6...
[2/12] Extracting lua54-5.4.6: ......... done
[3/12] Installing xxhash-0.8.2...
[3/12] Extracting xxhash-0.8.2: .......... done
[4/12] Installing py311-sqlite3-3.11.6_8...
[4/12] Extracting py311-sqlite3-3.11.6_8: ........ done
[5/12] Installing lighttpd-1.4.72...
===> Creating groups.
Using existing group 'www'.
===> Creating users
Using existing user 'www'.
[5/12] Extracting lighttpd-1.4.72: .......... done
[6/12] Installing gnugrep-3.11...
[6/12] Extracting gnugrep-3.11: .......... done
[7/12] Installing jq-1.7_1...
[7/12] Extracting jq-1.7_1: .......... done
[8/12] Installing grepcidr-2.0...
[8/12] Extracting grepcidr-2.0: ..... done
[9/12] Installing iprange-1.0.4...
[9/12] Extracting iprange-1.0.4: ..... done
[10/12] Installing rsync-3.2.7...
[10/12] Extracting rsync-3.2.7: .......... done
[11/12] Installing py311-maxminddb-2.4.0...
[11/12] Extracting py311-maxminddb-2.4.0: .......... done
[12/12] Installing pfSense-pkg-pfBlockerNG-devel-3.2.0_17...
[12/12] Extracting pfSense-pkg-pfBlockerNG-devel-3.2.0_17: .......... done
Saving updated package information...
done.
Loading package configuration... done.
Configuring package components...
Loading package instructions...
Custom commands...
Executing custom_php_install_command()...
Rebuilding GeoIP tabs... done.
Creating Firewall filter service... done.
Renew Firewall filter executables... done.
Starting Firewall filter Service... done.

Creating DNSBL service... done.
Renew DNSBL lighttpd executable... done.
Creating DNSBL web server config ... done.
Creating DNSBL Certificate... done.
Starting DNSBL Service... done.

Upgrading previous settings:
 Adv. Inbound firewall rule settings... no changes required ... done.
 OpenVPN/IPSec interface selections... no changes required ... done.
 Proofpoint/ET IQRisk settings... no changes required ... done.
 General Tab -> IP Tab settings... no changes required ... done.
 pfBlockerNGSuppress Alias -> IPv4 Suppression Customlist... no changes required ... done.
 Upgrading previous EasyLists to new format... no changes required ... done.
 Upgrading previous Firefox DoH to new format... no changes required ... done.
 MaxMind License Key configuration setting... no changes required ... done.
 Validating Widget cron settings... no changes required ... done.
Upgrading... done

Custom commands completed ... done.
Executing custom_php_resync_config_command()...done.
Menu items... done.
Services... done.
Writing configuration... done.
=====
Message from grepcidr-2.0:

--
===>   NOTICE:

The grepcidr port currently does not have a maintainer. As a result, it is
more likely to have unresolved issues, not be up-to-date, or even be removed in
the future. To volunteer to maintain this port, please create an issue at:

https://bugs.freebsd.org/bugzilla

More information about port maintainership is available at:

https://docs.freebsd.org/en/articles/contributing/#ports-contributing
=====
Message from rsync-3.2.7:

--
Some scripts provided by rsync, such as rrsync,
require Python, which is not installed by default.
>>> Cleaning up cache... done.
Success

Bug reverted. Thanks @marcosm

Digging further commences....