If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[AMO]Preview is down(500s)

RESOLVED FIXED

Status

Infrastructure & Operations
WebOps: Other
--
critical
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: krupa, Assigned: fox2mike)

Tracking

Details

(URL)

(Reporter)

Description

7 years ago
https://preview.addons.mozilla.org/ is a 500.

HTTP/1.1 500 Internal Server Error

Date: Mon, 09 Aug 2010 23:26:29 GMT

Connection: close

Content-Type: text/html
This is blocking QA
Severity: normal → major
This is blocking Firefox testing as well.
Severity: major → critical
(Assignee)

Comment 3

7 years ago
Should be back online. Looks like the machine got overwhelmed by python (yay) and was automatically re-booted, 20 mins ago.

19:18:11 <@nagios> [30] pm-app-amo24:hplog is CRITICAL: CRITICAL 0001: ASR Detected by System ROM

ASR = Automatic System Recovery IIRC and occurs when the system isn't responding at all, which is why it was rebooted.
Assignee: server-ops → shyam
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Yikes.  Why didn't it start working after it rebooted?  Is there a missing init script?
(Assignee)

Comment 5

7 years ago
What didn't work after it rebooted? I didn't do anything to "make it work". The box rebooted when I said it did and when I checked preview.amo, it loaded and so I put in the explanation and closed out the bug :)

It started working after it rebooted by the looks of it.
Oh, I thought the system detected it was broken and automatically rebooted, I didn't know you did it.
(Assignee)

Comment 7

7 years ago
(In reply to comment #6)
> Oh, I thought the system detected it was broken and automatically rebooted, I
> didn't know you did it.

Okay, you're confused or I failed at explaining the whole thing :)

1) I saw this bug and wanted to check what was going on.
2) I saw the Nagios alert in comment #3 
3) I verified that pm-app-amo24 was back up and running (by logging in to the box)
4) I hit preview.amo and the page loaded fine
5) I put in comment #3 and closed out the bug.

I did nothing to get preview.amo back up and running. The box rebooted itself and it looks like preview came back with it.
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.