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

    Fatal error: Allowed memory size of 134217728 bytes exhausted

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 4 Posters 2.9k 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
      grk2
      last edited by

      Hello,

      I try to upload a config.xml file and I get this error

      Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 48961718 bytes) in /usr/local/www/diag_backup.php on line 290

      I'm under a 64bit system and I tried to increase the "memory_limit" value under /etc/inc/config.inc but it continues to show this error.

      How can I solve this issue ?

      Thank's in advance,

      1 Reply Last reply Reply Quote 0
      • N
        Nachtfalke
        last edited by

        This is probably not the solution but did you backup RRD data ?
        If yes - you can try to delete this data in your config.xml and then try a restore again.

        1 Reply Last reply Reply Quote 0
        • C
          cmb
          last edited by

          How big is that config file? Even with RRD data and a large, complex config, configs shouldn't be that big.

          1 Reply Last reply Reply Quote 0
          • G
            grk2
            last edited by

            Ok Pfsense Heroes,

            Maybe I'm wrong and you're gonna laugh at me …
            I have a big config.xml file, about 46MB.

            In fact I want to apply a guarateed bandwidth (or limitation) for each IP . My network is on 10.10.0.0/16

            So I generated my config.xml in order no enter by myslelf each rule.

            For example, each IP has it's own rule like that (and of course limitation depends on the IP)

            <rule><id><type>pass</type>
            <interface>opt1</interface>
            <tag><tagged><max><max-src-nodes><max-src-conn><max-src-states><statetimeout><statetype>keep state</statetype>
            <os><protocol>tcp/udp</protocol>
            <source>

            <address>10.10.0.2</address>

            <destination><any></any></destination>
            <descr><dnpipe>1</dnpipe>
            <pdnpipe>2</pdnpipe></descr></os></statetimeout></max-src-states></max-src-conn></max-src-nodes></max></tagged></tag></id></rule>

            Is there is a better way to do that ?

            Thank's in advance

            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

              Just make the limiters with a mask - one with source mask, one with destination mask. That makes the limits act per IP instead of as a group.
              Then direct the entire /16 through that same pair of limiters.

              If you didn't mask them, odds are what you did there isn't actually doing what you want anyhow. If they all use the same limiter pair and that limiter pair isn't masked, they're all sharing the same "bucket" of bandwidth.

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

              1 Reply Last reply Reply Quote 0
              • G
                grk2
                last edited by

                Thank's a lot :)

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