[mythtv-users] Recordings not working

Gary Buhrmaster gary.buhrmaster at gmail.com
Tue May 25 15:38:24 UTC 2021


On Tue, May 25, 2021 at 1:48 PM Bill Meek <keemllib at gmail.com> wrote:

> The fix is pretty simple, but it's in common code used for
> database access. It's currently repeated 3x and I decided
> to put it all in 1 place. Also added logging that can
> be turned on with general:debug to make it easier if/when this
> happens again. So far, on master, my test 20.04 test host
> and (unaffected) 18.04 production host are happy with it.

Have you considered adding in something like

    db.setConnectOptions("MYSQL_OPT_RECONNECT=1");

to ask Qt (well, the MySQL connector) to automatically
reconnect?

Something equivalent was done in the zoneminder
plugin at one point (if my memory is not totally
misremembering).

I am not sure it will work appropriately here (one
would hope that the oracle client library will do the
right thing here(*)), but it may help in at least some
other cases, and might even eliminate the need
for MythTV to attempt the reconnect itself.

> I don't have a host with MariaDB handy (and there are reports
> that it's affected) and no takers to test the fix there.

It is the oracle mysql client library where the change
was introduced, which is why it impacts all server
types (no matter your server type, unless you go out
of your way to install the mariadb client library, you
get the oracle mysql client library in ubuntu).

But certainly it would be nice for someone to
personally validate that, rather than just going on
the theory.





(*) I vaguely recall a different bug in the oracle
mysql client which broke auto reconnect, but
it was recognized as a bug and resolved.  It
is software, there will be bugs.


More information about the mythtv-users mailing list