#21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout
passed
-------------------------------------+-------------------------------------
Reporter: ekeydar@… | Owner: err
Type: Bug | Status: assigned
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: mysql | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by anonymous):
Replying to [comment:22 aaugustin]:
> Unless I missed something, this only affects people that have management
commands running for more than 8 hours (or MySQL's connection timeout if
it has been changed from the default). Is that correct?
As far as I can tell I think this is correct. At least this is the place
where I was hitting this bug in my environment (before downgrading to 1.5
again because of this).
--
Ticket URL: <https://code.djangoproject.com/ticket/21597#comment:24>
Django <https://code.djangoproject.com/>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/075.4f801b5e70e8554f5b44b53dd504a171%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
