Re: [Django] #26935: DB connections stuck in closed state when using Django ORM in daemon

[Django]

#26935: DB connections stuck in closed state when using Django ORM in daemon
-+-
 Reporter:  noky |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 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 timgraham):

 * status:  new => closed
 * resolution:   => duplicate


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.a1fb2376e2a060f1f7af7f6b541605dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26935: DB connections stuck in closed state when using Django ORM in daemon

[Django]

#26935: DB connections stuck in closed state when using Django ORM in daemon
-+-
 Reporter:  noky |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 As usual when this topic comes up, the patch throws transactional
 integrity to the wind, which isn't acceptable.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.11cee7d02d474e8d8c9365f33d378836%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26935: DB connections stuck in closed state when using Django ORM in daemon

[Django]

#26935: DB connections stuck in closed state when using Django ORM in daemon
-+-
 Reporter:  noky |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 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 timgraham):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I think this is a duplicate of #24810. Can you confirm?

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.45bd2c8f971355bf5844def955fcf766%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26935: DB connections stuck in closed state when using Django ORM in daemon

[Django]

#26935: DB connections stuck in closed state when using Django ORM in daemon
--+
 Reporter:  noky  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.9
 Severity:  Normal| Resolution:
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by noky):

 * Attachment "django-daemon-test.tgz" added.

 barebones django "daemon" project that reproduces problem

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.401f42abdf6804bdb28c9731c657b8f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26935: DB connections stuck in closed state when using Django ORM in daemon

[Django]

#26935: DB connections stuck in closed state when using Django ORM in daemon
--+
 Reporter:  noky  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 '''Situation:'''
 1. A long-running daemon process is using the Django ORM
 2. The underlying database gets restarted, causing existing db
 connection(s) to become invalid

 '''Problem:'''
 A subsequent db read using the ORM fail with the exception:
 {{{
   File "main.py", line 22, in 
 testread()
   File "main.py", line 14, in testread
 user = User.objects.all()[0]
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/models/query.py", line 297, in __getitem__
 return list(qs)[0]
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/models/query.py", line 258, in __iter__
 self._fetch_all()
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/models/query.py", line 1074, in _fetch_all
 self._result_cache = list(self.iterator())
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/models/query.py", line 52, in __iter__
 results = compiler.execute_sql()
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/models/sql/compiler.py", line 848, in execute_sql
 cursor.execute(sql, params)
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/utils.py", line 95, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
 OperationalError: terminating connection due to administrator command
 server closed the connection unexpectedly
 This probably means the server terminated abnormally
 before or while processing the request.
 }}}

 Further subsequent db reads using the ORM yield a different (yet
 consistent) exception:
 {{{
   File "main.py", line 22, in 
 testread()
   File "main.py", line 14, in testread
 user = User.objects.all()[0]
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/models/query.py", line 297, in __getitem__
 return list(qs)[0]
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/models/query.py", line 258, in __iter__
 self._fetch_all()
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/models/query.py", line 1074, in _fetch_all
 self._result_cache = list(self.iterator())
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/models/query.py", line 52, in __iter__
 results = compiler.execute_sql()
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/models/sql/compiler.py", line 846, in execute_sql
 cursor = self.connection.cursor()
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/backends/base/base.py", line 233, in cursor
 cursor = self.make_cursor(self._cursor())
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/backends/base/base.py", line 206, in _cursor
 return self.create_cursor()
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/utils.py", line 95, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/backends/base/base.py", line 206, in _cursor
 return self.create_cursor()
   File "/home/noky/Downloads/django-standalone/venv/local/lib/python2.7
 /site-packages/django/db/backends/postgresql/base.py", line 210, in
 create_cursor
 cursor = self.connection.cursor()
 InterfaceError: connection already closed
 }}}

 '''Environment:'''
 * Ubuntu 14.04
 * PostgreSQL 9.5
 * Django 1.9.8
 * psycopg2 2.6.2

 '''To reproduce problem:'''
 * Download attached project files and untar
 * Create a PostgreSQL database `testdb`
 * Edit `settings.py` to setup db settings
 * Run `setup.sh` to create virtualenv, in