Closed
Bug 1071019
Opened 10 years ago
Closed 10 years ago
Symbol upload fails for telenor: internal server error
Categories
(Socorro :: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: benjamin, Assigned: dmaher)
References
Details
Moved from bug 1061482, Andreas Pehrson from Telenor says: === Benjamin, FYI I just got a 500 Internal Server Error when trying to upload symbols on https://crash-stats.mozilla.com/symbols/upload/web/ using the account in comment 13. Could you take a look? The following headers in the response look like they could be useful: Server:"Apache" X-Backend-Server:"socorro4.webapp.phx1.mozilla.com" X-Frame-Options:"DENY" === The account for upload is fxos-symbol-upload@comoyo.com. peterbe, are you the right person to investigate/fix?
Flags: needinfo?(peterbe)
Comment 1•10 years ago
|
||
It failed because of permission problems on the server. https://errormill.mozilla.org/webtools/socorro-prod/group/172759/ I'm going to email phrawzty too to make sure he understands the urgency of it.
Assignee: nobody → dmaher
Flags: needinfo?(peterbe)
Assignee | ||
Comment 2•10 years ago
|
||
Looks like the django symlink is busted for some reason. Investigating. ಠ_ಠ
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•10 years ago
|
||
On all the Prod webheads: * Moved content from webapp-django/media/symbols_upload to the mount. * Removed said errant directory. * Created symlink from webapp-django/media/symbols_upload to the mount. The error condition should be resolved; however, it's troubling that the symlink wasn't there in the first place. This will require further investigation.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 4•10 years ago
|
||
I just made another attempt at uploading the symbols. Still getting 500 internal server error. Daniel, could you have a quick look to see if it's the same issue or something new?
Status: RESOLVED → REOPENED
Flags: needinfo?(dmaher)
Resolution: FIXED → ---
Assignee | ||
Comment 5•10 years ago
|
||
Indeed it does appear to be exactly the same problem. Prod was pushed yesterday after I applied the manual fix in comment #3, which provides further evidence that the pushes themselves are the source of the problem. In any case, I will apply the manual fix again - please see bug 1071062 for further analysis.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Flags: needinfo?(dmaher)
Resolution: --- → FIXED
Comment 6•10 years ago
|
||
Prod was not pushed yesterday, to my knowledge.
Assignee | ||
Comment 7•10 years ago
|
||
From my IRC logs:
> Day changed to 22 Sep 2014
> 11:05:43 <@lonnen> objections to shipping some code?
> 11:06:58 < peterbe> none from me
??
Comment 8•10 years ago
|
||
I got pulled away to work on other things and it didn't happen. There was no push bug, email about new code, etc.
Assignee | ||
Comment 9•10 years ago
|
||
I see - well that may change things somewhat, and indeed, the symlink has been replaced by a directory. Again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•10 years ago
|
||
I also tried again earlier to no avail (another 500), hoping you had fixed it manually phrawzty. It was 5-6 hours ago. Any chance my uploads actually trigger this bug?
Assignee | ||
Comment 11•10 years ago
|
||
(In reply to Andreas Pehrson [:pehrsons] (Telenor) from comment #10) > I also tried again earlier to no avail (another 500), hoping you had fixed > it manually phrawzty. It was 5-6 hours ago. > > Any chance my uploads actually trigger this bug? Yes, the problem is recurring, and I'm literally investigating it right now. I don't know if your uploads are triggering the condition or not, though that's an interesting idea that I will explore further.
Comment 12•10 years ago
|
||
Had to put the investigation on hold for the night. Phrawzty narrowed it down to a cron job that is clobbering the symlinks every 5 minutes or so. Will come back to it tomorrow.
Assignee | ||
Comment 13•10 years ago
|
||
The root cause of this issue has been identified and addressed - see bug 1071062. Closing.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Comment 14•10 years ago
|
||
Managed to upload now. Thanks Daniel!
You need to log in
before you can comment on or make changes to this bug.
Description
•