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

    Crash Report

    Scheduled Pinned Locked Moved IDS/IPS
    2 Posts 2 Posters 279 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.
    • D
      deus.user
      last edited by

      I keep getting this crash report on my pfsense install
      I understand it's due to a memory size issue, but not sure were to change settings or delete the logs to fix the issue.
      Any help is appreciated.

      Crash report begins. Anonymous machine information:

      amd64
      14.0-CURRENT
      FreeBSD 14.0-CURRENT #1 RELENG_2_7_0-n255866-686c8d3c1f0: Wed Jun 28 04:21:19 UTC 2023 root@freebsd:/var/jenkins/workspace/pfSense-CE-snapshots-2_7_0-main/obj/amd64/LwYAddCr/var/jenkins/workspace/pfSense-CE-snapshots-2_7_0-main/sources/FreeBSD-src-REL

      Crash report details:

      PHP Errors:
      [22-Aug-2023 22:42:59 America/Denver] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 547481896 bytes) in /usr/local/www/suricata/suricata_logs_browser.php on line 50
      [22-Aug-2023 22:43:15 America/Denver] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 635066880 bytes) in /usr/local/www/suricata/suricata_logs_browser.php on line 54
      [22-Aug-2023 22:43:17 America/Denver] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 547481896 bytes) in /usr/local/www/suricata/suricata_logs_browser.php on line 50

      No FreeBSD crash data found.

      1 Reply Last reply Reply Quote 0
      • bmeeksB
        bmeeks
        last edited by

        Whatever log file you are trying to open and view has now grown too large. There is a finite system limit on RAM that is allocated to a PHP process. I believe that limit is current 512 MB.

        You will need to view that log using a tool outside of the Suricata GUI so that PHP is bypassed.

        You also need to verify that automatic log managment is enabled on the LOGS MGMT tab and that you have not configured any large log filesize limits.

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