Closed
Bug 693694
Opened 13 years ago
Closed 13 years ago
Affiliates: 500 errors on stage with banner link
Categories
(Firefox Affiliates Graveyard :: affiliates.mozilla.org, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
1.0
People
(Reporter: cmore, Unassigned)
Details
(Whiteboard: [it])
We are randomly getting 500 errors on banner links. Here are the times: Thread Name: Thread Group 1-7 Sample Start: 2011-10-11 10:59:57 PDT Load time: 11425 Latency: 11425 Size in bytes: 743 Headers size in bytes: 202 Body size in bytes: 541 Sample Count: 1 Error Count: 1 Response code: 500 Response message: Internal Server Error Thread Name: Thread Group 1-4 Sample Start: 2011-10-11 10:59:57 PDT Load time: 18684 Latency: 18684 Size in bytes: 743 Headers size in bytes: 202 Body size in bytes: 541 Sample Count: 1 Error Count: 1 Response code: 500 Response message: Internal Server Error Thread Name: Thread Group 1-9 Sample Start: 2011-10-11 10:59:57 PDT Load time: 18697 Latency: 18697 Size in bytes: 743 Headers size in bytes: 202 Body size in bytes: 541 Sample Count: 1 Error Count: 1 Response code: 500 Response message: Internal Server Error Thread Name: Thread Group 1-13 Sample Start: 2011-10-11 10:59:57 PDT Load time: 18636 Latency: 18636 Size in bytes: 743 Headers size in bytes: 202 Body size in bytes: 541 Sample Count: 1 Error Count: 1 Response code: 500 Response message: Internal Server Error Since these are on stage, we will need to have IT look at the apache log files.
Reporter | ||
Comment 1•13 years ago
|
||
These errors were random and when load testing on stage with 100 concurrent requests.
Reporter | ||
Updated•13 years ago
|
Severity: normal → major
Target Milestone: --- → 1.0
Reporter | ||
Comment 2•13 years ago
|
||
I'm having IT pull the log files for these times. I am also able to replicate it with additional load tests, but it is still random.
Whiteboard: [it]
Reporter | ||
Comment 3•13 years ago
|
||
Mkelly: I've looked over all of the apache error logs and there is only one error that stands out, but it looks to be just a warning. I don't think this would cause a 500 error: [Tue Oct 11 11:49:31 2011] [error] /usr/lib/python2.6/site-packages/jinja2/__init__.py:31: UserWarning: Module memcache was already imported from /data/www/affiliates.allizom.org/affiliates-app/vendor/lib/python/memcache.py, but /usr/lib/python2.6/site-packages is being added to sys.path [Tue Oct 11 11:49:31 2011] [error] __version__ = __import__('pkg_resources') \\
Reporter | ||
Comment 4•13 years ago
|
||
Here are some additional errors that I got from the error logs: [Wed Oct 12 10:50:07 2011] [error] [client 10.8.33.248] Premature end of script headers: playdoh.wsgi [Wed Oct 12 10:50:07 2011] [error] [client 10.8.33.248] Premature end of script headers: playdoh.wsgi [Wed Oct 12 10:50:07 2011] [error] [client 10.8.33.248] Premature end of script headers: playdoh.wsgi [Wed Oct 12 10:50:07 2011] [error] [client 10.8.33.248] Premature end of script headers: playdoh.wsgi [Wed Oct 12 10:50:07 2011] [error] [client 10.8.33.248] Premature end of script headers: playdoh.wsgi [Wed Oct 12 10:50:07 2011] [error] [client 10.8.33.248] Premature end of script headers: playdoh.wsgi [Wed Oct 12 10:50:07 2011] [error] [client 10.8.33.248] Premature end of script headers: playdoh.wsgi [Wed Oct 12 10:50:07 2011] [error] [client 10.8.33.248] Premature end of script headers: playdoh.wsgi [Wed Oct 12 10:50:07 2011] [error] [client 10.8.33.248] Premature end of script headers: playdoh.wsgi [Wed Oct 12 10:50:07 2011] [error] [client 10.8.33.248] Premature end of script headers: playdoh.wsgi
Reporter | ||
Comment 5•13 years ago
|
||
Here is some information on the premature end of script error: http://stackoverflow.com/questions/4501817/django-apache-mod-wsgi-error-premature-end-of-script-headers
Reporter | ||
Comment 6•13 years ago
|
||
This was due to just overloading dev/stage due to the limited amount of concurrent requests they can handle and sessions being dropped. Invalid
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Updated•12 years ago
|
Status: RESOLVED → VERIFIED
Assignee | ||
Updated•12 years ago
|
Product: Websites → Firefox Affiliates
Assignee | ||
Updated•9 years ago
|
Product: Firefox Affiliates → Firefox Affiliates Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•