[mythtv-users] Recordings not working

Jan Ceuleers jan.ceuleers at gmail.com
Sun May 23 17:13:21 UTC 2021


On 23/05/2021 18:16, Gary Buhrmaster wrote:
> Without any proof, I am suspicious of
> the recent ubuntu libmysqlclient21 upgrade
> in ubuntu (to the ...8.0.25 version) which
> would have been made available to
> users around ten days ago.

My understanding is that there have been reports from users who are
using MariaDB rather than MySQL. Is it plausible that the same bug might
have been introduced into both code bases at the same time?

Still, I see in the MySQL release notes for version 8.0.24 [1] that
changes have been made to how the server deals with connection timeouts
(i.e. cases where an open connection has not been used for a time
exceeding the wait_timeout system variable. I quote:

---begin quote---
Previously, if a client did not use the connection to the server within
the period specified by the wait_timeout system variable and the server
closed the connection, the client received no notification of the
reason. Typically, the client would see Lost connection to MySQL server
during query (CR_SERVER_LOST) or MySQL server has gone away
(CR_SERVER_GONE_ERROR).

In such cases, the server now writes the reason to the connection before
closing it, and client receives a more informative error message, The
client was disconnected by the server because of inactivity. See
wait_timeout and interactive_timeout for configuring this behavior.
(ER_CLIENT_INTERACTION_TIMEOUT).

The previous behavior still applies for client connections to older
servers and connections to the server by older clients.
---end quote---

[1]: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-24.html

> Someone impacted should probably try
> to downgrade to the previous version
> of libmysqlclient21 and see if the problem
> goes away.

Happy to do that, but it would be difficult to be certain that the
problem has gone away.



More information about the mythtv-users mailing list