Closed
Bug 659711
Opened 13 years ago
Closed 13 years ago
Returning a 500 Internal Server Error for Firefox 3.5.13's correlation reports
Categories
(Socorro :: General, task, P1)
Socorro
General
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 650904
2.4
People
(Reporter: stephend, Assigned: rhelmer)
References
()
Details
Attachments
(1 file)
325.01 KB,
image/png
|
Details |
https://crash-stats-dev.allizom.org/topcrasher/byversion/Firefox/3.5.13/28/all returns a 500 error when doing AJAX calls for the correlation reports: [11:34:16.446] POST https://crash-stats-dev.allizom.org/correlation/bulk_ajax/cpu/Firefox/3.5.13/ [HTTP/1.1 500 Internal Server Error 33073ms] [11:34:16.450] POST https://crash-stats-dev.allizom.org/correlation/bulk_ajax/addon/Firefox/3.5.13/ [HTTP/1.1 500 Internal Server Error 33014ms] [11:34:16.454] POST https://crash-stats-dev.allizom.org/correlation/bulk_ajax/module/Firefox/3.5.13/ [HTTP/1.1 500 Internal Server Error 32958ms]
Assignee | ||
Comment 1•13 years ago
|
||
We don't appear to have correlation reports for 3.5.13: https://crash-analysis.mozilla.com/crash_analysis/20110525/ Stephen does this version work on any other environments (stage, prod)?
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to comment #1) > We don't appear to have correlation reports for 3.5.13: > > https://crash-analysis.mozilla.com/crash_analysis/20110525/ > > Stephen does this version work on any other environments (stage, prod)? Prod bombs too: https://crash-stats.mozilla.com/topcrasher/byversion/Firefox/3.5.13/7/all [12:25:11.106] POST https://crash-stats.mozilla.com/correlation/bulk_ajax/cpu/Firefox/3.5.13/ [undefined 30735ms] [12:25:11.135] POST https://crash-stats.mozilla.com/correlation/bulk_ajax/addon/Firefox/3.5.13/ [undefined 31732ms] [12:25:11.171] POST https://crash-stats.mozilla.com/correlation/bulk_ajax/module/Firefox/3.5.13/ [undefined 31678ms]
Reporter | ||
Comment 3•13 years ago
|
||
Do we have scripts that check that correlation reports for a given version have been ran? What about integrity, as much as that's possible?
Reporter | ||
Comment 4•13 years ago
|
||
For https://crash-stats.mozilla.com/topcrasher/byversion/Firefox/4.0 we're also returning 500s, on prod/dev, as an additional datapoint; I'll stop spamming now :-)
Assignee | ||
Comment 5•13 years ago
|
||
(In reply to comment #3) > Do we have scripts that check that correlation reports for a given version > have been ran? What about integrity, as much as that's possible? No it's all pretty separate from the core Socorro right now, although there are some bugs to make the integration better. I think the real bug(s) here is that we need to be handling missing correlations better. Do you think we could whittle these down to one bug? I think I could make some surgical improvements (returning 404 instead of 500, etc).
Assignee | ||
Comment 6•13 years ago
|
||
(In reply to comment #5) > Do you think we could whittle these down to one bug? After IRC discussion, let's leave bug 658034 separate. That one is about stopping the spinners if there's an error. The issue in this one is that a missing correlation file should be a case we handle and return a 404.
Assignee | ||
Updated•13 years ago
|
Priority: -- → P1
Assignee | ||
Comment 7•13 years ago
|
||
Looking at the response in Firebug I can see what's happening is the Zeus is timing the request out, which is where the HTTP 500 is coming from. What this code is intended to return in this case (and does on a smaller set of inputs) is: HTTP/1.1 200 OK ... [{"rank":1,"signature":"xul.dll@0x7a39d0","correlation":"ERROR: No reports generated on 20110527 for Firefox 3.5.13. Looked at http:\/\/people.mozilla.com\/crash_analysis\/20110527\/20110527_Firefox_3.5.13-core-counts.txt and http:\/\/people.mozilla.com\/crash_analysis\/20110527\/20110527_Firefox_3.5.13-core-counts.txt.gz"}]
Status: NEW → ASSIGNED
Comment 8•13 years ago
|
||
Status please Rob? If this isn't landed, it's going to have to wait.
Assignee | ||
Comment 9•13 years ago
|
||
(In reply to comment #8) > Status please Rob? If this isn't landed, it's going to have to wait. The problem is that the zeus is timing the request; the fix for bug 658034 treats the symptoms but you'll still see HTTP 500 in the error console (because that's what the zeus is sending back). The deeper issue we need to solve is that this request shouldn't be taking so long it's timing out, moving milestone and reducing severity to deal with that part of it (this is nothing new).
Severity: critical → normal
Target Milestone: 1.7.8 → 2.0
Assignee | ||
Updated•13 years ago
|
Target Milestone: 2.0 → 2.1
Updated•13 years ago
|
Target Milestone: 2.1 → 2.2
Reporter | ||
Comment 10•13 years ago
|
||
This is a moving target, it seems (comment 9 has it nailed, I think). Current timeoutes/500s are from loading https://crash-stats-dev.allizom.org/topcrasher/byversion/Firefox/3.6.3/28/all, and its correlation reports: [10:48:58.416] POST https://crash-stats-dev.allizom.org/correlation/bulk_ajax/cpu/Firefox/3.6.3/ [HTTP/1.1 500 Internal Server Error] [10:48:58.490] POST https://crash-stats-dev.allizom.org/correlation/bulk_ajax/addon/Firefox/3.6.3/ [HTTP/1.1 500 Internal Server Error] [10:48:58.538] POST https://crash-stats-dev.allizom.org/correlation/bulk_ajax/module/Firefox/3.6.3/ [HTTP/1.1 500 Internal Server Error]
Updated•13 years ago
|
Target Milestone: 2.2 → 2.3
Updated•13 years ago
|
Target Milestone: 2.3 → 2.4
Assignee | ||
Comment 11•13 years ago
|
||
I don't think there's a simple patch to fix this, we just need to redo the way correlation reports are done.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•13 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
You need to log in
before you can comment on or make changes to this bug.
Description
•