#34082: "mysql server has gone away" on 404, 403 or 401
-------------------------------------+-------------------------------------
Reporter: williamchevremont | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: invalid
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 Peter Tillema):
Hi! I'm not sure if this is still relevant for you, but my application got
this problem as well. The normal application running fine (with nginx and
gunicorn/uvicorn), but whenever I hit a non-existing page a 500 error was
thrown. I tried to restart the mysql service, but then I got even worse
problems. So I enabled heavy logging in mysql and then I found out I
missed quotes around `'init_command': 'SET sql_mode=STRICT_TRANS_TABLES'`
so it wasn't a string, but an invalid identifier. Fixing that problem
solved everything magically, and now the 404 pages properly throw a 404.
Maybe this helps?
--
Ticket URL: <https://code.djangoproject.com/ticket/34082#comment:3>
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/01070185745cc49c-b7521e31-48e2-4b1b-84db-9d5a0c81ea5a-000000%40eu-central-1.amazonses.com.
