Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Cannot allocate memor after adding GEO IP

    Scheduled Pinned Locked Moved pfBlockerNG
    6 Posts 3 Posters 1.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      GPRV9dzPhG
      last edited by GPRV9dzPhG

      Hello. I installed pfsense today and register own maxmind license key
      After Add GEO IP block rule

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

      Sometimes change country name but same

      1.PNG

      This is my pfsense update tab. It was 400000 table-entries hard limit after installation
      So I increased to 600000 but same symtom.

      What can I trying?

      Thanks

      2.4.4-RELEASE-p3 (amd64) , pfBlockerNG=devel (2.2.5_28), Intel(R) Pentium(R) CPU G2020 @ 2.90GHz , 4GB RAM

      1 Reply Last reply Reply Quote 0
      • kiokomanK
        kiokoman LAYER 8
        last edited by kiokoman

        increase table limit again to 800000 or more, afaik when you update the rules, new one take place before purging the old rules, from 444598 to 600000 you have litle space to move

        ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
        Please do not use chat/PM to ask for help
        we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
        Don't forget to Upvote with the 👍 button for any post you find to be helpful.

        G 1 Reply Last reply Reply Quote 2
        • G
          GPRV9dzPhG @kiokoman
          last edited by

          @kiokoman said in Cannot allocate memor after adding GEO IP:

          Okay. I tried

          2.PNG

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

          But same symtom should I try increasing more?

          provelsP 1 Reply Last reply Reply Quote 0
          • kiokomanK
            kiokoman LAYER 8
            last edited by

            yeah, try to increase, you can always revert back if it's not that

            ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
            Please do not use chat/PM to ask for help
            we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
            Don't forget to Upvote with the 👍 button for any post you find to be helpful.

            1 Reply Last reply Reply Quote 1
            • provelsP
              provels @GPRV9dzPhG
              last edited by provels

              @GPRV9dzPhG I think you need at least double the table usage for the hard limit, because temporarily both new and old are held in memory. Mine was set at 2,000,000 out of the box.
              5afcc8da-46a3-4b4c-ab9c-c1e91ef27242-image.png

              Peder

              MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
              BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

              G 1 Reply Last reply Reply Quote 1
              • G
                GPRV9dzPhG @provels
                last edited by

                @provels @kiokoman
                I increased it 1600000. And It solved

                Thanks a lot!

                I wonder how this value calculated

                Thanks

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.