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

    Crash report after update

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    1 Posts 1 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.
    • B
      biggsy
      last edited by

      Every time I update to the latest snapshot for 2.1 a crash report is generated:

      Crash report begins.  Anonymous machine information:
      
      amd64
      8.3-RELEASE-p8
      FreeBSD 8.3-RELEASE-p8 #1: Wed May 29 17:31:57 EDT 2013     root@snapshots-8_3-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8
      
      Crash report details:
      
      PHP Errors:
      [30-May-2013 17:57:20 Australia/Sydney] HTTP error, got response: HTTP/1.0 503 Service Unavailable
      
      Filename: /var/crash/minfree
      2048
      

      Yes, that's it, one file of 5 bytes with 2048 and a line-feed  ???

      When I try to submit the report Squid blocks it:

      Invalid Request error was encountered while trying to process the request:
      
          POST /crash_reporter.php HTTP/1.1
          User-Agent: Mozilla/4.0 (compatible;)
          Host: crashreporter.pfsense.org
          Accept: */*
          Content-Length: 969
          Expect: 100-continue
          Content-Type: multipart/form-data; boundary=----------------------------898c2fd50f51
      
      Some possible problems are:
      
          Request is too large.
      
          Content-Length missing for POST or PUT requests.
      
          Illegal character in hostname; underscores are not allowed.
      
          HTTP/1.1 "Expect:" feature is being asked from an HTTP/1.0 software.
      
      Your cache administrator is admin@localhost.
      

      I uninstalled Squid from that VM and it makes no difference.

      Is the crash report submitted through the browser session and being blocked by Squid on the "production" pfSense?

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