Closed Bug 602197 Opened 14 years ago Closed 14 years ago

64-bit dumps make staging choke

Categories

(Socorro :: General, task)

Product:
Socorro
Component:
General
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: laura, Unassigned)

Details

As per bug 601114 and bug 571578, we have a new stackwalker in staging.

Ted submitted
0d143352-c3d7-42b1-b1c0-a7c022101006
to staging.  The webapp just sits on the pending page and requesting the rawdump gives a 500 error.

Can we check:
- if this dump posted successfully to HBase?
- if it got processed?

The underlying bug (571578) is a Firefox 4 blocker, so this is high priority.
This appeared to be a transient hbase issue.  I was experiencing a similar difficulty with unrelated crashes that I was submitting.  This problem has apparently cleared up as my crashes are now going through. 

Please try again.
there were two problems in staging: some transient hbase stuff and the staging collector on a virtual machine was having memory problems.  These are resolved and ted's crashes are being processed correctly.
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.