Pfblocker 2.1 error (Cannot allocate memory) with builds after "Aug 1 19:39:40"
-
Same problem here. I do want to add that the error happens for those block lists defined in the Lists folder. For example, I set up a block list using Bluetack Level 1. Immediately afterwards, the error message popped up and internet access was cut off. pfBlocker works correctly with built-in lists that comes with pfBlocker.
-
Same problem:
[ There were error(s) loading the rules: /tmp/rules.debug:33: cannot define table pfBlockerEurope: Cannot allocate memory - The line in question reads [33]: table persist file /var/db/aliastables/pfBlockerEurope.txt]d2500, 4 gb ram, (System - Advanced - Firewall Maximum Table Entries = 999999999)
-
Having same problems to…........
-
Thank you to the people that has replied. At least I know I am not alone with this issue.
Does anybody know how we can open a bug report for this?
Thx.
-
Just reported this bug so hopefully it will get fixed soon :)
Thank you to the people that has replied. At least I know I am not alone with this issue.
Does anybody know how we can open a bug report for this?
Thx.
-
Ah awesome, glad it's not only me. Been struggling for 2 hours to try and tweak settings with no joy.
-
Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49 -
Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49Does the machine need a reboot after applying the patch? I applied it but can't reboot right now and am still getting the error.
-
Can you show the contents of that file?
Or does even that file exists at all? -
Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49Thanks! Works :)
-
This worked for me too. Thanks!
(Guessing this will be fixed in an upcoming build?)
Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49Thanks! Works :)
-
Today's build (Thu Aug 15 16:30:12 EDT 2013 ) seems to fix this.
My bug is still open so this is not "official" yet. I'll confirm when it gets acknowledged and marked as fixed/closed.
Thx.
This worked for me too. Thanks!
(Guessing this will be fixed in an upcoming build?)
Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49Thanks! Works :)
-
This issue was indeed fixed in yesterday's build.
Thanks so much to the pfSense team.
pfSense rocks!
Today's build (Thu Aug 15 16:30:12 EDT 2013 ) seems to fix this.
My bug is still open so this is not "official" yet. I'll confirm when it gets acknowledged and marked as fixed/closed.
Thx.
This worked for me too. Thanks!
(Guessing this will be fixed in an upcoming build?)
Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49Thanks! Works :)
-
I am confused.
If this was already fixed, why does it still happen in this build:
2.1-RELEASE (i386)
built on Wed Sep 11 18:16:50 EDT 2013 ?"[ There were error(s) loading the rules: /tmp/rules.debug:34: cannot define table pfBlockerEurope: Cannot allocate memory - The line in question reads [34]: table persist file /var/db/aliastables/pfBlockerEurope.txt]"
This issue was indeed fixed in yesterday's build.
Thanks so much to the pfSense team.
pfSense rocks!
Today's build (Thu Aug 15 16:30:12 EDT 2013 ) seems to fix this.
My bug is still open so this is not "official" yet. I'll confirm when it gets acknowledged and marked as fixed/closed.
Thx.
This worked for me too. Thanks!
(Guessing this will be fixed in an upcoming build?)
Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49Thanks! Works :)
-
Also, if I try to Patch using "System: Patches"
I get the following errors:
"Patch can NOT be applied cleanly (detail)
Patch can NOT be reverted cleanly (detail)"I am confused.
If this was already fixed, why does it still happen in this build:
2.1-RELEASE (i386)
built on Wed Sep 11 18:16:50 EDT 2013 ?"[ There were error(s) loading the rules: /tmp/rules.debug:34: cannot define table pfBlockerEurope: Cannot allocate memory - The line in question reads [34]: table persist file /var/db/aliastables/pfBlockerEurope.txt]"
This issue was indeed fixed in yesterday's build.
Thanks so much to the pfSense team.
pfSense rocks!
Today's build (Thu Aug 15 16:30:12 EDT 2013 ) seems to fix this.
My bug is still open so this is not "official" yet. I'll confirm when it gets acknowledged and marked as fixed/closed.
Thx.
This worked for me too. Thanks!
(Guessing this will be fixed in an upcoming build?)
Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49Thanks! Works :)
-
I am confused.
If this was already fixed, why does it still happen in this build:
2.1-RELEASE (i386)Disable pfblocker, increase the value and then enable it again.
-
Marcel,
Can you describe the value that you mentioned in your post?
Thanks !I am confused.
If this was already fixed, why does it still happen in this build:
2.1-RELEASE (i386)Disable pfblocker, increase the value and then enable it again.
-
It will depend on the size of your lists
you can use default 100000 or 300000 or 400000…..
-
It will depend on the size of your lists
you can use default 100000 or 300000 or 400000…..
Okay - Let me rephrase my question:
Where is this value?
-
Okay - Let me rephrase my question:
Where is this value?
It's on the first post of this thread System -> Advanced -> Firewall Maximum Table Entries
I already tried some very high values for the Firewall Maximum Table Entries with no success (System - Advanced - Firewall Maximum Table Entries = 999999999)
