"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
-
@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....
-
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. SuccessBug reverted. Thanks @marcosm
Digging further commences....
-
@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:
Ha, yup. Testing _17....
If _17 has been reverted, we should expect a _18 in a near future ?
If so, I'll just wait for that release.Bug reverted. Thanks @marcosm
Nice, thanks everyone
-
@mcury 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:
If _17 has been reverted, we should expect a _18
Too far, it was _15, then _16, now _17 is the one he is discussing:
@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:
[12/12] Extracting pfSense-pkg-pfBlockerNG-devel-3.2.0_17: .......... done
-
@SteveITS 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:
Too far, it was _15, then _16, now _17 is the one he is discussing:
Yeap, that is clear as water to me, Steve.
-
@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:
Looks good:
Metoo !
_17 up and running
-
Version
3.2.0_17has the changes reverted that caused the issue and is safe to upgrade to.That also means if you're upgrading pfSense to 24.03 and have pfBlockerNG-devel installed it will now complete correctly.
-
@stephenw10 Just upgraded to 3.2.0_17 on 2.7.2 and I'm still stuck at "Loading Package Instructions"
-
If you are upgrading from one of the effected versions, _15 or _16, you will still need to kill the DEINSTALL script that hangs there to allow it to continue.
-
@stephenw10 I killed the DEINSTALL process but the result is the same. I'm upgrading from _15.
-
Hmm, you killed the process ID shown in the ps output?
-
@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:
Hmm, you killed the process ID shown in the ps output?
yup
If I do a ps -aux | grep devel it comes back empty -
@rgrichster install non-devel then upgrade to devel. worked for me.
-
You will only see that process active whilst the pkg install/upgrade is trying to run. But killing the actual script should have worked. Killing the pkg-static process may have just aborted the whole install.
-
@stephenw10 I was able to install the non devel version and everything is working again. Guess I'll just stay here rather than upgrade to devel. Sounds like there really isn't a reason to use devel anymore.
