[Django] #22410: Error(mail) on connection reset
Django
-------------------------------+--------------------
Reporter: allo@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
When deployed with gunicorn, django mails errors about connection resets
of the client:
error: [Errno 104] Connection reset by peer
As the mail comes from django ([django] in the subject) i guess django
should filter these errors.
--
Ticket URL: <https://code.djangoproject.com/ticket/22410>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: allo@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.6
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by allo@…):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Additional, there is no indication, at which site it happenend, only the
venv can be seen in the traceback.
--
Ticket URL: <https://code.djangoproject.com/ticket/22410#comment:1>
Django
Reporter: allo@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.6
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by timo):
It looks like your email sending is not configured correctly. It's not
clear to me what action you think we should take based on this report.
--
Ticket URL: <https://code.djangoproject.com/ticket/22410#comment:2>
Django
Reporter: allo@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.6
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by allo@…):
Not sure, because the traceback does not go into django, but into
socket.py from gunicorn, but django with the mail_admins on loglevel error
mails for "connection reset" and for csrf failures, which are both user
errors and no server problems.
(Sorry, no log at hand for the csrf stuff, but there seems to be a problem
on filtering the mails for code errors and other "normal" errors)
--
Ticket URL: <https://code.djangoproject.com/ticket/22410#comment:3>
Django
Reporter: allo@… | Owner: nobody
Type: Uncategorized | Status: closed
Component: Documentation | Version: 1.6
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timo):
* status: new => closed
* resolution: => needsinfo
--
Ticket URL: <https://code.djangoproject.com/ticket/22410#comment:4>