"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
-
@DBMandrake For what it's worth, I got out of this mess by removing the devel version from the command line and installing the non-devel version, and it appears as if all my config from the devel version carried over to non-devel.
-
@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:
@DBMandrake For what it's worth, I got out of this mess by removing the devel version from the command line and installing the non-devel version, and it appears as if all my config from the devel version carried over to non-devel.
Did you install the non-devel version through the GUI package manager or from the command line ?
I would have to check but I think the only feature of pfBlockerNG that I'm actually using is the Google/Youtube/Bing safesearch DNS entries, as its a lot easier to tick a box in pfBlockerNG to achieve this than manually enter (and maintain) dozens of entries in Unbound!
If the config carries over I think I will do this so I'm not on the "bleeding edge". (Although this is the first time I've actually had an issue with the devel version to be fair)
-
Once you have removed the bad devel pkg by killing the script process you can reinstall either pfBlockerNG version and it should work. And include the existing settings.
-
@stephenw10 Is it unusual for two different packages in PFSense to share the same configuration files / backup ? Or are these two packages mutually exclusive so only one can be installed at the same time ? (Using the same configuration file directories)
-
@DBMandrake I did it via the cli because at the time the GUI was being problematic due to the original devel-version issue.
-
@DBMandrake 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:
s it unusual for two different packages in PFSense to share the same configuration files / backup ?
Yes, I'm not sure any other package does (maybe HAProxy-dev). Yes they are mutually exclusive.
-
OH wow, i think i found my issue related to this pfblocker package. How can i just disable it via cli that way i can get into the gui and sort it out later?
-
@gacpac If the GUI is stuck and not responding log in with SSH and choose option 16 "Restart PHP-FPM" - that's what I did when the GUI was stuck after accessing the package manager.
-
G gacpac referenced this topic on
-
Mmm, I didn't try that but that should work because php gets stuck on the uninstall script.
It wouldn't complete the uninstall of the bad package but that may not matter since all the important stuff has already happened by that point.
-
@DBMandrake i tried that and nothing. i happen to be able to restore from backup right before installing pfblocker update, I assume it's because the config has nothing to do with the package itself.
Over cli how do i guess downgrade pfblocker or something between those lines?
-
-
G Gertjan referenced this topic on
-
@Gertjan is removing it the only way, I can't just disable it?
-
You could probably remove the pfBlocker widget from the dashboard.
But killing the script from the CLI when you remove it is not too hard. See: https://forum.netgate.com/post/1185688
-
@stephenw10 Thanks, i was able to install the regular package and it deinstalled the devel version, lucky it didn't get stuck in the process because i couldn't find the install script to kill the pid.
pkg-static install pfSense-pkg-pfBlockerNG
-
@stephenw10 Thanks, killing the stuck remove process and installing the non-dev version got me back into the GUI. I had to restart unbound to restore service, but now things seem to be working as expected.
However, in Package Manager, the developer version is still listed, with a red exclamation mark. When I try to click the remove button it says “ERROR: Package pfSense-pkg-pfBlockerNG-devel is not installed”. Is there a way to force remove it from the package manager screen?
-
@gigabitwanted it is an annoying bug i have to say
-
You should be able to install again from the webgui. Then remove it if you want. Or just leave it, the _17 version should be good.
