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

    Fatal error: Allowed memory size exhausted

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 Posters 626 Views 3 Watching
    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.
    • P Offline
      peterlecki
      last edited by

      FULL ERROR IN BROWSER:

      Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 107962344 bytes) in /usr/local/www/classes/Form/Section.class.php on line 134 PHP ERROR: Type: 1, File: /usr/local/www/classes/Form/Section.class.php, Line: 134, Message: Allowed memory size of 536870912 bytes exhausted (tried to allocate 107962344 bytes)
      
      • First things first 536,870,912 bytes is bigger than the attempted allocation of 107,962,344

      • This happens when I attempt to edit an alias that got imported fine but cannot be edited now since it has thousands of lines of CIDR networks. Idea is to block traffic from countries with many nefarious actors.

      • I read somewhere such config can cause a hard crash so I have not implemented the aliases into rules, only created them. But if it crashes while trying to edit the name, I would be hesitant to make rules to process those aliases.

      • Referenced line 134 is <scope>user</scope> so I'm obviously looking at the line count wrong.

      KOMK 1 Reply Last reply Reply Quote 0
      • KOMK Offline
        KOM @peterlecki
        last edited by

        @peterlecki If you're using very large aliases then you may have to increase your Firewall Maximum Table Entries via System - Advanced - Firewall & NAT.

        1 Reply Last reply Reply Quote 0
        • stephenw10S Offline
          stephenw10 Netgate Administrator
          last edited by

          That is probably the global 512MB PHP memory limit you're hitting. Other things are already using it when you try to open the alias requiring an additional 100MB. The maximum table size value probably isn't going to help there.

          Basically if you're seeing that you're are probably using the wrong alias type. Aliases that large should be imported URL aliases. pfBlocker was designed to solve exactly this problem. I would be using that.

          Steve

          P 1 Reply Last reply Reply Quote 0
          • P Offline
            peterlecki @stephenw10
            last edited by

            Thanks, @stephenw10
            Maximum Table Entries made no difference, as you expected. I will try pfBlocker right now.

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