<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jan 10, 2019 at 9:24 PM Kris J <<a href="mailto:kris.jensen.knj@gmail.com">kris.jensen.knj@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jan 10, 2019 at 7:02 PM Peter Bennett <<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
On 1/10/19 6:37 PM, Kris J wrote:<br>
><br>
><br>
> On Thu, Jan 10, 2019 at 5:18 PM Peter Bennett <<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a> <br>
> <mailto:<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a>>> wrote:<br>
><br>
><br>
><br>
> On 1/10/19 4:49 PM, Kris J wrote:<br>
>><br>
>><br>
>> On Thu, Jan 10, 2019 at 12:51 PM Kris J<br>
>> <<a href="mailto:kris.jensen.knj@gmail.com" target="_blank">kris.jensen.knj@gmail.com</a> <mailto:<a href="mailto:kris.jensen.knj@gmail.com" target="_blank">kris.jensen.knj@gmail.com</a>>> wrote:<br>
>><br>
>><br>
>><br>
>> On Thu, Jan 10, 2019 at 10:52 AM Kris J<br>
>> <<a href="mailto:kris.jensen.knj@gmail.com" target="_blank">kris.jensen.knj@gmail.com</a><br>
>> <mailto:<a href="mailto:kris.jensen.knj@gmail.com" target="_blank">kris.jensen.knj@gmail.com</a>>> wrote:<br>
>><br>
>><br>
>><br>
>> On Thu, Jan 10, 2019 at 10:48 AM Peter Bennett<br>
>> <<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a> <mailto:<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a>>> wrote:<br>
>><br>
>><br>
>><br>
>> On 1/10/19 10:41 AM, Kris J wrote:<br>
>>><br>
>>><br>
>>> On Thu, Jan 10, 2019 at 10:32 AM Peter Bennett<br>
>>> <<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a> <mailto:<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a>>><br>
>>> wrote:<br>
>>><br>
>>><br>
>>><br>
>>> On 1/10/19 10:21 AM, Kris J wrote:<br>
>>>><br>
>>>><br>
>>>> On Wed, Jan 9, 2019 at 6:43 PM Peter Bennett<br>
>>>> <<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a><br>
>>>> <mailto:<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a>>> wrote:<br>
>>>><br>
>>>><br>
>>>><br>
>>>> On 1/9/19 1:47 PM, Kris J wrote:<br>
>>>>><br>
>>>>> I can install either available 64bit<br>
>>>>> packages from<br>
>>>>> <a href="https://dl.bintray.com/bennettpeter/generic/" rel="noreferrer" target="_blank">https://dl.bintray.com/bennettpeter/generic/</a>.<br>
>>>>> The android fronted starts up with trying<br>
>>>>> to connect to backend, it seems slow to<br>
>>>>> find the backend (29.1+fixes) and<br>
>>>>> sometimes fails. However after several<br>
>>>>> try's it eventually connects. (using ETH)<br>
>>>>><br>
>>>>><br>
>>>>> I can move about the frontend. However<br>
>>>>> most end points in the menu lead to a<br>
>>>>> loading screen that seems to hang the<br>
>>>>> Nvshield, and requires a hard power off.<br>
>>>>><br>
>>>>><br>
>>>>> I've been reading the user list and wiki<br>
>>>>> for pointer. However it seems I'm the only<br>
>>>>> one with this type of trouble. I see no<br>
>>>>> other reports of this type so I must have<br>
>>>>> missed something somewhere.<br>
>>>>><br>
>>>>><br>
>>>>> Any pointers appreciated.<br>
>>>>><br>
>>>>> Many thanks.<br>
>>>>><br>
>>>>><br>
>>>><br>
>>>> I have not seen or heard of this behavior.<br>
>>>> I assume you got as far as the main menu so<br>
>>>> it must be successfully connecting to the<br>
>>>> database and the backend.<br>
>>>><br>
>>>> Have you gone into setup and set the audio<br>
>>>> and video profile (or maybe it hangs even<br>
>>>> before you can get there). If you have not<br>
>>>> set these up and you are attempting<br>
>>>> playback it will not work well.<br>
>>>><br>
>>>> If you still have a problem you can get a log.<br>
>>>><br>
>>>> If you have adb installed and debug mode<br>
>>>> activated, you can do this to get a log:<br>
>>>><br>
>>>> On your linux machine, with the ip address<br>
>>>> of the shield:<br>
>>>> adb connect [ip address]<br>
>>>> adb logcat mfe:D *:S |& tee android.log<br>
>>>><br>
>>>> Then try starting mythfrontend and<br>
>>>> navigating. If it is having errors you will<br>
>>>> see them on the screen and in the<br>
>>>> android.log file. This may give you an idea<br>
>>>> of what is wrong.<br>
>>>><br>
>>>> Peter<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Hi, Peter<br>
>>>><br>
>>>> I don't see anything in the log<br>
>>>> (<a href="https://pastebin.com/AuTgdVXk" rel="noreferrer" target="_blank">https://pastebin.com/AuTgdVXk</a>) that's a<br>
>>>> obvious, other then minor font errors.<br>
>>>><br>
>>>> The log stops when I navigate to<br>
>>>> "setup/general" Then the load screen pops up<br>
>>>> and the shield needed are power off.<br>
>>>><br>
>>>> Many Thank for your time.<br>
>>>><br>
>>>><br>
>>> The log looks normal. Which backend version are<br>
>>> you using? Perhaps there is a problem with that.<br>
>>> The android frontend will work with backend<br>
>>> version 29 or later. Older versions will likely<br>
>>> cause problems.<br>
>>><br>
>>> _______________________________________________<br>
>>><br>
>>> Backend package = mythtv-backend-master<br>
>>> 29.1+fixes.20181228.af5d819~ubuntu16.04.1<br>
>>><br>
>>> And<br>
>>><br>
>>> "m-user@MythServer:~/build$ mythbackend -v<br>
>>> 2019-01-10 10:35:20.003539 C mythbackend version: <br>
>>> [v29.1] <a href="http://www.mythtv.org" rel="noreferrer" target="_blank">www.mythtv.org</a> <<a href="http://www.mythtv.org" rel="noreferrer" target="_blank">http://www.mythtv.org</a>><br>
>>> 2019-01-10 10:35:20.003567 C Qt version: compile:<br>
>>> 5.5.1, runtime: 5.5.1"<br>
>>><br>
>>><br>
>>><br>
>>><br>
>> I have no idea what the problem is. You could try<br>
>> uninstalling and reinstalling, also try looking at a<br>
>> full log. That gives messages from all applications<br>
>> and android itself, there you can see things like<br>
>> missing libraries:<br>
>><br>
>> adb logcat |& tee tmp/android.log<br>
>><br>
>> Peter<br>
>> _______________________________________________<br>
>><br>
>><br>
>><br>
>> Ok thank for the logging tips.<br>
>><br>
>> I'll see if I can find anything meaningful to work off of.<br>
>><br>
>> Many Thanks again.<br>
>><br>
>><br>
>><br>
>><br>
>> So I noticed the backend log has some errors when the android<br>
>> frontend has the loading screen. :<br>
>><br>
>> Jan 10 16:10:07 MythServer mythbackend: mythbackend[1690]: I<br>
>> MythSocketThread(84) mainserver.cpp:7674 (connectionClosed)<br>
>> Playback sock(1b0a970) 'android-3a0785970c9ae7ba' disconnected<br>
>> Jan 10 16:10:07 MythServer mythbackend: mythbackend[1690]: I<br>
>> MythSocketThread(86) mainserver.cpp:7674 (connectionClosed)<br>
>> Monitor sock(1a69530) 'android-3a0785970c9ae7ba' disconnected<br>
>> Jan 10 16:10:07 MythServer mythbackend: mythbackend[1690]: E<br>
>> CoreContext mythdbcon.cpp:873 (prepare) Error preparing query:<br>
>> SELECT data FROM settings WHERE value = :KEY AND hostname = :HOSTNAME<br>
>> Jan 10 16:10:07 MythServer mythbackend: mythbackend[1690]: E<br>
>> CoreContext mythdbcon.cpp:875 (prepare) Driver error was<br>
>> [2/2013]:#012QMYSQL3: Unable to prepare statement#012Database<br>
>> error was:#012Lost connection to MySQL server during query<br>
>> Jan 10 16:10:07 MythServer mythbackend: mythbackend[1690]: I<br>
>> CoreContext mythdbcon.cpp:263 (Reconnect) MySQL reconnected<br>
>> successfully<br>
>><br>
>> I don't have problems connecting with my other frontends and<br>
>> kodi's frontend connect fine on the same shield.<br>
>><br>
>> Still trying however.<br>
>><br>
>><br>
>><br>
><br>
> That looks like the root cause of the problem. I seem to remember<br>
> something like this being the result of having conflicting<br>
> versions of database software on client and server. Do you have<br>
> very old mysql server software?<br>
><br>
><br>
><br>
><br>
> Hmm.. I seem to have old and new mysql packages installed on my myth <br>
> server. I did a package search for "mysql" and found:<br>
><br>
> libdbd-mysql-perl 4.033-1ubuntu0.1<br>
> libmysqlclient18 5.5.62-0ubuntu0.14.04.1<br>
> libmysqlclient20 5.7.24-0ubuntu0.16.04.1<br>
> libqt4-sql-mysql 4.8.7+dfsg-5ubuntu2<br>
> libqt5sql5-mysql 5.5.1+dfsg-16ubuntu7.5<br>
> mysql-client 5.7.24-0ubuntu0.16.04.1 K-O<br>
> mysql-client-5.7 5.7.24-0ubuntu0.16.04.1 K-O<br>
> mysql-client-core-5.7 5.7.24-0ubuntu0.16.04.1<br>
> mysql-common 5.7.24-0ubuntu0.16.04.1<br>
> mysql-server 5.7.24-0ubuntu0.16.04.1<br>
> mysql-server-5.7 5.7.24-0ubuntu0.16.04.1<br>
> mysql-server-core-5.7 5.7.24-0ubuntu0.16.04.1<br>
> php5-mysql 5.5.9+dfsg-1ubuntu4.26<br>
> php7.0-mysql 7.0.32-0ubuntu0.16.04.1<br>
> python-mysqldb 1.3.7-1build2<br>
><br>
> So it's the lingering 5.5 mysql packages the cause?<br>
><br>
> I'm sketchy when it comes to DB stuff. But I would think removing the <br>
> older packages listed below would be ok. Yes?<br>
> libmysqlclient18 5.5.62-0ubuntu0.14.04.1,<br>
> libqt4-sql-mysql 4.8.7+dfsg-5ubuntu2,<br>
> libqt5sql5-mysql 5.5.1+dfsg-16ubuntu7.5<br>
> php5-mysql 5.5.9+dfsg-1ubuntu4.26<br>
><br>
><br>
><br>
><br>
><br>
I don't think that will make a difference, 5.7 is the version shipping <br>
with ubuntu now. The only one important is mysql-server and you have 5.7 <br>
so that should be OK. The latest mysql is version 8. I am using mariadb <br>
which is at version 10. It seems ubuntu ships newer versions of mariadb <br>
than of mysql.<br>
<br>
Perhaps you have some network problem. Using ethernet try plugging it <br>
differently, into a different router if possible. Also try different cables.<br>
<br>
<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://lists.mythtv.org/mailman/listinfo/mythtv-users" rel="noreferrer" target="_blank">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" rel="noreferrer" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a><br>
MythTV Forums: <a href="https://forum.mythtv.org" rel="noreferrer" target="_blank">https://forum.mythtv.org</a></blockquote><div><br></div><div> I think you are correct about network issues. Looking though the mysql log's and they are filled with errors like such:</div><div><br></div><div><div>2019-01-08T18:12:32.196916Z 8808 [Note] Aborted connection 8808 to db: 'mythconverg' user: 'mythtv' host: 'localhost' (Unknown error)</div><div>2019-01-08T18:12:32.626207Z 8855 [Note] Aborted connection 8855 to db: 'mythconverg' user: 'mythtv' host: '192.168.0.15' (Got an error reading communication packets)</div><div>2019-01-08T18:12:33.792349Z 8858 [Note] Aborted connection 8858 to db: 'mythconverg' user: 'mythtv' host: '192.168.0.15' (Got an error reading communication packets)</div><div>2019-01-08T18:13:19.080825Z 8857 [Note] Aborted connection 8857 to db: 'mythconverg' user: 'mythtv' host: 'localhost' (Unknown error)</div><div>2019-01-08T18:15:59.133402Z 8910 [Note] Got an error reading communication packets</div></div><div><br></div><div>hmmm....I'll have to test things on the network. Or maybe remake the server, in preparation of 0.30 release. With mariadb. </div><div><br></div><div><br></div><div>Many thanks Peter</div></div></div></div></blockquote><div><br></div><div>I think I track it down to DB corruption.</div><div>Running ( mysql -umythtv -p mythconverg -e 'status;' ) on my server shows:</div><div><div>--------------</div><div>mysql Ver 14.14 Distrib 5.7.24, for Linux (x86_64) using EditLine wrapper</div><div><br></div><div>Connection id: 11854</div><div>Current database: mythconverg</div><div>Current user: mythtv@localhost</div><div>SSL: Not in use</div><div>Current pager: stdout</div><div>Using outfile: ''</div><div>Using delimiter: ;</div><div>Server version: 5.7.24-0ubuntu0.16.04.1 (Ubuntu)</div><div>Protocol version: 10</div><div>Connection: Localhost via UNIX socket</div><div>Server characterset: latin1</div><div>Db characterset: utf8</div><div>Client characterset: utf8</div><div>Conn. characterset: utf8</div><div>UNIX socket: /var/run/mysqld/mysqld.sock</div><div>Uptime: 4 hours 2 min 39 sec</div><div><br></div><div>Threads: 46 Questions: 2801872 Slow queries: 0 Opens: 4221 Flush tables: 1 Open tables: 128 Queries per second avg: 192.449</div><div>--------------</div></div><div><br></div><div>Searching for answers lead me to a old outdated wiki page that explains the problem and how to fix the DB. </div><div>(<a href="https://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding">https://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding</a>)</div><div><br></div><div>However I'm leery to apply the suggested fix as the page has been labeled outdated. </div><div><br></div><div>Is the "Fixing the database corruption" entry still a viable fix for Mythtv .29.1?</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div></div></div></div></div></div></div>