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

    SG1100 Update 24.11 to 25.07.1 crash report/programming bug

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    3 Posts 2 Posters 19 Views 2 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.
    • M Offline
      Mission-Ghost
      last edited by Mission-Ghost

      After updating my SG1100 to pfSense+ 25.07.1 from 24.11, I now receive the banner on the dashboard "Netgate pfSense Plus has detected a crash report..." and the error posted is: "PHP Fatal Error - Allowed memory size of 134217728 bytes exhausted"

      This appears related to Ver 2.8.0 - PHP Fatal Error - Allowed memory size of 536870912 bytes exhausted

      There are two apparently related bugs:

      16217
      16223

      EXCEPT that my pfBlocker already uses Python mode and it only has two DNSBL groups: EasyList and ADs_Basic.

      So, although the redmine bugs tend to suggest that it doesn't really need fixing because it's not a big deal, it has taken a working 24.11 installation to a problematic 25.07.1 on my SG1100 and the offered work-around doesn't work in my case.

      I will try to jack up the memory in the System>Advanced menu and see how that goes.

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

        Yup increasing the PHP memory limit is the only other thing you can do there. But obviously the limited RAM in the 1100 may present an issue for that.

        1 Reply Last reply Reply Quote 0
        • M Offline
          Mission-Ghost @Mission-Ghost
          last edited by Mission-Ghost

          I changed System>Advanced>Miscellaneous>PHP Settings>Memory Limit from 128 to 256, rebooted and the banner is gone.

          Presumably this has resolved it. I have a second 1100 which I'll repeat the update and see if the error recurs. If so, I'll see if the above fix resolves it as well.

          Seems the update process, at least, should make this adjustment instead of leaving a mess requiring the customer to trouble-shoot.

          In the long run, as I've observe elsewhere before, the SG1100 seems to be under-resourced for pfSense's modern versions.

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