Constant error message with pfBlockerNG - cannot define table pfB_Top_v6
-
Run the following command to find the pid
ps aux | grep pfblockerng.php
Example output:
root 46898 7.0 0.9 234092 36632 - S 7:30PM 0:00.85 /usr/local/bin/php /usr/local/www/pfblockerng/pfblockerng.php cron
Then to kill the process:
kill -9 46898
This stops it yes however it happens again next time cron runs
also my original error is still happening
I've even tried removing pfblockerNG and reinstalling and this doesn't help either.
-
Hi,
Can anyone please suggest a fix for the following errorThere were error(s) loading the rules: /tmp/rules.debug:45: cannot define table pfB_Top_v6: Cannot allocate memory - The line in question reads [45]: table <pfB_Top_v6> persist file "/var/db/aliastables/pfB_Top_v6.txt" @ 2016-09-22 10:05:36
Regards
JamieDid you set the
pfSense / Advanced / Firewall-NAT / Firewall Maximum Table Entries
to 10000000 ?
-
It's set to 14000000 and I have also tried 10000000, error still happening every now and then.
Thanks for you help with this :-)Regards
Jamie -
What's the memory usage on the FW (Status / Monitoring : System Memory) ?
What's the pfsense version, pfblockerNG version, CPU type etc? -
Hi,
Running latest versions of everything.
Pfsense is running in a vm on a dell r710 server using xenserver 74 cores and 2 gig of ram, currently its using 47% of the ram.
Regards
Jamie -
Anyone ? this error is annoying and I assume causing pfBlockerNG to not function correctly
-
You don't have much memory, on my 2.5GB system, in the last 2 days, free memory is 17-35%.
Did you look at the pfblockerng.log ? system log?
Double the Firewall Maximum Table Entries until the rules loads. -
Increased Ram to 4gb, no difference error still occurs.
I can't see any error in the pfblockerng.logCheers
Jamie -
Increased Ram to 4gb, no difference error still occurs.
I can't see any error in the pfblockerng.logWhat does this command report?
wc -l /var/db/aliastables/*.txt | sort -n
Have you tried unchecking "Keep Settings", and Disabling/Enabling the package to see if that clears this issue? (Don't forget to re-enable "keep settings")…
Failing the above, you might also want to download/update the MaxMind database to see if that fixes your issue:
php /usr/local/www/pfblockerng/pfblockerng.php dc
-
php /usr/local/www/pfblockerng/pfblockerng.php dc
seems to have fixed the issue
thanks for your help