714173 - "There was a problem submitting your report" messages when trying to submit Mac crashes

Status: RESOLVED WORKSFORME

(Toolkit :: Crash Reporting, defect)

Description

[Marcia Knous [:marcia]]

Attachment: Screenshot of issue

Seen originally while running 10.0b2, but I have seen it on Aurora and nightly as well.

STR:
1. Download a fresh 10.0b2 build.
2. Install crashme extension
3. Crash with null pointer deref.
4. Receive the dialog in the attachment.

Anthony Hughes tried to reproduce and was not able to, but he is not in the MV office.

I have tried this on three Mac different machines, all with the same result. On the Windows 7 lab machine running 10.0b2 I was able to successfully submit a report.

Comment 1

[u279076]

I suspect this could be location specific as I cannot reproduce this problem on the Mozilla Vancouver network.

Comment 2

[Laura Thomson :laura]

Marcia: what happens when you ping the collectors?

Comment 3

[Marcia Knous [:marcia]]

If I go into about:crashes and click on the crash, I do get it on nightly.

(In reply to Laura Thomson :laura from comment #2)
> Marcia: what happens when you ping the collectors?

Comment 4

[Marcia Knous [:marcia]]

I am able to ping the host and get a response in MV, so Laura indicates that would mean it would not be a network issue.

Comment 5

[(not currently active) Ted Mielczarek]

Can you check "~/Library/Application Support/Firefox/Crash Reports/submit.log", and see what error message it gives you?

Comment 6

[Marcia Knous [:marcia]]

Here are the most recent error messages for my crashes yesterday and today:

[Thu Dec 29 13:25:26 2011] Crash report submission failed: The request timed out.
[Thu Dec 29 13:27:22 2011] Crash report submission failed: The request timed out.
[Thu Dec 29 13:30:12 2011] Crash report submitted successfully
[Thu Dec 29 13:31:53 2011] Crash report submission failed: The request timed out.
[Thu Dec 29 13:52:37 2011] Crash report submission failed: The request timed out.

Comment 7

[(not currently active) Ted Mielczarek]

This sounds like a network error to me, then.

Comment 8

[Robert Helmer [:rhelmer]]

I don't see anything interesting on the Socorro collector server logs. I suspect the MV network, the front-end to the Socorro servers (network, Zeus etc) or something in between.

Is this still an ongoing issue or was it limited to certain time periods yesterday? There have been a lot of network and Zeus problems in the PHX datacenter lately so might try correlating it to one of those periods if it's not ongoing.

Comment 9

[Marcia Knous [:marcia]]

For me, it was happening late in the day yesterday PST. So far today I have not seen an issue with reports not being submitted.

(In reply to Robert Helmer [:rhelmer] from comment #8)
> I don't see anything interesting on the Socorro collector server logs. I
> suspect the MV network, the front-end to the Socorro servers (network, Zeus
> etc) or something in between.
> 
> Is this still an ongoing issue or was it limited to certain time periods
> yesterday? There have been a lot of network and Zeus problems in the PHX
> datacenter lately so might try correlating it to one of those periods if
> it's not ongoing.

Comment 10

[u279076]

Any further issues here?

Comment 11

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

Per comment #9, I'm marking this bug as WORKSFORME.