#34082: "mysql server has gone away" on 404, 403 or 401
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
williamchevremont |
Type: Bug | Status: new
Component: Database | Version: 4.1
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Hi,
I'm facing an issue I don't find any solution on the web, nor similar
problem.
When my application raise some 404, 403 or 401 error, sometime, this lead
to a "mysql server has gone away" error, randomly. There is no error on
the mysql logs. The application run in a docker container, mysql server on
one other. Even the "mysql_server_has_gone_away" connection engine didn't
patch correctly the stuff. I can't upgrade to newer django version,
because of some third party libraries that are not yet compatible.
--
Ticket URL: <https://code.djangoproject.com/ticket/34082>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070183c3966470-72103e3a-1774-48d6-85d6-a71fad34cb59-000000%40eu-central-1.amazonses.com.
