Status

Infrastructure & Operations
WebOps: Community Platform
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: ryanc, Unassigned)

Tracking

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1358] )

(Reporter)

Description

3 years ago
Getting a 503 with this. Was brought to my attention around 2200 PST by :stephend.
:mythmon - is this a SUMO issue, or should Web Ops take a look?
Flags: needinfo?(mcooper)
I don't know of any SUMO problems that could be causing this. I don't see any requests in New Relic (which is normal for stage), and I don't see any errors in Sentry which I would normally see in case there are python errors. This sounds like an error in Apace, Zeus, modwsgi, something like that.
Flags: needinfo?(mcooper)
Assignee: nobody → server-ops-webops
Component: General → WebOps: Community Platform
Product: support.mozilla.org → Infrastructure & Operations
QA Contact: smani
Version: unspecified → other

Updated

3 years ago
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1358]

Comment 3

3 years ago
support.allizom.org should be back up and working.

It looks like the wsgi process died at some point.[1]   I've done a graceful restart of Apache; if this problem crops up again, we should do more digging about in the logs.


[1] [Tue Jun 23 17:03:48 2015] [error] [client 208.181.190.99] (11)Resource temporarily unavailable: mod_wsgi (pid=11613): Unable to connect to WSGI daemon process 'kitsune-ssl' on '/var/run/wsgi.32377.15.1.sock'.
(In reply to C. Liang [:cyliang] from comment #3)
> support.allizom.org should be back up and working.
> 
> It looks like the wsgi process died at some point.[1]   I've done a graceful
> restart of Apache; if this problem crops up again, we should do more digging
> about in the logs.
> 
> 
> [1] [Tue Jun 23 17:03:48 2015] [error] [client 208.181.190.99] (11)Resource
> temporarily unavailable: mod_wsgi (pid=11613): Unable to connect to WSGI
> daemon process 'kitsune-ssl' on '/var/run/wsgi.32377.15.1.sock'.

Thanks; our automation (and therefore the site) seems to have been fine, ever since.

Marking as FIXED since you did a graceful Apache restart; :mythmon, if you want to do root-cause analysis, please feel free to reopen.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.