Issue 15 in django-mailer: Postgres 8.3.3 and send_all: "unexpected EOF on client connection"

28 views
Skip to first unread message

codesite...@google.com

unread,
Dec 6, 2008, 12:12:20 PM12/6/08
to pinax-...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 15 by carl.j.meyer: Postgres 8.3.3 and send_all: "unexpected EOF
on client connection"
http://code.google.com/p/django-mailer/issues/detail?id=15

What steps will reproduce the problem?
1. Install django-mailer with Postgres 8.3.3 and django-1.0.x branch
2.
3.

What is the expected output? What do you see instead?

django-mailer seems to work as expected, however there is an unexpected
error in the PostgreSQL log files. Every time the send_all() function is
called, the error "unexpected EOF on client connection" appears in the
PostgreSQL logs. Since my crontab runs send_mail every minute, this bloats
the log pretty quickly. According to Postgres, this error message simply
means that the client died or dropped the connection.

What version of the product are you using? On what operating system?

django-mailer r42, Postgres 8.3.3, django-1.0.x branch r9526

Please provide any additional information below.

I'm turning up logging to see if I can figure out what's causing the
problem more specifically, I'll post back here whatever I find.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

codesite...@google.com

unread,
Dec 6, 2008, 12:52:27 PM12/6/08
to pinax-...@googlegroups.com

Comment #1 on issue 15 by carl.j.meyer: Postgres 8.3.3 and
send_all: "unexpected EOF on client connection"
http://code.google.com/p/django-mailer/issues/detail?id=15

Ok, this seems to be a more general problem; Postgres gives this error if
the
connection isn't closed properly, so any Django management command (or even
just
playing around in ./manage.py shell) will trigger it if it doesn't
explicitly call
django.db.connection.close() before exiting. (Django explicitly closes its
connection at the end of a normal request/response cycle). Normally not a
big deal,
but since send_mail is typically called so frequently, maybe it would be
worth adding
an explicit connection.close to help out Postgres users? I'm certainly
patching my
copy to do that; patch attached if anyone else wants it.

Attachments:
issue15.diff 564 bytes

codesite...@google.com

unread,
Feb 25, 2010, 10:38:54 AM2/25/10
to pinax-...@googlegroups.com

Comment #2 on issue 15 by dimit...@glezos.com: Postgres 8.3.3 and
send_all: "unexpected EOF on client connection"
http://code.google.com/p/django-mailer/issues/detail?id=15

This was also reported on Transifex as well (www.transifex.net).

Reply all
Reply to author
Forward
0 new messages