[mythtv-users] Trying Nvshield android package, unsuccessfully. Pointers needed.
mythtv at sky.com
Fri Jan 11 11:23:22 UTC 2019
On 11/01/2019 03:20, Kris J wrote:
> On Thu, Jan 10, 2019 at 9:24 PM Kris J <kris.jensen.knj at gmail.com
> <mailto:kris.jensen.knj at gmail.com>> wrote:
> I think I track it down to DB corruption.
> Running ( mysql -umythtv -p mythconverg -e 'status;' ) on my server shows:
> mysql Ver 14.14 Distrib 5.7.24, for Linux (x86_64) using EditLine
> Connection id: 11854
> Current database: mythconverg
> Current user: mythtv at localhost
> SSL: Not in use
> Current pager: stdout
> Using outfile: ''
> Using delimiter: ;
> Server version: 5.7.24-0ubuntu0.16.04.1 (Ubuntu)
> Protocol version: 10
> Connection: Localhost via UNIX socket
> Server characterset: latin1
> Db characterset: utf8
> Client characterset: utf8
> Conn. characterset: utf8
> UNIX socket: /var/run/mysqld/mysqld.sock
> Uptime: 4 hours 2 min 39 sec
> Threads: 46 Questions: 2801872 Slow queries: 0 Opens: 4221 Flush
> tables: 1 Open tables: 128 Queries per second avg: 192.449
> Searching for answers lead me to a old outdated wiki page that
> explains the problem and how to fix the DB.
> However I'm leery to apply the suggested fix as the page has been
> labeled outdated.
> Is the "Fixing the database corruption" entry still a viable fix for
> Mythtv .29.1?
That wiki page is referring to MythTV before 0.21 I don't think it's
relevant anymore. We store everything as utf8 in the DB now.
There is a script to repair and optimize the DB called
I that doesn't work I'd look at trying different network cables, router
etc like Peter suggested.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users