Closed
Bug 1057827
Opened 11 years ago
Closed 11 years ago
Pulse - http string on pulse-app1.dmz.phx1.mozilla.com is CRITICAL: HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - string 'Pulse' not found on 'http://pulse.mozilla.org:80/ ' - 768 bytes in 0.003 second response time
Categories
(Webtools :: Pulse, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nagiosapi, Unassigned)
References
(
URL
)
Details
(Whiteboard: [id=nagios1.private.phx1.mozilla.com:365466])
Automated alert report from nagios1.private.phx1.mozilla.com:
Hostname: pulse-app1.dmz.phx1.mozilla.com
Service: Pulse - http string
State: CRITICAL
Output: HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - string 'Pulse' not found on 'http://pulse.mozilla.org:80/' - 768 bytes in 0.003 second response time
Runbook: http://m.allizom.org/Pulse+-+http+string
Comment 1•11 years ago
|
||
[Sun Aug 24 03:53:26 2014] [error] [client 10.8.75.19] File "/data/www/pulse/pulsewebsite/django.wsgi", line 8, in <module>
[Sun Aug 24 03:53:26 2014] [error] [client 10.8.75.19] import django.core.handlers.wsgi
[Sun Aug 24 03:53:26 2014] [error] [client 10.8.75.19] ImportError: No module named wsgi
[Sun Aug 24 03:54:52 2014] [error] [client 10.8.74.211] mod_wsgi (pid=13696): Target WSGI script '/data/www/pulse/pulsewebsite/django.wsgi' cannot be loaded as Python module.
[Sun Aug 24 03:54:52 2014] [error] [client 10.8.74.211] mod_wsgi (pid=13696): Exception occurred processing WSGI script '/data/www/pulse/pulsewebsite/django.wsgi'.
[Sun Aug 24 03:54:52 2014] [error] [client 10.8.74.211] Traceback (most recent call last):
[Sun Aug 24 03:54:52 2014] [error] [client 10.8.74.211] File "/data/www/pulse/pulsewebsite/django.wsgi", line 8, in <module>
[Sun Aug 24 03:54:52 2014] [error] [client 10.8.74.211] import django.core.handlers.wsgi
[Sun Aug 24 03:54:52 2014] [error] [client 10.8.74.211] ImportError: No module named wsgi
Updated•11 years ago
|
Component: Server Operations: MOC → Pulse
Product: mozilla.org → Webtools
QA Contact: dmoore
Updated•11 years ago
|
Severity: normal → critical
Comment 2•11 years ago
|
||
TL;DR: I *think* the application needs to be updated to be compatible with Django 1.6. Reverting the python-django package to an older version has restored the site to working. For now, I've "locked" the version of python-django in puppet.
This weekend, it looks like the version of python-django went from 1.3.1 to 1.6.6. When I tried to get to a shell to confirm paths, I got an error:
$ python manage.py shell
Traceback (most recent call last):
File "manage.py", line 2, in <module>
from django.core.management import execute_manager
ImportError: cannot import name execute_manager
According to http://stackoverflow.com/questions/20906305/import-error-cannot-import-name-execute-manager-in-windows-environment, execute_manager was deprecated in 1.4 and removed in 1.6
Comment 3•11 years ago
|
||
I believe this can be closed unless there's still a plan to make it work with an updated django.
Comment 4•11 years ago
|
||
[13:30:38] <nagios-phx1> Wed 13:30:38 PDT [1239] pulse-app1.dmz.phx1.mozilla.com:Pulse - http string is CRITICAL: HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - string Pulse not found on http://pulse.mozilla.org:80/ - 768 bytes in 0.003 second response time (http://m.mozilla.org/Pulse+-+http+string)
Comment 5•11 years ago
|
||
My bad -- this was caused by my switchover of the production pulse to pull from a central pulse admin server.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•