Pfblocker 2.1 error (Cannot allocate memory) with builds after "Aug 1 19:39:40"

pppfsense

Hi all, first ever post in the forums so I hope I am doing it right.

I have been using pfsense for over 2 years now and I love it (master and slave virtualized under ESXi 5.1).
I am using pfblocker 2.1 and have not had much trouble with it until last week when I started to get the error:

[ There were error(s) loading the rules: /tmp/rules.debug:41: cannot define table pfBlockerLevel2: Cannot allocate memory - The line in question reads [41]: table persist file /var/db/aliastables/pfBlockerLevel2.txt]

–------------------------------------------------------------------------
I already tried some very high values for the Firewall Maximum Table Entries with no success (System - Advanced - Firewall Maximum Table Entries = 999999999)
My previous value was 4000000 and it was working fine.

This happens with no changes made to the pfsense config: The error comes up if I update to any build after: Thu Aug 1 19:39:40 EDT 2013

I also went ahead and configured 2 GB Memory (instead of 1 GB that was working fine until last week), with no success either.

I also tried changing the PHP memory (/etc/inc/config.inc) from 256M to 512M, with no success either.

Can somebody pretty please help or give me some guidance?

Appreciated in advance.

bbqrooster

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.

turker

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)

Clear-Pixel

Having same problems to…........

pppfsense

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.

pppfsense

Just reported this bug so hopefully it will get fixed soon :)

@pppfsense:

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.

drzoidberg33

Ah awesome, glad it's not only me. Been struggling for 2 hours to try and tweak settings with no joy.

jimp

Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49

DigitalDeviant

@jimp:

Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49

Does the machine need a reboot after applying the patch? I applied it but can't reboot right now and am still getting the error.

eri--

Can you show the contents of that file?
Or does even that file exists at all?

drzoidberg33

@jimp:

Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49

Thanks! Works :)

pppfsense

This worked for me too. Thanks!

(Guessing this will be fixed in an upcoming build?)

@drzoidberg33:

@jimp:

Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49

Thanks! Works :)

pppfsense

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.

@pppfsense:

This worked for me too. Thanks!

(Guessing this will be fixed in an upcoming build?)

@drzoidberg33:

@jimp:

Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49

Thanks! Works :)

pppfsense

This issue was indeed fixed in yesterday's build.

Thanks so much to the pfSense team.

pfSense rocks!

@pppfsense:

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.

@pppfsense:

This worked for me too. Thanks!

(Guessing this will be fixed in an upcoming build?)

@drzoidberg33:

@jimp:

Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49

Thanks! Works :)

brasilnut

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]"

@pppfsense:

This issue was indeed fixed in yesterday's build.

Thanks so much to the pfSense team.

pfSense rocks!

@pppfsense:

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.

@pppfsense:

This worked for me too. Thanks!

(Guessing this will be fixed in an upcoming build?)

@drzoidberg33:

@jimp:

Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49

Thanks! Works :)

brasilnut

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)"

@brasilnut:

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]"

@pppfsense:

This issue was indeed fixed in yesterday's build.

Thanks so much to the pfSense team.

pfSense rocks!

@pppfsense:

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.

@pppfsense:

This worked for me too. Thanks!

(Guessing this will be fixed in an upcoming build?)

@drzoidberg33:

@jimp:

Try reverting this commit via the system patches package:
https://github.com/pfsense/pfsense/commit/71549fa70975d30cf2fdb0275da8744b40c8ee49

Thanks! Works :)

marcelloc

@brasilnut:

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.

brasilnut

Marcel,

Can you describe the value that you mentioned in your post?
Thanks !

@marcelloc:

@brasilnut:

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.

marcelloc

It will depend on the size of your lists

you can use default 100000 or 300000 or 400000…..

brasilnut

@marcelloc:

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?