PfBlockerNG v2.0 w/DNSBL
-
Got a crash report running on 2.3.2-RELEASE (i386) with pfBlockerNG 2.1.1_2 with only DNSBL setup according to advise #18 (https://forum.pfsense.org/index.php?topic=102470.15), btw having enabled Alexa with 1K set.
Thanks for any help/advise cheers Qinn
Crash report begins. Anonymous machine information:
i386
10.3-RELEASE-p5
FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 14:11:41 CDT 2016 root@ce23-i386-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense_wrap_vgaCrash report details:
PHP Errors:
[03-Aug-2016 05:06:13] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20 bytes) in /usr/local/www/pfblockerng/pfblockerng.php on line 728
[03-Aug-2016 05:06:13] PHP Stack trace:
[03-Aug-2016 05:06:13] PHP 1. {main}() /usr/local/www/pfblockerng/pfblockerng.php:0
[03-Aug-2016 05:06:13] PHP 2. pfblockerng_get_countries() /usr/local/www/pfblockerng/pfblockerng.php:105
[03-Aug-2016 05:06:13] PHP 3. explode() /usr/local/www/pfblockerng/pfblockerng.php:728Filename: /var/crash/minfree
2048I have an identical situation except the line "(tried to allocate 20 bytes)" reads 27 bytes. Also, the PHP Errors block repeats itself a few times.
I tried to reinstall pfBlockerNG through the package manager, it claimed to have reinstalled but it no longer shows under the Firewall menu of pfSense. I uninstalled and reinstalled in two steps, again using the package manager, same result. For now I removed the package. My hardware is based on 32 bit N270 and I have 1GB of RAM, tons of HD space.
Prior to upgrading pfSense to 2.3.2 everything worked flawlessly for over a month so I assume that it has something to do with pfSense upgrade. I don't recall when I got pfBlockerNG upgraded.
I hope mine is not an isolated case. -
Second, I followed your advise, here are the results, btw Memory size = 1Gb (1024) usage 18%, during the process below I noticed that Memory usage rose from 16% to 28% and dropped to 17% after the error occurred, as shown below. It seems the process eats RAM and somehow there is a max set for the process.
any advice is welcome,
cheers, Qinn
1GB might be too small since the last MaxMind database change. Can you put more RAM in the box?
I have 2.5GB on my pfsense and I got a crash report :o
This looks like a change at some point in the MaxMind db. So be patient until BBcan177 take a looks at this. -
@haleakalas:
I have an identical situation except the line "(tried to allocate 20 bytes)" reads 27 bytes. Also, the PHP Errors block repeats itself a few times.
I tried to reinstall pfBlockerNG through the package manager, it claimed to have reinstalled but it no longer shows under the Firewall menu of pfSense. I uninstalled and reinstalled in two steps, again using the package manager, same result. For now I removed the package. My hardware is based on 32 bit N270 and I have 1GB of RAM, tons of HD space.
Prior to upgrading pfSense to 2.3.2 everything worked flawlessly for over a month so I assume that it has something to do with pfSense upgrade. I don't recall when I got pfBlockerNG upgraded.
I hope mine is not an isolated case.Maybe it is too late, but did you get any errors while removing or installing pfBlockerNG?
-
Although today 1GB Memory isn't much, maybe the dev's (BBcan177) could be encouraged ;) to find a solution as the pfSense recommended requirements are (https://www.pfsense.org/hardware/) RAM - 1 GB. So I put in a extra 512MB (so now 1,5GB), but I am shit out of luck, again error. Should have guessed it, as even your 2,5GB wasn't enough.
-
Hmmm, I have searched the forum and this error has occurred many times, and never the solution was to increase memory:
https://forum.pfsense.org/index.php?topic=87994.0
https://forum.pfsense.org/index.php?topic=113483.0
https://forum.pfsense.org/index.php?topic=102904.0
https://forum.pfsense.org/index.php?topic=76981.0
-
I get these messages Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 36 bytes)
from time to time with other function in pfsense, when viewing big file or with backup.
And I never found a solution for these.I disabled pfBlockerNG, DSNBL, surricata, reboot, close all pfsense tabs.
This gives me around 1.8GB of free memory, and the pfblockerng.php dc still crashes.Is there someone with more than 2.5GB of memory that doesn't have crash when updating the MaxMind GeoIP db ?
-
https://forum.pfsense.org/index.php?topic=116305.0
https://forum.pfsense.org/index.php?topic=116307.0
Problem seems to be spreading…
-
@oswoldy:
Hi,
I get the crash with 8GB of RAM :(I guess I won't bother installing any more than the 4GB that I currently have installed. I have disabled pfBlockerNG for the time being.
-
Same here with 4gb ram.
I tried to reinstall Pfblocker but no luck now it doesn't even show up anymore under Firewall menu item.
Before I reinstalled it hanged constantly on update the lists. -
Well during installation pfBlockerNG download the MaxMind GeoIP database … it probably crashes and the installation doesn't complete. :o
-
do you see stability if you reduce the number of lists you have active? My 16GB runs along fine at 40% utilisation with a fair few lists thrown at it and I recall from my casual observation it uses more whilst it processes them too.
-
@haleakalas:
I have an identical situation except the line "(tried to allocate 20 bytes)" reads 27 bytes. Also, the PHP Errors block repeats itself a few times.
I tried to reinstall pfBlockerNG through the package manager, it claimed to have reinstalled but it no longer shows under the Firewall menu of pfSense. I uninstalled and reinstalled in two steps, again using the package manager, same result. For now I removed the package. My hardware is based on 32 bit N270 and I have 1GB of RAM, tons of HD space.
Prior to upgrading pfSense to 2.3.2 everything worked flawlessly for over a month so I assume that it has something to do with pfSense upgrade. I don't recall when I got pfBlockerNG upgraded.
I hope mine is not an isolated case.Maybe it is too late, but did you get any errors while removing or installing pfBlockerNG?
No, there was no error messages during the reinstall, removal or installation. But, the weird thing is that although pfSense said the installation (or the reinstallation) was a success, pfBlockerNG was nowhere to be found; in the menus nor in the service status, watchdog, etc. So, I assume that it didn't install properly. But the dashboard says that only 20% of the RAM is used, so I doubt that this is a memory issue. Plus, I have been using pfBlockerNG on this same hardware for some time, so unless the last version has changed something drastically 1GB has been fine.
Meanwhile, I restored a raw copy backup of my system prior to 2.3.2 upgrade. That works like a charm. It has pfBlockerNG 2.0.17 on pfSense 2.3.1-p5 (i386). PfBlocker definitely works as it blocks access to and from China, Russia, etc.
So, until the dust settles oldies are the best way to go for me. -
Here is always worked fine with my 4GB of ram but since the last update it started to give problems i disbaled PFblocker for now and wait maybe it get fixed if not then i gave to sadly uninstall uninstall.
-
Here is a fix for the MaxMind errors https://forum.pfsense.org/index.php?topic=116307.msg644910#msg644910
please use that thread for this issue -
Above tip of Ronpfs worked.
But after the last re-install of pfblocker it didn't reinstall correct. It doesn't show up in the menu and it gives a error at the end of the reinstall.pkg: POST-INSTALL script failed
Is there a way i can install a previous version of pfblocker?
-
@Gé:
Above tip of Ronpfs worked.
But after the last re-install of pfblocker it didn't reinstall correct. It doesn't show up in the menu and it gives a error at the end of the reinstall.pkg: POST-INSTALL script failed
Is there a way i can install a previous version of pfblocker?
I do not think you can revert to a previous version :(
And even with the previous version it would be the same as the change comes from MaxMind GeoIP change, not from pfblockerNG code.Can you try https://forum.pfsense.org/index.php?topic=115966.0
-
Thank you again Ronpfs.
I did what you suggested on that other thread it did not work. I increased to 750M but no joy :( -
Here is a fix for the MaxMind errors https://forum.pfsense.org/index.php?topic=116307.msg644910#msg644910
please use that thread for this issueSolving the problem by throwing more memory at it worries me a bit. I hate to sound old-school, but 1GB or RAM on a router/firewall is a lot of memory. Allocating upwards of 300MB for one particular function, if that is on exclusive basis, would worry me that the implementation of that function is less than optimal.
As for the installation issue, it is still there. I can no longer install the latest version of pfBlockerNG; although pfSense claims that it's installed it doesn't show anywhere in the menus.
-
@Gé:
Thank you again Ronpfs.
I did what you suggested on that other thread it did not work. I increased to 750M but no joy :(The patch was made for someone with pfBlockerNG installed. You could probably revert it.
I posted another similar patch for the case when pfBlockerNG isn't installed. -
@haleakalas:
Here is a fix for the MaxMind errors https://forum.pfsense.org/index.php?topic=116307.msg644910#msg644910
please use that thread for this issueSolving the problem by throwing more memory at it worries me a bit. I hate to sound old-school, but 1GB or RAM on a router/firewall is a lot of memory. Allocating upwards of 300MB for one particular function, if that is on exclusive basis, would worry me that the implementation of that function is less than optimal.
As for the installation issue, it is still there. I can no longer install the latest version of pfBlockerNG; although pfSense claims that it's installed it doesn't show anywhere in the menus.
We are just trying to get a fix until BBcan177 can find a proper fix when he comes back.
there is a thread for the installation failure https://forum.pfsense.org/index.php?topic=115966.0
pfBlockerNG with DNSBL requires load of memory as it handle 1M+ table. So 1GB is really not that much memory for this kind or usage.
