I'm still having this issue, and it definitely seems Channels related. When
the issue occurs, I can logout/login and do other things on the Django only
portion of the site. As soon as I try to make DB requests from within a
Channels consumer, the error pops up. Restarting the Daphne server resolves
the issue.
On Friday, November 1, 2019 at 9:13:41 AM UTC-4, BR wrote:
>
> I think I'm experiencing an issue related to:
>
> https://github.com/django/channels/issues/1234
>
> where I get (2006, 'MySQL server has gone away') after trying to establish
> a new channels connection with calls using database_sync_to_async(). I have
> set my Django DB CONN_MAX_AGE to 300 (5 minutes) and my MariaDB
> wait_timeout to 28800 (was 600 originally). All this did was extend the
> time before I saw the issue.
>
> Why would Django not be clearing out old connections, and why doesn't it
> just open a new one?
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/acd7afb1-0ee2-4259-8392-8f0a6cc9f34a%40googlegroups.com.
