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

    Crash reports keeps crashing… (empty page)

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 2 Posters 1.2k 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.
    • E Offline
      EdwinNadorp
      last edited by

      After the upgrade there is an new item, 'pfSense has detected a crash report or programming bug. Click here for more information.'
      Haproxy was crashing …. again and again. Today i upgraded haproxy and hopefully is stops crashing.

      But when iam following the link 'here' to the http://pfsense/crash_reporter.php page. The page stays empty.

      How can i cleanup the crash reports?

      1 Reply Last reply Reply Quote 0
      • E Offline
        EdwinNadorp
        last edited by

        Today the page responded:

        Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 58251962 bytes) in /usr/local/www/crash_reporter.php on line 139 Call Stack: 0.0005 226872 1. {main}() /usr/local/www/crash_reporter.php:0 PHP ERROR: Type: 1, File: /usr/local/www/crash_reporter.php, Line: 139, Message: Allowed memory size of 268435456 bytes exhausted (tried to allocate 58251962 bytes)

        Looks like php needs more memory. But how?

        1 Reply Last reply Reply Quote 0
        • E Offline
          EdwinNadorp
          last edited by

          Never mind.

          The file /usr/local/www/crash_reporter.php  told  me it uses /tmp/PHP_errors.log

          wc -l /tmp/PHP_errors.log

          595818 /tmp/PHP_errors.log

          ls -lah /tmp/PHP_errors.log

          -rw-r–r--  1 root  wheel    63M May 11 17:16 /tmp/PHP_errors.log

          rm /tmp/PHP_errors.log

          problem solved. Now wait en see if haproxy is crashing again

          1 Reply Last reply Reply Quote 0
          • E Offline
            EdwinNadorp
            last edited by

            haproxy keeps crashing.

            after removing the haproxy package the folowing files remains on the host:

            /usr/local/pkg/haproxy.inc
            /usr/local/pkg/haproxy_htmllist.inc
            /usr/local/pkg/haproxy_socketinfo.inc
            /usr/local/pkg/haproxy_upgrade_config.inc
            /usr/local/pkg/haproxy_xmlrpcsyncclient.inc
            /usr/local/pkg/pkg_haproxy_tabs.inc

            removing those files en reinstallation of the package look like resolves this problem (just one crash happend after, complaining about the removed files)

            now we wait ….

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

              Looks like haproxy racked up a huge PHP error log (likely over a long period of time), which is why the crash report was crashing, too big for it to parse within its memory limit.

              Looks like you got to the bottom of it, that should be fine now.

              1 Reply Last reply Reply Quote 0
              • E Offline
                EdwinNadorp
                last edited by

                Yes, i can confirm that it is working correcty now. No crashes overnight.

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