Closed Bug 480234 Opened 15 years ago Closed 15 years ago

Report fails to submit with "There was a problem submitting your report" message

Categories

(Socorro :: General, task)

x86
macOS
task
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: marcia, Unassigned)

Details

Seen while running Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2a1pre) Gecko/20090225 Minefield/3.2a1pre

STR:
1. Crash
2. Submit Breakpad report
3. Receive dialog with "There was a problem submitting your report" message at the bottom

about:crashes does not show the crash and there seems to be some things in my "pending" folder under crash reports.
Severity: normal → critical
I can see this too on OS X. We always fail to send the crash report. Looks like a blocker.
Severity: critical → blocker
After much thrashing about, it was determined that the machine storing crash dumps had run out of i-nodes even while it reported 178G of free space. Cleanup ensued.  Socorro is now running again.

Crashes submitted during the outage, unfortunately have been lost.  They were never successfully written to disk and are therefore irretrievable.  Unless, of course, there is a way to resubmit them that no one has ever told me about.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Thanks Lars. It works fine now.

Shouldn't we have some scripts which check for free disk space and free i-nodes
and send reports to nagios? We really should catch such problems earlier.
Loosing crash reports is bad. Is there anything planned or shall I file a new bug?
Status: RESOLVED → VERIFIED
There are already such nagios alarms either in place or planned.  That issue entirely in the realm of IT, we can only offer suggestions.  An alarm was raised when disk problems began, however the ramifications were not understood until well into the crisis response three hours later.
I've filed bug 480346 for enhancements of the current scripts.
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.