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

mod_wsgi apps are down on mrapp-stage02

VERIFIED FIXED

Status

mozilla.org Graveyard
Server Operations
--
critical
VERIFIED FIXED
7 years ago
3 years ago

People

(Reporter: stephend, Assigned: fox2mike)

Tracking

Details

(URL)

(Reporter)

Description

7 years ago
http://input.stage.mozilla.com/ is face-palming, right now, along with http://m.input.stage.mozilla.com/, and by face-palming, I mean it's just a white screen returning 200 OK to my GET requests.
(Assignee)

Comment 1

7 years ago
Not a blocker, after business hours in MV.
Severity: blocker → major
(Assignee)

Comment 2

7 years ago
Jeff poked around and found the probable reason why, he'll update the bug and we'll toss it over to the input devs.
(Assignee)

Comment 3

7 years ago
So this is a slightly bigger issue. Aravind installed mod_python on mrapp-stage02 earlier today :

Sep 28 16:07:17 Installed: mod_python-3.2.8-3.1.i386

Which hosed mod_wsgi, apparently they can't co-exist :

http://www.g-loaded.eu/2010/04/07/mod_wsgi-incompatible-with-mod_python/

We (IT) will re-convene in the morning and figure out next steps and keep you guys posted. If I remove mod_python, the wsgi apps work fine.
Assignee: server-ops → shyam
Severity: major → critical
Summary: Input staging/mobile staging are down for the count → mod_wsgi apps are down on mrapp-stage02
(Assignee)

Comment 4

7 years ago
(In reply to comment #3)
> So this is a slightly bigger issue. Aravind installed mod_python on
> mrapp-stage02 earlier today :

Forgot to mention this was for crash-reports.
(Assignee)

Comment 5

7 years ago
Also, comment #2 is invalid, since this hasn't really got anything to do with the app itself. Jeff will probably talk to Dave about the issues he found with the app, though.
(Assignee)

Comment 6

7 years ago
So I tried upgrading to mod_python 3.3.1 and it still doesn't work. Seems like splitting stuff up is the way to go.

http://code.google.com/p/modwsgi/wiki/InstallationIssues#Incompatible_ModPython_Versions

I'm curious as to why crash-reports wants to use mod_python vs mod_wsgi?
Socorro (Crash Reporter) is in a stake of flux.  It has been rolled back from v 1.8 to v 1.7 in both stage and production.  1.7 requires mod_python; 1.8 requires mod_wsgi.  Once we rollout an intermediary version (1.7.4) to production, we'll be able to resume the 1.8 migration and move from mod_python to mod_wsgi on stage.

Comment 8

7 years ago
The ETA for that, by the way, is 2-3 weeks.
(Assignee)

Comment 9

7 years ago
(In reply to comment #3)

> We (IT) will re-convene in the morning and figure out next steps and keep you
> guys posted. If I remove mod_python, the wsgi apps work fine.

mod_python is gone from mrapp-stage02, but I'm seeing an ISE from input, probably a separate issue.

Aravind will be moving crash-reports stage elsewhere so mod_python and mod_wsgi don't clash.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Reporter)

Comment 10

7 years ago
(In reply to comment #9)
> (In reply to comment #3)
> 
> > We (IT) will re-convene in the morning and figure out next steps and keep you
> > guys posted. If I remove mod_python, the wsgi apps work fine.
> 
> mod_python is gone from mrapp-stage02, but I'm seeing an ISE from input,
> probably a separate issue.

I spun this off as bug 600667.
(Reporter)

Comment 11

7 years ago
Verified FIXED.
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.