Closed
Bug 1160144
Opened 9 years ago
Closed 9 years ago
Staging site is showing 'Service Unavailable' error
Categories
(support.mozilla.org :: General, defect)
support.mozilla.org
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: davehunt, Unassigned)
References
Details
(Whiteboard: [fromAutomation])
https://support.allizom.org/ is currently down for me, and is affecting Web QA's automated tests.
Reporter | ||
Comment 1•9 years ago
|
||
$ wget https://support.allizom.org/ --2015-04-30 14:47:35-- https://support.allizom.org/ Resolving support.allizom.org... 63.245.217.89 Connecting to support.allizom.org|63.245.217.89|:443... connected. HTTP request sent, awaiting response... 500 Internal Server Error 2015-04-30 14:48:06 ERROR 500: Internal Server Error.
Comment 2•9 years ago
|
||
According to chief, the current rev on -stage is: 130d08ab0930aeadb133918f35ffa17d0eb122dc I tried re-deploying that just now. Logs are here: http://supportadm.private.phx1.mozilla.com/chief/support.stage/logs/130d08ab0930aeadb133918f35ffa17d0eb122dc.1430405848 The deploy seems to have gone fine. Pretty sure that error page is coming from the ZLB and not Apache or Django. I think we're going to have to open up a bug with webops to figure out what's going on.
Depends on: 1160172
Comment 3•9 years ago
|
||
-stage seems to be working now. I'm going to mark this WORKSFORME even though it was definitely busted earlier. I don't think the other resolutions are much better given the problem seems to have just "gone away".
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•