Closed
Bug 419482
Opened 18 years ago
Closed 18 years ago
Missing two Mac breakpad reports
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: marcia, Assigned: aravind)
Details
I have two reports that were submitted over the weekend, one legitimate crash and one test crash that still show a 404. Would like to see the stack of the legitimate one, which happened on the 23rd.
They are:
http://crash-stats.mozilla.com/report/index/f32025d9-e269-11dc-9945-001a4bd43ef6
http://crash-stats.mozilla.com/report/index/a683b011-e33d-11dc-8893-001a4bd43ef6
I am not sure where to file this, whether it should be under IT...
Updated•18 years ago
|
Assignee: nobody → server-ops
Component: Breakpad Integration → Server Operations
Product: Toolkit → mozilla.org
QA Contact: breakpad.integration → justin
Version: Trunk → other
| Assignee | ||
Updated•18 years ago
|
Assignee: server-ops → aravind
| Assignee | ||
Comment 1•18 years ago
|
||
morgamic: The processor seems to be stuck on a bad report.
createReport for 12ac5cb0-e217-11dc-a4dd-001a4bd43ed6
Caught Error (ignoring): exceptions.UnicodeEncodeError
'ascii' codec can't encode characters in position 10-15: ordinal not in range(128)
Moving that 12ac5cb0-e217-11dc-a4dd-001a4bd43ed6 report aside.
Comment 2•18 years ago
|
||
Thanks, Aravind. Can we drop that report+json somewhere to debug/write tests for? Have not seen this error on staging/dev before.
Comment 3•18 years ago
|
||
Is the crash-reporter beginning to recover? Any idea how backlogged it is?
| Assignee | ||
Comment 4•18 years ago
|
||
We have 19174 pending reports. I started a couple more processors, so it should catchup soon. And yes, I will add monitoring soon.
| Reporter | ||
Comment 5•18 years ago
|
||
Should I file a separate bug for the monitoring? I am concerned that this kind of backup could hurt us as we move closer toward the end game.
| Assignee | ||
Comment 6•18 years ago
|
||
(In reply to comment #5)
> Should I file a separate bug for the monitoring? I am concerned that this kind
> of backup could hurt us as we move closer toward the end game.
>
nah, I will not close this bug unless I add the monitoring for it.
| Assignee | ||
Comment 7•18 years ago
|
||
Marcia, both of those reports are now showing up.
| Assignee | ||
Comment 8•18 years ago
|
||
morgamic, did you want to add this monitor as a part of reporter (so I can query some sort of status page?) or did you want me to add a nagios check script?
Comment 9•18 years ago
|
||
Will hit this tomorrow. Let's plan a push tomorrow night to push the addition a monitor for date_processed.
| Assignee | ||
Comment 10•18 years ago
|
||
Done, we now have a monitor in place as well.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•