Cannot define table bogonsv6: Cannot allocate memory
-
Hello,
Since a few days, I have this error :
There were error(s) loading the rules: /tmp/rules.debug:23: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [23]: table <bogonsv6> persist file "/etc/bogonsv6"
There are 95952 lines in the file bogonsv6 :
- wc -l /etc/bogonsv6 95952 /etc/bogonsv6
pfSense version : 2.4.1-RELEASE
What should I do ?
Thanks for your help
Best Regards,
Fabien -
https://forum.pfsense.org/index.php?action=search
-
https://forum.pfsense.org/index.php?action=search
Wow, this is a useless reply. A search for this topic actually returns this thread, since OP put in so much detail to their question.
you could have pointed them
here https://forum.pfsense.org/index.php?topic=146036.0
or
here https://forum.pfsense.org/index.php?topic=145990.msg793804#msg793804but you wasted not just op's time, but mine and I'm sure other's as well (cause google is a thing, y'all) to post a snarky reply.
For the sake of those that actually come here for help, Please Go Away. Your above message contributes nothing to this thread.
-
For reference if you hit that issue go to System > Advanced > Firewall & NAT and set the field "Firewall Maximum Table Entries" to 400000.
Then go to Status > Filter Realod and make sure it loads cleanly without generating new alerts.
Steve
-
@stephenw10 said in Cannot define table bogonsv6: Cannot allocate memory:
400000
I followed your instructions and yet on the Filter Reload I now get only one alert error as follows:
Filter Reload
There were error(s) loading the rules: /tmp/rules.debug:31: cannot define table pfB_Europe_v4: Cannot allocate memory - The line in question reads [31]: table <pfB_Europe_v4> persist file "/var/db/aliastables/pfB_Europe_v4.txt" @ 2019-03-25 13:07:16
I tried the Status > Filter Reload several times and always get the pfb_Europe_v4 table.
Wonder is something is wrong with that particular table?
-
@fabienfs said in Cannot define table bogonsv6: Cannot allocate memory:
pfSense version : 2.4.1-RELEASE
What should I do ?Update would be the first freaking thing.. 2.4.4p2 is current
His point is if you would search for the exact subject of your post you would of found your problem asked and answered multiple times already.
-
@Web2Print
Did you try to increase to 600000 ...
and did you do a Force Reload All under pfblockerNG / Update tab? -
@johnpoz That was like a year ago.
@Web2Print Yeah you can increse that further to, say, 1M.
However that error is not due to table size or memory exhaustion. It's because the table defined by pfBlocker has not been populated. That would normally be updated automatically but you should force an update in pfBlocker to be sure.Steve