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

    Netgate SG 3100 Crash Report: PHP Errors

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    4 Posts 2 Posters 812 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.
    • T
      Tiger 0
      last edited by

      Hi Netgate Community,

      I've been receiving this crash report, can you help me understand what does the report means?

      What can I do to resolve this, thank you.

      [30-Nov-2021 08:37:39 Asia/Manila] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 50331656 bytes) in /usr/local/www/diag_command.php on line 174
      [30-Nov-2021 17:24:08 Asia/Manila] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 50331656 bytes) in /usr/local/www/diag_command.php on line 174

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

        It means a command was run in the webgui from Diag > Command Prompt that exhausted the allowed PHP memory.
        You should only run command there that have very limited output. For example it you run ping there you should always include a ping count with it so it returns after that. Otherwise it will just run continually in the background.

        Steve

        T 1 Reply Last reply Reply Quote 0
        • T
          Tiger 0 @stephenw10
          last edited by

          @stephenw10 I see, how can I delete what I run in command prompt that causes this error?

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

            If whatever you ran is still running you can kill the process manually at the command line.
            More likely though it just had a very large output that caused PHP to fall over and has now finished.

            Steve

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