Closed Bug 677459 Opened 14 years ago Closed 14 years ago

"Fetching this archived report" fails due to timeout from today

Categories

(Socorro :: General, task)

Product:
Socorro
Component:
General
Platform:
x86
Windows 7
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: alice0775, Unassigned)

Details

Build Identifier: http://hg.mozilla.org/mozilla-central/rev/f414db34c70b Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0a1) Gecko/20110808 Firefox/8.0a1 ID:20110808030804 "Fetching this archived report" fails due to timeout since today. Reproducible: Always Steps to Reproduce: 1. Start browser 2. Open about:crashes 3. Click one of Report ID which is generated today Actual Results: timeout. Expected Results: Crash detail should appear.
Talkback is the previous crash reporting system, over to Socorro we go.
Assignee: jay → nobody
Component: Talkback Server & Webtool → Socorro
Product: mozilla.org → Webtools
QA Contact: talkback-server → socorro
We had some system issues today. Can you please give me the crash id from about:crashes?
Just now, it works again! bp-db2014ee-9b07-426e-a84c-ab2f82110808 bp-1a348b4c-7d15-4a40-bc44-024f12110808 Should I change status to WORKSFORME?
no, I still detect a problem with Socorro. some of your earlier UUIDs still won't come up. I suspect they are in a "stuck" state within the 'jobs' table. This is an artifact of the earlier systems issues. We'll need to purge them from the jobs table and then resubmit the processing requests.
Lars, is this the reason why crash rates for yesterday are artificially low (ADU numbers look fine, crash numbers not)?
spot checking, it appears that all the crashes mentioned in this bug have now been processed. In comment #3, two of the uuids are incomplete, I added an '8' to the end to make them work. If there are further difficulties, please file another bug.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.