Project

General

Profile

Actions

Bug #12058

closed

pfBlockerNG / "Cannot allocate memory" from Geo blocking IP list

Added by Sean McBride almost 3 years ago. Updated over 2 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
pfBlockerNG
Target version:
-
Start date:
06/18/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

My pfsense emailed me an error yesterday:

```
Notifications in this message: 1 ================================

17:04:38 There were error(s) loading the rules: /tmp/rules.debug:30: cannot define table pfB_GeoIPBlockPublicIP7_v4: Cannot allocate memory - The line in question reads [30]: table <pfB_GeoIPBlockPublicIP7_v4> persist file "/var/db/aliastables/pfB_GeoIPBlockPublicIP7_v4.txt"
```

I use pfsense+ 21.05-RELEASE and pfBlockerNG-devel 3.0.0_16 (both newest currently).

The file pfB_GeoIPBlockPublicIP7_v4.txt is only 407536 bytes big, and attached here. It is a list of IPs, 25982 lines long.

My system has 8 Gib of RAM, and the dashboard shows only 24% usage.

That file just doesn't seem big enough to legitimately run out of memory...


Files

pfB_GeoIPBlockPublicIP7_v4.txt (398 KB) pfB_GeoIPBlockPublicIP7_v4.txt Sean McBride, 06/18/2021 11:20 AM
Actions #1

Updated by Sean McBride over 2 years ago

Just a note: this wasn't a one-off. I get this email (just about?) every time I change some firewall setting.

Actions #2

Updated by Viktor Gurov over 2 years ago

  • Status changed from New to Duplicate

Duplicate of #6814

Actions #3

Updated by Sean McBride over 2 years ago

Viktor, thanks for suggesting the duplicate. I'll see if the config change there also fixes my issue and report back here.

Actions #4

Updated by Sean McBride over 2 years ago

Indeed increasing that has eliminated the "Cannot allocate memory" messages.

Could the error message be improved to state not only the problem but also the solution?

Actions

Also available in: Atom PDF