Closed
Bug 617957
Opened 14 years ago
Closed 14 years ago
support-stage 500 apache error and logs aren't working
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jsocol, Assigned: fox2mike)
Details
Attachments
(1 file, 1 obsolete file)
|
5.08 KB,
text/plain
|
Details |
support-stage is returning Apache-style 500 errors, which means something is wrong too far up/down for Django to send us email, and since yesterday, only celery logs are showing up on cm-vpn01 (that's probably a code issue so if you can help me figure out what's wrong I'll fix it :)
Anyway, we have a release today, and QA needs this server to work to verify bugs beforehand.
Updated•14 years ago
|
Assignee: server-ops → dmoore
Comment 1•14 years ago
|
||
See attached error log
Comment 2•14 years ago
|
||
settings_default exists and appears valid
[root@mrapp-stage04 support.mozilla.org]# cd /data/www/support-stage-new.mozilla.com/kitsune/vendor/src/django-mozilla-product-details/product_details/
[root@mrapp-stage04 product_details]# ls -al settings_defaults.py
-rw-r--r-- 1 root root 338 Sep 22 16:40 settings_defaults.py
Updated•14 years ago
|
Attachment #496509 -
Attachment description: suppo → support-stage error
| Reporter | ||
Comment 4•14 years ago
|
||
I've never seen product-details throw that error before. What happens if you try `python26 manage.py shell` from the kitsune directory?
Comment 5•14 years ago
|
||
No errors from the shell, bouncing over to fox2mike for special attention.
Assignee: dmoore → shyam
| Assignee | ||
Comment 6•14 years ago
|
||
Yeah, nothing from the shell.
[root@mrapp-stage04 kitsune]# python26 manage.py shell
Python 2.6.2 (r262:71600, Aug 26 2009, 21:59:15)
Type "copyright", "credits" or "license" for more information.
IPython 0.10 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help -> Python's own help system.
object? -> Details about 'object'. ?object also works, ?? prints more.
In [1]:
| Assignee | ||
Comment 7•14 years ago
|
||
Rechecking out the vendor lib fixed this.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•