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

    PHP error and log files

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 3 Posters 3.5k 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.
    • A Offline
      Anteater4341
      last edited by

      Hello,

      The hard disk I use for pfSense (dedicated 60GB, re-purposed Firebox M370) is filling up with logs. I haven't been able to associate the issue with either Snort or pfBlockerNG-devel. This is the most recent crash data:

      Crash report begins.  Anonymous machine information:
      
      amd64
      15.0-CURRENT
      FreeBSD 15.0-CURRENT #21 RELENG_2_8_1-n256095-47c932dcc0e9: Thu Aug 28 16:27:48 UTC 2025     root@pfsense-build-release-amd64-1.eng.atx.netgate.com:/var/jenkins/workspace/pfSense-CE-snapshots-2_8_1-main/obj/amd64/AupY3aTL/var/jenkins/workspace/pfSense-CE-
      
      Crash report details:
      
      PHP Errors:
      [21-Sep-2025 15:50:17 America/Edmonton] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 634694348 bytes) in /usr/local/www/diag_edit.php on line 61
      [21-Sep-2025 15:50:34 America/Edmonton] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 634694348 bytes) in /usr/local/www/diag_edit.php on line 61
      [21-Sep-2025 15:54:00 America/Edmonton] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 634694348 bytes) in /usr/local/www/diag_edit.php on line 61
      [21-Sep-2025 15:54:02 America/Edmonton] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 634694348 bytes) in /usr/local/www/diag_edit.php on line 61
      
      
      
      No FreeBSD crash data found.
      

      Any and all assistance is much appreciated. Thank you!

      dennypageD 1 Reply Last reply Reply Quote 0
      • dennypageD Offline
        dennypage @Anteater4341
        last edited by

        @Anteater4341 If you are using pfBlockerNG, you need to enable Python mode for DNS Resolver (Unbound) and pfBlockerNG.

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

          It looks like what actually triggered that 'crash' though was trying to open a 600MB file in Diag > Edit.

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