Mailing List Archive

Can't connect to remote backend database (again)
Back in June I posted a problem where I couldn't connect any remote
frontends to my v13 backend running on Ubuntu 20.04. I fixed that with help
from everyone (thanks) which meant I could connect a mythfrontend running
on a Ubuntu PC.

However, I thought the fix would mean I could connect any number of remote
frontends, but Ihave a Chromecast with Google TV device with mythfrontend
installed on it and that won't connect. It finds the backend server and
populates the IP address, database name (mythconverg) and user (mythtv).
I'm 100% certain I've entered the correct password (which should be the
same as the password on the PC mythfrontend, correct?)

This is my list of users:
mysql> select host,user from mysql.user;
+-------------+------------------+
| host | user |
+-------------+------------------+
| % | mythtv |
| 192.168.0.% | mythtv |
| localhost | debian-sys-maint |
| localhost | mysql.infoschema |
| localhost | mysql.session |
| localhost | mysql.sys |
| localhost | root |
+-------------+------------------+

These are my grants:
mysql> show grants for "mythtv"@"192.168.0.%";
+-------------------------------------------------------------------+
| Grants for mythtv@192.168.0.% |
+-------------------------------------------------------------------+
| GRANT USAGE ON *.* TO `mythtv`@`192.168.0.%` |
| GRANT ALL PRIVILEGES ON `mythconverg`.* TO `mythtv`@`192.168.0.%` |
+-------------------------------------------------------------------+


Any idea why the PC's mythfrontend can connect, but the Chromecast
with Google TV can't? BTW I know there's connectivity because other Android
apps like Leanfront can connect. They use the APIs so, ironically, they're
a lot easier to get working than MythTV's inbuilt mythfrontend.

Regards,
Phill
Re: Can't connect to remote backend database (again) [ In reply to ]
On Mon, 5 Jul 2021 08:40:05 +1000, you wrote:

>Back in June I posted a problem where I couldn't connect any remote
>frontends to my v13 backend running on Ubuntu 20.04. I fixed that with help
>from everyone (thanks) which meant I could connect a mythfrontend running
>on a Ubuntu PC.
>
>However, I thought the fix would mean I could connect any number of remote
>frontends, but Ihave a Chromecast with Google TV device with mythfrontend
>installed on it and that won't connect. It finds the backend server and
>populates the IP address, database name (mythconverg) and user (mythtv).
>I'm 100% certain I've entered the correct password (which should be the
>same as the password on the PC mythfrontend, correct?)
>
>This is my list of users:
>mysql> select host,user from mysql.user;
>+-------------+------------------+
>| host | user |
>+-------------+------------------+
>| % | mythtv |
>| 192.168.0.% | mythtv |
>| localhost | debian-sys-maint |
>| localhost | mysql.infoschema |
>| localhost | mysql.session |
>| localhost | mysql.sys |
>| localhost | root |
>+-------------+------------------+
>
>These are my grants:
>mysql> show grants for "mythtv"@"192.168.0.%";
>+-------------------------------------------------------------------+
>| Grants for mythtv@192.168.0.% |
>+-------------------------------------------------------------------+
>| GRANT USAGE ON *.* TO `mythtv`@`192.168.0.%` |
>| GRANT ALL PRIVILEGES ON `mythconverg`.* TO `mythtv`@`192.168.0.%` |
>+-------------------------------------------------------------------+
>
>
>Any idea why the PC's mythfrontend can connect, but the Chromecast
>with Google TV can't? BTW I know there's connectivity because other Android
>apps like Leanfront can connect. They use the APIs so, ironically, they're
>a lot easier to get working than MythTV's inbuilt mythfrontend.
>
>Regards,
>Phill

You could try looking in the /var/log/mysql directory on the backend,
and seeing if there are any error messages that tell you what is
happening.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
On 2021-07-04 6:40 p.m., Phill Edwards wrote:
> Back in June I posted a problem where I couldn't connect any remote

> This is my list of users:
> mysql> select host,user from mysql.user;
> +-------------+------------------+
> | host        | user             |
> +-------------+------------------+
> | %           | mythtv           |
> | 192.168.0.% | mythtv           |
> | localhost   | debian-sys-maint |
> | localhost   | mysql.infoschema |
> | localhost   | mysql.session    |
> | localhost   | mysql.sys        |
> | localhost   | root             |
> +-------------+------------------+

Run that mysql query again, but use:

select host, user, password from mysql.user;

So you can check if the (hash of the) passwords are the same. I have
never seemed to have had any luck with using the '%' wildcard for
connections. So I specify each one by IP:

MariaDB [(none)]> select host,user,password from mysql.user where user =
"mythtv";
+-------------------+--------+-------------------------------------------+
| host | user | password |
+-------------------+--------+-------------------------------------------+
| localhost | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
| 192.168.1.99 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
| 192.168.1.96 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
| 192.168.1.95 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
| 192.168.1.86 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC

Those are the main desktop, the mythbox and the laptop (wired and
wireless) as set in /etc/hosts and on each computer.
Works for me.
Note: if you are using SchedulesDirect JSON you will have an 'sd' user too.

Geoff

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
>
> > Back in June I posted a problem where I couldn't connect any remote
>
> > This is my list of users:
> > mysql> select host,user from mysql.user;
> > +-------------+------------------+
> > | host | user |
> > +-------------+------------------+
> > | % | mythtv |
> > | 192.168.0.% | mythtv |
> > | localhost | debian-sys-maint |
> > | localhost | mysql.infoschema |
> > | localhost | mysql.session |
> > | localhost | mysql.sys |
> > | localhost | root |
> > +-------------+------------------+
>
> Run that mysql query again, but use:
>
> select host, user, password from mysql.user;
>
> So you can check if the (hash of the) passwords are the same. I have
> never seemed to have had any luck with using the '%' wildcard for
> connections. So I specify each one by IP:
>
> MariaDB [(none)]> select host,user,password from mysql.user where user =
> "mythtv";
> +-------------------+--------+-------------------------------------------+
> | host | user | password |
> +-------------------+--------+-------------------------------------------+
> | localhost | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
> | 192.168.1.99 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
> | 192.168.1.96 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
> | 192.168.1.95 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
> | 192.168.1.86 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
>
> Those are the main desktop, the mythbox and the laptop (wired and
> wireless) as set in /etc/hosts and on each computer.
> Works for me.
>


Hi, thanks for this tip. I've literally been trying to get this working on
and off for weeks, but no success. As a last resort I dropped the user and
re-created it and used a brand new password, but it still won't connect.

If it was a normal linux frontend I could SSH in and test connectivity etc.
But as this is a Chromecast With Google TV device I can't do that - can I?
Any ideas how to troubleshoot this? The problem could be network
connectivity (probably not as the Leanfront app works), or database grants
or incorrect password? Any suggestions on how I can troubleshoot this?

Also, I noticed the Chromecast With Google TV device has an IPv6 address as
well as IPv4. Could that be causing a problem?



BTW the column names are different on MySQL vs MariaDB, so the MySQL query
should be
mysql> select host, user, authentication_string from mysql.user;
Re: Can't connect to remote backend database (again) [ In reply to ]
On 2021-08-06 3:52 a.m., Phill Edwards wrote:
> > Back in June I posted a problem where I couldn't connect any remote
>
> > This is my list of users:
> > mysql> select host,user from mysql.user;
> > +-------------+------------------+
> > | host        | user             |
> > +-------------+------------------+
> > | %           | mythtv           |
> > | 192.168.0.% | mythtv           |
> > | localhost   | debian-sys-maint |
> > | localhost   | mysql.infoschema |
> > | localhost   | mysql.session    |
> > | localhost   | mysql.sys        |
> > | localhost   | root             |
> > +-------------+------------------+
>
> Run that mysql query again, but use:
>
> select host, user, password from mysql.user;
>
> So you can check if the (hash of the) passwords are the same. I have
> never seemed to have had any luck with using the '%' wildcard for
> connections. So I specify each one by IP:
>
> MariaDB [(none)]> select host,user,password from mysql.user where
> user =
> "mythtv";
> +-------------------+--------+-------------------------------------------+
> | host              | user   | password
>     |
> +-------------------+--------+-------------------------------------------+
> | localhost         | mythtv |
> *CC8F35F587CA5A556B4132C2407E556D92172FFC
> | 192.168.1.99      | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
> | 192.168.1.96      | mythtv |
> *CC8F35F587CA5A556B4132C2407E556D92172FFC
> | 192.168.1.95      | mythtv |
> *CC8F35F587CA5A556B4132C2407E556D92172FFC
> | 192.168.1.86      | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
>
> Those are the main desktop, the mythbox and the laptop (wired and
> wireless) as set in /etc/hosts and on each computer.
> Works for me.
>
>
>
> Hi, thanks for this tip. I've literally been trying to get this working
> on and off for weeks, but no success. As a last resort I dropped the
> user and re-created it and used a brand new password, but it still won't
> connect.
>
> If it was a normal linux frontend I could SSH in and test connectivity
> etc. But as this is a Chromecast With Google TV device I can't do that -
> can I? Any ideas how to troubleshoot this? The problem could be network
> connectivity (probably not as the Leanfront app works), or database
> grants or incorrect password? Any suggestions on how I can troubleshoot
> this?
>
> Also, I noticed the Chromecast With Google TV device has an IPv6 address
> as well as IPv4. Could that be causing a problem?
>
>
>
> BTW the column names are different on MySQL vs MariaDB, so the MySQL
> query should be
> mysql> select host, user, authentication_string from mysql.user;

Leaving aside the possible Chromecast issues, it sounds more like a
configuration problem on the *server*.

The server machine MUST HAVE:
bind-address= 0.0.0.0
and
#skip-networking in thr my.cnf config.(That is, the skip-networking line
must be commented OUT.)
If bind-address is set to 127.0.0.1 then mysql/mariadb will NOT listen
to anything external. Similarly with skip-networking which when active
does exactly that.

Since this is a Chromecast device which (surprising to me) seems not to
allow ssh, then I can only suggest that you beg, borrow, steal a laptop
and try ssh into the server from it. So long as your bbs laptop is on
the same network sub-net (192.168.1...etc.) you should be able to launch
a mysql client on it (presuming mysql is installed of course!).

And try the login commands which you grants have set up on the server.
If the laptop is set to a different IP address you will at least get an
error message, proving that there is communication between the mysql
client and the mysql server.

G.




_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
On Fri, 6 Aug 2021 17:52:52 +1000, you wrote:

>>
>> > Back in June I posted a problem where I couldn't connect any remote
>>
>> > This is my list of users:
>> > mysql> select host,user from mysql.user;
>> > +-------------+------------------+
>> > | host | user |
>> > +-------------+------------------+
>> > | % | mythtv |
>> > | 192.168.0.% | mythtv |
>> > | localhost | debian-sys-maint |
>> > | localhost | mysql.infoschema |
>> > | localhost | mysql.session |
>> > | localhost | mysql.sys |
>> > | localhost | root |
>> > +-------------+------------------+
>>
>> Run that mysql query again, but use:
>>
>> select host, user, password from mysql.user;
>>
>> So you can check if the (hash of the) passwords are the same. I have
>> never seemed to have had any luck with using the '%' wildcard for
>> connections. So I specify each one by IP:
>>
>> MariaDB [(none)]> select host,user,password from mysql.user where user =
>> "mythtv";
>> +-------------------+--------+-------------------------------------------+
>> | host | user | password |
>> +-------------------+--------+-------------------------------------------+
>> | localhost | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
>> | 192.168.1.99 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
>> | 192.168.1.96 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
>> | 192.168.1.95 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
>> | 192.168.1.86 | mythtv | *CC8F35F587CA5A556B4132C2407E556D92172FFC
>>
>> Those are the main desktop, the mythbox and the laptop (wired and
>> wireless) as set in /etc/hosts and on each computer.
>> Works for me.
>>
>
>
>Hi, thanks for this tip. I've literally been trying to get this working on
>and off for weeks, but no success. As a last resort I dropped the user and
>re-created it and used a brand new password, but it still won't connect.
>
>If it was a normal linux frontend I could SSH in and test connectivity etc.
>But as this is a Chromecast With Google TV device I can't do that - can I?
>Any ideas how to troubleshoot this? The problem could be network
>connectivity (probably not as the Leanfront app works), or database grants
>or incorrect password? Any suggestions on how I can troubleshoot this?
>
>Also, I noticed the Chromecast With Google TV device has an IPv6 address as
>well as IPv4. Could that be causing a problem?
>
>
>
>BTW the column names are different on MySQL vs MariaDB, so the MySQL query
>should be
>mysql> select host, user, authentication_string from mysql.user;

You can run Wireshark on the server and see the network traffic.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
>
> Leaving aside the possible Chromecast issues, it sounds more like a
> configuration problem on the *server*.
>
> The server machine MUST HAVE:
> bind-address= 0.0.0.0
> and
> #skip-networking in thr my.cnf config.(That is, the skip-networking line
> must be commented OUT.)
> If bind-address is set to 127.0.0.1 then mysql/mariadb will NOT listen
> to anything external. Similarly with skip-networking which when active
> does exactly that.
>
> Since this is a Chromecast device which (surprising to me) seems not to
> allow ssh, then I can only suggest that you beg, borrow, steal a laptop
> and try ssh into the server from it. So long as your bbs laptop is on
> the same network sub-net (192.168.1...etc.) you should be able to launch
> a mysql client on it (presuming mysql is installed of course!).
>
> And try the login commands which you grants have set up on the server.
> If the laptop is set to a different IP address you will at least get an
> error message, proving that there is communication between the mysql
> client and the mysql server.
>

Thank you for these suggestions. I've got lots of PCs and virtual machines
around the place so I can have a crack at this. I'm pretty sure it's not an
issue with the MythBackend server config, or the subnet because I have a
linux PC on the same subnet running MythFrontend which works fine. Inspired
by your suggestions I think I'll reconfigure a linux frontend to have the
same IP address as the Chromecast device and see if it can connect. That
should give me some pointers.
Re: Can't connect to remote backend database (again) [ In reply to ]
>
> Thank you for these suggestions. I've got lots of PCs and virtual machines
>> around the place so I can have a crack at this. I'm pretty sure it's not an
>> issue with the MythBackend server config, or the subnet because I have a
>> linux PC on the same subnet running MythFrontend which works fine. Inspired
>> by your suggestions I think I'll reconfigure a linux frontend to have the
>> same IP address as the Chromecast device and see if it can connect. That
>> should give me some pointers.
>
>
Well, this is getting "interesting" (i.e. even more frustrating!). I set a
linux frontend to have the IP address that the Chromecast With Google TV
was using (192.168.0.125). And I had already set a different password in
MySQL for mythtv@192.168.0.125. The linux frontend connects without any
problems. The Chromecast With Google TV can't connect. That makes no sense
to me.

So then I managed to install an SSHD app (SSHelper which has to be
sideloaded from https://arachnoid.com/android/SSHelper/) on the Chromecast
With Google TV.

Now, if I run this command on my PC the connection succeeds:
C:\Users\phill>telnet 192.168.0.120 3306


But if I SSH into the Chromecast With Google TV and run it, it fails as
follows:
$ telnet 192.168.0.120 3306
kHost '192.168.0.125' is blocked because of many connection errors; unblock
with 'mysqladmin flush-hosts'Connection closed by foreign host


I believe this indicates that MySQL on the MythBackend has permanently
blocked the Chromecast With Google TV due to previously failed connection
attempts. So I logged into MySQL as root and ran:
mysql> flush hosts;

I can now telnet 192.168.0.120 3306.

But it hasn't fixed the problem. MythFrontend on the Chromecast With Google
TV still can't connect. I've cleared the cache, cleared the data and
re-entered the username and password. I've created a new account called
mythtv2 and tried to connect with that, but that doesn't work either.

I noticed that even after clearing the MythFrontend app data on Chromecast
With Google TV, when I restart the app it still displays mythtv as the user
and an old password. This also happened after uninstalling and
re-installing the app. Where could it be getting this from, and could it
indicate a problem that may be behind all this?
Re: Can't connect to remote backend database (again) [ In reply to ]
On 07/08/2021 06:14, Phill Edwards wrote:
> Thank you for these suggestions. I've got lots of PCs and
> virtual machines around the place so I can have a crack at this.
> I'm pretty sure it's not an issue with the MythBackend server
> config, or the subnet because I have a linux PC on the same
> subnet running MythFrontend which works fine. Inspired by your
> suggestions I think I'll reconfigure a linux frontend to have
> the same IP address as the Chromecast device and see if it can
> connect. That should give me some pointers.
>
>
> Well, this is getting "interesting" (i.e. even more frustrating!). I set
> a linux frontend to have the IP address that the Chromecast With Google
> TV was using (192.168.0.125). And I had already set a different password
> in MySQL for mythtv@192.168.0.125 <mailto:mythtv@192.168.0.125>. The
> linux frontend connects without any problems. The Chromecast With Google
> TV can't connect. That makes no sense to me.
>
> So then I managed to install an SSHD app (SSHelper which has to be
> sideloaded from https://arachnoid.com/android/SSHelper/
> <https://arachnoid.com/android/SSHelper/>) on the Chromecast With Google
> TV.
>
> Now, if I run this command on my PC the connection succeeds:
> C:\Users\phill>telnet 192.168.0.120 3306
>
>
> But if I SSH into the Chromecast With Google TV and run it, it fails as
> follows:
> $ telnet 192.168.0.120 3306
> kHost '192.168.0.125' is blocked because of many connection errors;
> unblock with 'mysqladmin flush-hosts'Connection closed by foreign host
>
>
> I believe this indicates that MySQL on the MythBackend has permanently
> blocked the Chromecast With Google TV due to previously failed
> connection attempts. So I logged into MySQL as root and ran:
> mysql> flush hosts;
>
> I can now telnet 192.168.0.120 3306.
>
> But it hasn't fixed the problem. MythFrontend on the Chromecast With
> Google TV still can't connect. I've cleared the cache, cleared the data
> and re-entered the username and password. I've created a new
> account called mythtv2 and tried to connect with that, but that doesn't
> work either.
>
> I noticed that even after clearing the MythFrontend app data on
> Chromecast With Google TV, when I restart the app it still displays
> mythtv as the user and an old password. This also happened after
> uninstalling and re-installing the app. Where could it be getting thi
> from, and could it indicate a problem that may be behind all this?
>

Earlier this year I had similar mysterious and persistent attempts to
connect to the wrong backend. I was running master.

Somehow the UPnP section of ~/.mythtv/config.xml had acquired nested
Mythfrontend, DefaultBackend, USN entries. Resetting the host address
worked again after those lines had been commented out. ( <!-- --> )

John P

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
>
> Earlier this year I had similar mysterious and persistent atte mpts to
> connect to the wrong backend. I was running master.
>
> Somehow the UPnP section of ~/.mythtv/config.xml had acquired nested
> Mythfrontend, DefaultBackend, USN entries. Resetting the host address
> worked again after those lines had been commented out. ( <!-- --> )
>

Thanks, John. Do you mean the config.xml on the frontend or backend?

>
>
Re: Can't connect to remote backend database (again) [ In reply to ]
On 07/08/2021 23:09, Phill Edwards wrote:
> Earlier this year I had similar mysterious and persistent atte mpts to
> connect to the wrong backend.  I was running master.
>
> Somehow the UPnP section of ~/.mythtv/config.xml had acquired nested
> Mythfrontend, DefaultBackend, USN entries.  Resetting the host address
> worked again after those lines had been commented out. ( <!--   --> )
>
>
> Thanks, John. Do you mean the config.xml on the frontend or backend?
>

IIRC the failure was in connecting the frontend in one of two hopefully
independent FE/BE boxes, and I changed config.xml there. But if you
have several versions and none of them have these extra lines then this
isn't your problem. It wasn't clear to me how they got there.



_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
>
>
> > Earlier this year I had similar mysterious and persistent atte mpts
> to
> > connect to the wrong backend. I was running master.
> >
> > Somehow the UPnP section of ~/.mythtv/config.xml had acquired nested
> > Mythfrontend, DefaultBackend, USN entries. Resetting the host
> address
> > worked again after those lines had been commented out. ( <!-- --> )
>

I've been trying everything to get mythfrontend Android app to connect
from a Chromecast with Google TV but still no luck. So yesterday I factory
reset the Android TV and re-installed all the apps. Still no luck and
there's some weird stuff:

1. After doing a factory reset and re-installing mythfrontend, the
settings displayed a username and password without me putting them in yet.
How can that possibly happen if this is the first run after a factory
reset? There should be no historic settings, like a password, to be picked
up

2. I can telnet mbe4 3306 from an SSH app on Android TV and it seems
that a connection attempt is made. I also enabled MySQL general-log=1 so
I could see what happens when a connection attempt is made from
mythfrontend on Android TV, but nothing appears in the
/var/lib/mysql/MBE4.log for it so that's weird.

3. I created a new mythtv account (creatively named mythtv2) and granted
privileges to it but this can't connect either.

4. When the app is trying to connect it says "Waiting for database to
start". Is that normal given that this is an Android app so the database is
on a remote backend? Is it just a poorly worded message, or is it actually
looking for a database on the Android TV device (where it won't find one)?


So the way I read the situation is that connectivity appears to be OK but
it can't connect to the remote database. For some reason. Best known to
itself. I wonder if I've stuffed something up in the area of database users
and grants. Here's my user accounts from MySQL showing 2 accounts for
192.168.0.125 which is my Android TV device:
+---------------+------------------+------------------------------------------------------------------------+
| host | user | authentication_string
|
+---------------+------------------+------------------------------------------------------------------------+
| % | mythtv |
*E9333A4FFE29CF0081729D3EB885F8EABCD47CBA |
| 192.168.0.% | mythtv |
$A$005$Oj"_1AmjRHKwT#:qZeMYiDQ5wgXeZoLjQ4.fC2CcLwjBaj8jmz.lAYlpI8. |
| 192.168.0.125 | mythtv | $A$005$
R7DD?CM27zLrb!NK/KA7CtGy4tPU3ED7HrPYKuxpxUQroYfApmeksZfwh9 |
| 192.168.0.125 | mythtv2 |
$A$005$+_B0pk(9x+rre!*XHmcl/uazRoEn/rbsd6cAodYWCTK40TzRtuRwd9xdm9A |
| localhost | debian-sys-maint | $A$005$T
+ P\ 2{(+p`*I

7GEo9iwbghOjnQvXKm2gZ0VUY/nhHCi38.1baiu6po4 |
| localhost | mysql.infoschema |
$A$005$THISISACOMBINATIONOFINVALIDSALTANDPASSWORDTHATMUSTNEVERBRBEUSED |
| localhost | mysql.session |
$A$005$THISISACOMBINATIONOFINVALIDSALTANDPASSWORDTHATMUSTNEVERBRBEUSED |
| localhost | mysql.sys |
$A$005$THISISACOMBINATIONOFINVALIDSALTANDPASSWORDTHATMUSTNEVERBRBEUSED |
| localhost | root |
*58D540776DD45547773EC3D627954E383D1A9ABA |
+---------------+------------------+------------------------------------------------------------------------+

I'm out of ideas for how to make this work. I've been a mythtv user
since 2004 but this has me totally stumped. Any ideas would be very, very
welcome.
Re: Can't connect to remote backend database (again) [ In reply to ]
On Sun, 15 Aug 2021 15:19:08 +1000, you wrote:

>I've been trying everything to get mythfrontend Android app to connect
>from a Chromecast with Google TV but still no luck. So yesterday I factory
>reset the Android TV and re-installed all the apps. Still no luck and
>there's some weird stuff:
>
> 1. After doing a factory reset and re-installing mythfrontend, the
> settings displayed a username and password without me putting them in yet.
> How can that possibly happen if this is the first run after a factory
> reset? There should be no historic settings, like a password, to be picked
> up
>
> 2. I can telnet mbe4 3306 from an SSH app on Android TV and it seems
> that a connection attempt is made. I also enabled MySQL general-log=1 so
> I could see what happens when a connection attempt is made from
> mythfrontend on Android TV, but nothing appears in the
> /var/lib/mysql/MBE4.log for it so that's weird.
>
> 3. I created a new mythtv account (creatively named mythtv2) and granted
> privileges to it but this can't connect either.
>
> 4. When the app is trying to connect it says "Waiting for database to
> start". Is that normal given that this is an Android app so the database is
> on a remote backend? Is it just a poorly worded message, or is it actually
> looking for a database on the Android TV device (where it won't find one)?
>
>
>So the way I read the situation is that connectivity appears to be OK but
>it can't connect to the remote database. For some reason. Best known to
>itself. I wonder if I've stuffed something up in the area of database users
>and grants. Here's my user accounts from MySQL showing 2 accounts for
>192.168.0.125 which is my Android TV device:
>+---------------+------------------+------------------------------------------------------------------------+
>| host | user | authentication_string
> |
>+---------------+------------------+------------------------------------------------------------------------+
>| % | mythtv |
>*E9333A4FFE29CF0081729D3EB885F8EABCD47CBA |
>| 192.168.0.% | mythtv |
>$A$005$Oj"_1AmjRHKwT#:qZeMYiDQ5wgXeZoLjQ4.fC2CcLwjBaj8jmz.lAYlpI8. |
>| 192.168.0.125 | mythtv | $A$005$
>R7DD?CM27zLrb!NK/KA7CtGy4tPU3ED7HrPYKuxpxUQroYfApmeksZfwh9 |
>| 192.168.0.125 | mythtv2 |
>$A$005$+_B0pk(9x+rre!*XHmcl/uazRoEn/rbsd6cAodYWCTK40TzRtuRwd9xdm9A |
>| localhost | debian-sys-maint | $A$005$T
> + P\ 2{(+p`*I
>
>7GEo9iwbghOjnQvXKm2gZ0VUY/nhHCi38.1baiu6po4 |
>| localhost | mysql.infoschema |
>$A$005$THISISACOMBINATIONOFINVALIDSALTANDPASSWORDTHATMUSTNEVERBRBEUSED |
>| localhost | mysql.session |
>$A$005$THISISACOMBINATIONOFINVALIDSALTANDPASSWORDTHATMUSTNEVERBRBEUSED |
>| localhost | mysql.sys |
>$A$005$THISISACOMBINATIONOFINVALIDSALTANDPASSWORDTHATMUSTNEVERBRBEUSED |
>| localhost | root |
>*58D540776DD45547773EC3D627954E383D1A9ABA |
>+---------------+------------------+------------------------------------------------------------------------+
>
>I'm out of ideas for how to make this work. I've been a mythtv user
>since 2004 but this has me totally stumped. Any ideas would be very, very
>welcome.

Run Wireshark or tshark or tcpdump on the backend box and capture the
traffic from the Chromecast with Google TV and see if it is actually
ever trying to connect to the database. Just use a "host
192.168.0.125" capture filter to only see the traffic from the
Chromecast with Google TV.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
>
>
> Run Wireshark or tshark or tcpdump on the backend box and capture the
> traffic from the Chromecast with Google TV and see if it is actually
> ever trying to connect to the database. Just use a "host
> 192.168.0.125" capture filter to only see the traffic from the
> Chromecast with Google TV.
>

Hi Simon, thanks for your suggestion. I've captured the traffic with tshark
and I get this repeated a few times:

147 88.911855731 192.168.0.120 ? 192.168.0.125 MySQL 161 Server Greeting
proto=10 version=8.0.26-0ubuntu0.20.04.2
148 88.912727650 192.168.0.125 ? 192.168.0.120 TCP 66 39502 ? 3306 [ACK]
Seq=1 Ack=96 Win=87808 Len=0 TSval=131226266 TSecr=1186449381
149 88.915360803 192.168.0.125 ? 192.168.0.120 MySQL 232 Login Request
user=mythtv db=mythconverg
150 88.915367067 192.168.0.120 ? 192.168.0.125 TCP 66 3306 ? 39502 [ACK]
Seq=96 Ack=167 Win=65152 Len=0 TSval=1186449385 TSecr=131226267
151 88.915469028 192.168.0.120 ? 192.168.0.125 MySQL 114 Auth Switch
Request
152 88.917330547 192.168.0.125 ? 192.168.0.120 TCP 66 39502 ? 3306 [FIN,
ACK] Seq=167 Ack=144 Win=87808 Len=0 TSval=131226267 TSecr=1186449385
153 88.917457270 192.168.0.120 ? 192.168.0.125 MySQL 121 Response Error
1158
154 88.917470722 192.168.0.120 ? 192.168.0.125 TCP 66 3306 ? 39502 [FIN,
ACK] Seq=199 Ack=168 Win=65152 Len=0 TSval=1186449387 TSecr=131226267
155 88.918298535 192.168.0.125 ? 192.168.0.120 TCP 60 39502 ? 3306 [RST]
Seq=168 Win=0 Len=0
156 88.918774149 192.168.0.125 ? 192.168.0.120 TCP 60 39502 ? 3306 [RST]
Seq=168 Win=0 Len=0
157 89.996525845 34:0a:33:87:ad:00 ? Broadcast ARP 60 Who has
192.168.0.125? Tell 192.168.0.204
158 89.999819001 192.168.0.125 ? 192.168.0.120 TCP 74 39504 ? 3306 [SYN]
Seq=0 Win=65535 Len=0 MSS=1460 SACK_PERM=1 TSval=131226538 TSecr=0 WS=256
159 89.999861548 192.168.0.120 ? 192.168.0.125 TCP 74 3306 ? 39504 [SYN,
ACK] Seq=0 Ack=1 Win=65160 Len=0 MSS=1460 SACK_PERM=1 TSval=1186450469
TSecr=131226538 WS=128
160 90.000509424 192.168.0.125 ? 192.168.0.120 TCP 66 39504 ? 3306 [ACK]
Seq=1 Ack=1 Win=87808 Len=0 TSval=131226538 TSecr=1186450469

So at least I know the request is reaching the backend database. But what I
can't work out is why it's returning an error. From what I can find online
error 1158 means "Got an error reading communication packets". How would I
go about resolving this?
Re: Can't connect to remote backend database (again) [ In reply to ]
On Sat, 21 Aug 2021 16:27:17 +1000, you wrote:

>>
>>
>> Run Wireshark or tshark or tcpdump on the backend box and capture the
>> traffic from the Chromecast with Google TV and see if it is actually
>> ever trying to connect to the database. Just use a "host
>> 192.168.0.125" capture filter to only see the traffic from the
>> Chromecast with Google TV.
>>
>
>Hi Simon, thanks for your suggestion. I've captured the traffic with tshark
>and I get this repeated a few times:
>
> 147 88.911855731 192.168.0.120 ? 192.168.0.125 MySQL 161 Server Greeting
>proto=10 version=8.0.26-0ubuntu0.20.04.2
> 148 88.912727650 192.168.0.125 ? 192.168.0.120 TCP 66 39502 ? 3306 [ACK]
>Seq=1 Ack=96 Win=87808 Len=0 TSval=131226266 TSecr=1186449381
> 149 88.915360803 192.168.0.125 ? 192.168.0.120 MySQL 232 Login Request
>user=mythtv db=mythconverg
> 150 88.915367067 192.168.0.120 ? 192.168.0.125 TCP 66 3306 ? 39502 [ACK]
>Seq=96 Ack=167 Win=65152 Len=0 TSval=1186449385 TSecr=131226267
> 151 88.915469028 192.168.0.120 ? 192.168.0.125 MySQL 114 Auth Switch
>Request
> 152 88.917330547 192.168.0.125 ? 192.168.0.120 TCP 66 39502 ? 3306 [FIN,
>ACK] Seq=167 Ack=144 Win=87808 Len=0 TSval=131226267 TSecr=1186449385
> 153 88.917457270 192.168.0.120 ? 192.168.0.125 MySQL 121 Response Error
>1158
> 154 88.917470722 192.168.0.120 ? 192.168.0.125 TCP 66 3306 ? 39502 [FIN,
>ACK] Seq=199 Ack=168 Win=65152 Len=0 TSval=1186449387 TSecr=131226267
> 155 88.918298535 192.168.0.125 ? 192.168.0.120 TCP 60 39502 ? 3306 [RST]
>Seq=168 Win=0 Len=0
> 156 88.918774149 192.168.0.125 ? 192.168.0.120 TCP 60 39502 ? 3306 [RST]
>Seq=168 Win=0 Len=0
> 157 89.996525845 34:0a:33:87:ad:00 ? Broadcast ARP 60 Who has
>192.168.0.125? Tell 192.168.0.204
> 158 89.999819001 192.168.0.125 ? 192.168.0.120 TCP 74 39504 ? 3306 [SYN]
>Seq=0 Win=65535 Len=0 MSS=1460 SACK_PERM=1 TSval=131226538 TSecr=0 WS=256
> 159 89.999861548 192.168.0.120 ? 192.168.0.125 TCP 74 3306 ? 39504 [SYN,
>ACK] Seq=0 Ack=1 Win=65160 Len=0 MSS=1460 SACK_PERM=1 TSval=1186450469
>TSecr=131226538 WS=128
> 160 90.000509424 192.168.0.125 ? 192.168.0.120 TCP 66 39504 ? 3306 [ACK]
>Seq=1 Ack=1 Win=87808 Len=0 TSval=131226538 TSecr=1186450469
>
>So at least I know the request is reaching the backend database. But what I
>can't work out is why it's returning an error. From what I can find online
>error 1158 means "Got an error reading communication packets". How would I
>go about resolving this?

If the Chromecast with Google TV device was a normal Linux box, I
would be trying this command to see if it is possible to login to the
database:

mysql -h 192.168.0.120 -u mythtv mythconverg

Does it have a terminal session that you can use for that? Does it
have the mysql command installed? If not, then you could make sure
the CGTV device is powered off (so it is not using its IP address),
and then use a virtual machine and set it to use the CGTV's IP address
as a static IP address and see if the command works from there. The
VM would need to be set to use bridged networking so that it is
connected to the same subnet that your CGTV and MythTV backend boxes
are. And then capture the packets for a good login and compare them
to the bad login above.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
>
>
>
> If the Chromecast with Google TV device was a normal Linux box, I
> would be trying this command to see if it is possible to login to the
> database:
>
> mysql -h 192.168.0.120 -u mythtv mythconverg
>
> Does it have a terminal session that you can use for that? Does it
> have the mysql command installed? If not, then you could make sure
> the CGTV device is powered off (so it is not using its IP address),
> and then use a virtual machine and set it to use the CGTV's IP address
> as a static IP address and see if the command works from there. The
> VM would need to be set to use bridged networking so that it is
> connected to the same subnet that your CGTV and MythTV backend boxes
> are. And then capture the packets for a good login and compare them
> to the bad login above.
>

I have a VM with a different IP address which I've installed mysql-client
on just now. That connected immediately to the mythconverg database - even
though I didn't set up a specific user for its IP address.

So it looks like the backend can accept remote database connections. It
just doesn't want to accept one from my Chromecast with Google TV device.
Re: Can't connect to remote backend database (again) [ In reply to ]
On Mon, 23 Aug 2021 20:38:42 +1000, you wrote:

>>
>>
>>
>> If the Chromecast with Google TV device was a normal Linux box, I
>> would be trying this command to see if it is possible to login to the
>> database:
>>
>> mysql -h 192.168.0.120 -u mythtv mythconverg
>>
>> Does it have a terminal session that you can use for that? Does it
>> have the mysql command installed? If not, then you could make sure
>> the CGTV device is powered off (so it is not using its IP address),
>> and then use a virtual machine and set it to use the CGTV's IP address
>> as a static IP address and see if the command works from there. The
>> VM would need to be set to use bridged networking so that it is
>> connected to the same subnet that your CGTV and MythTV backend boxes
>> are. And then capture the packets for a good login and compare them
>> to the bad login above.
>>
>
>I have a VM with a different IP address which I've installed mysql-client
>on just now. That connected immediately to the mythconverg database - even
>though I didn't set up a specific user for its IP address.
>
>So it looks like the backend can accept remote database connections. It
>just doesn't want to accept one from my Chromecast with Google TV device.

I have just looked through the tshark packet trace is more detail, and
in combination with this page:

https://dev.mysql.com/doc/internals/en/connection-phase-packets.html

I think I know what is happening. It appears that the CGTV is
connecting using an out of date authorisation method. The MySQL
server responds to this with an AuthSwitchRequest packet telling the
CGTV to try a different authorisation method. The CGTV does not like
that and responds by disconnecting, which causes the server to log a
"Response Error 1158".

What that suggests is that the mythfrontend loaded on the CGTV was
compiled using an out of date version of the MySQL client library. It
is possible that the MySQL server may have an option to accept older
authorisation methods, and setting such an option might fix the
problem. But I think it would be better to use an up to date version
of mythfrontend.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
>
> What that suggests is that the mythfrontend loaded on the CGTV was
> compiled using an out of date version of the MySQL client library. It
> is possible that the MySQL server may have an option to accept older
> authorisation methods, and setting such an option might fix the
> problem. But I think it would be better to use an up to date version
> of mythfrontend.
>

Wow, great detective work. I'll see if there's another version somewhere I
can get hold of. Although I think I got my APK from a link on the wiki so
it should have been ok.

>
Re: Can't connect to remote backend database (again) [ In reply to ]
> What that suggests is that the mythfrontend loaded on the CGTV was
>> compiled using an out of date version of the MySQL client library. It
>> is possible that the MySQL server may have an option to accept older
>> authorisation methods, and setting such an option might fix the
>> problem. But I think it would be better to use an up to date version
>> of mythfrontend.
>>
>
> Wow, great detective work. I'll see if there's another version somewhere I
> can get hold of. Although I think I got my APK from a link on the wiki so
> it should have been ok.
>

I've installed every version of the app I can get my hands on and still
can't connect, so I guess they must all have the same issue.

Could you please advise how I can change the MySQL settings to accept older
auth methods?

>
Re: Can't connect to remote backend database (again) [ In reply to ]
On Wed, 25 Aug 2021 22:30:33 +1000, you wrote:

>> What that suggests is that the mythfrontend loaded on the CGTV was
>>> compiled using an out of date version of the MySQL client library. It
>>> is possible that the MySQL server may have an option to accept older
>>> authorisation methods, and setting such an option might fix the
>>> problem. But I think it would be better to use an up to date version
>>> of mythfrontend.
>>>
>>
>> Wow, great detective work. I'll see if there's another version somewhere I
>> can get hold of. Although I think I got my APK from a link on the wiki so
>> it should have been ok.
>>
>
>I've installed every version of the app I can get my hands on and still
>can't connect, so I guess they must all have the same issue.
>
>Could you please advise how I can change the MySQL settings to accept older
>auth methods?

It looks like you need to do this to the MySQL server config:

[mysqld]
default_authentication_plugin=mysql_native_password

See here:

https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password

I am running MariaDB these days, so I can not test that setting, but I
think all you need to do is to put those lines in a new file in
/etc/mysql/conf.d. Call it "old_auth.cnf" for example. The file
should be "chown root:root" and "chmod u=rw,g=r,o=r". Then restart
mysqld:

sudo systemctl restart mysqld

This problem should only have happened if you have installed MySQL
version >=8 and then created users for MythTV. If you created the
MySQL users for MythTV on an older version of MySQL and then upgraded
MySQL to v8 it should have retained the older auth settings for all
the existing users.

It should also be possible to change the auth setting per user back to
the old method:

ALTER USER <user>
IDENTIFIED WITH mysql_native_password
BY '<password>';

You may need to do the ALTER USER command or delete and re-create the
user for the CGTV device even though you have added that config file
as new users created on v8+ get the then current default
authentication setting, which was "caching_sha2_password" at the time
that user was created.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
>
> >Could you please advise how I can change the MySQL settings to accept
> older
> >auth methods?
>
> It looks like you need to do this to the MySQL server config:
>
> [mysqld]
> default_authentication_plugin=mysql_native_password
>
>
> I am running MariaDB these days, so I can not test that setting, but I
> think all you need to do is to put those lines in a new file in
> /etc/mysql/conf.d. Call it "old_auth.cnf" for example. The file
> should be "chown root:root" and "chmod u=rw,g=r,o=r". Then restart
> mysqld:
>
> sudo systemctl restart mysqld
>
> This problem should only have happened if you have installed MySQL
> version >=8 and then created users for MythTV. If you created the
> MySQL users for MythTV on an older version of MySQL and then upgraded
> MySQL to v8 it should have retained the older auth settings for all
> the existing users.
>
> It should also be possible to change the auth setting per user back to
> the old method:
>
> ALTER USER <user>
> IDENTIFIED WITH mysql_native_password
> BY '<password>';
>
> You may need to do the ALTER USER command or delete and re-create the
> user for the CGTV device even though you have added that config file
> as new users created on v8+ get the then current default
> authentication setting, which was "caching_sha2_password" at the time
> that user was created.
>

Thanks Stephen. I tried what you suggested and changed the MySQL settings
but the Chomecast with Google TV still wouldn't connect. So I dropped the
user account in MySQL and re-created it. Still no joy - even though the PC
sitting right next to it on the same subnet connects without problems.

I also contacted the developer of the mythtvfrontend Android app and
relayed your theory to him. He was very helpful and tried installing and
connecting and it all worked fine for him. After his testing he said "So it
is not an incompatibility with mysql or with recent versions that is
causing the problem".

I've also tried to install a MySQL client on the device. But there's only
one I could find, and it doesn't work on Google TV because the UI won't let
you create a connection database using a remote control. The developer is
going to address that in the next release but I have no idea when that will
be.

So I'm now even more stumped than I was before.
Re: Can't connect to remote backend database (again) [ In reply to ]
On Sat, 4 Sep 2021 17:34:58 +1000, you wrote:

>>
>> >Could you please advise how I can change the MySQL settings to accept
>> older
>> >auth methods?
>>
>> It looks like you need to do this to the MySQL server config:
>>
>> [mysqld]
>> default_authentication_plugin=mysql_native_password
>>
>>
>> I am running MariaDB these days, so I can not test that setting, but I
>> think all you need to do is to put those lines in a new file in
>> /etc/mysql/conf.d. Call it "old_auth.cnf" for example. The file
>> should be "chown root:root" and "chmod u=rw,g=r,o=r". Then restart
>> mysqld:
>>
>> sudo systemctl restart mysqld
>>
>> This problem should only have happened if you have installed MySQL
>> version >=8 and then created users for MythTV. If you created the
>> MySQL users for MythTV on an older version of MySQL and then upgraded
>> MySQL to v8 it should have retained the older auth settings for all
>> the existing users.
>>
>> It should also be possible to change the auth setting per user back to
>> the old method:
>>
>> ALTER USER <user>
>> IDENTIFIED WITH mysql_native_password
>> BY '<password>';
>>
>> You may need to do the ALTER USER command or delete and re-create the
>> user for the CGTV device even though you have added that config file
>> as new users created on v8+ get the then current default
>> authentication setting, which was "caching_sha2_password" at the time
>> that user was created.
>>
>
>Thanks Stephen. I tried what you suggested and changed the MySQL settings
>but the Chomecast with Google TV still wouldn't connect. So I dropped the
>user account in MySQL and re-created it. Still no joy - even though the PC
>sitting right next to it on the same subnet connects without problems.
>
>I also contacted the developer of the mythtvfrontend Android app and
>relayed your theory to him. He was very helpful and tried installing and
>connecting and it all worked fine for him. After his testing he said "So it
>is not an incompatibility with mysql or with recent versions that is
>causing the problem".
>
>I've also tried to install a MySQL client on the device. But there's only
>one I could find, and it doesn't work on Google TV because the UI won't let
>you create a connection database using a remote control. The developer is
>going to address that in the next release but I have no idea when that will
>be.
>
>So I'm now even more stumped than I was before.

If you capture the TCP/IP packets again, is it the same as before - is
it still the same error message?
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
>
>
>
> >Thanks Stephen. I tried what you suggested and changed the MySQL settings
> >but the Chomecast with Google TV still wouldn't connect. So I dropped the
> >user account in MySQL and re-created it. Still no joy - even though the PC
> >sitting right next to it on the same subnet connects without problems.
> >
> >I also contacted the developer of the mythtvfrontend Android app and
> >relayed your theory to him. He was very helpful and tried installing and
> >connecting and it all worked fine for him. After his testing he said "So
> it
> >is not an incompatibility with mysql or with recent versions that is
> >causing the problem".
> >
> >I've also tried to install a MySQL client on the device. But there's only
> >one I could find, and it doesn't work on Google TV because the UI won't
> let
> >you create a connection database using a remote control. The developer is
> >going to address that in the next release but I have no idea when that
> will
> >be.
> >
> >So I'm now even more stumped than I was before.
>
> If you capture the TCP/IP packets again, is it the same as before - is
> it still the same error message?
>

Thanks very much, Stephen, for your patient assistance with this one. I
didn't try your last suggestion. But I have fixed the problem. When I
disconnected the wired ethernet connection and connected with WiFi
instead,Mythfrontend connected without any issues. Obviously I'm delighted
with this development. But I have no idea why it can connect over WiFi but
not ethernet when they're on the same subnet. It doesn't make sense to me.
Do you think there could be a bug of some sort with the devices' ethernet
implementation? The ethernet cable connects into the power supply which is
an adaptor sold by Google -
https://store.google.com/au/product/chromecast_ethernet_adapter_gen_2?hl=en-GB

It's good news that it's working. But the WiFi connection obviously isn't
as fast as the ethernet connection, so I would like to get it going over
ethernet eventually if I can. I might try a powered USB hub and connect the
ethernet to that instead of the power supply and see if that works. i did
have one but I've lost it!
Re: Can't connect to remote backend database (again) [ In reply to ]
On 12/09/2021 08:48, Phill Edwards wrote:
>>
>>
>>
>>> Thanks Stephen. I tried what you suggested and changed the MySQL settings
>>> but the Chomecast with Google TV still wouldn't connect. So I dropped the
>>> user account in MySQL and re-created it. Still no joy - even though the PC
>>> sitting right next to it on the same subnet connects without problems.
>>>
>>> I also contacted the developer of the mythtvfrontend Android app and
>>> relayed your theory to him. He was very helpful and tried installing and
>>> connecting and it all worked fine for him. After his testing he said "So
>> it
>>> is not an incompatibility with mysql or with recent versions that is
>>> causing the problem".
>>>
>>> I've also tried to install a MySQL client on the device. But there's only
>>> one I could find, and it doesn't work on Google TV because the UI won't
>> let
>>> you create a connection database using a remote control. The developer is
>>> going to address that in the next release but I have no idea when that
>> will
>>> be.
>>>
>>> So I'm now even more stumped than I was before.
>>
>> If you capture the TCP/IP packets again, is it the same as before - is
>> it still the same error message?
>>
>
> Thanks very much, Stephen, for your patient assistance with this one. I
> didn't try your last suggestion. But I have fixed the problem. When I
> disconnected the wired ethernet connection and connected with WiFi
> instead,Mythfrontend connected without any issues. Obviously I'm delighted
> with this development. But I have no idea why it can connect over WiFi but
> not ethernet when they're on the same subnet. It doesn't make sense to me.
> Do you think there could be a bug of some sort with the devices' ethernet
> implementation? The ethernet cable connects into the power supply which is
> an adaptor sold by Google -
> https://store.google.com/au/product/chromecast_ethernet_adapter_gen_2?hl=en-GB
>
> It's good news that it's working. But the WiFi connection obviously isn't
> as fast as the ethernet connection, so I would like to get it going over
> ethernet eventually if I can. I might try a powered USB hub and connect the
> ethernet to that instead of the power supply and see if that works. i did
> have one but I've lost it!
>
It is possible that you are misunderstanding the function of the device you link to. (It is also
possible that I am misunderstanding it!)

From my reading of the very sketchy description, this device is designed for locations where a WiFi
signal is poor or non-existent. Therefore, I would think that all it has is a mini-WiFi access point
from which the Chromecast can get a local signal.

It won't be sending Ethernet up the power cable, if that's what you assumed.

--

Mike Perkins

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Can't connect to remote backend database (again) [ In reply to ]
On 12/09/2021 10:23, Mike Perkins wrote:
> On 12/09/2021 08:48, Phill Edwards wrote:
>>>
>>>
>>>
>>>> Thanks Stephen. I tried what you suggested and changed the MySQL
>>>> settings
>>>> but the Chomecast with Google TV still wouldn't connect. So I
>>>> dropped the
>>>> user account in MySQL and re-created it. Still no joy - even though
>>>> the PC
>>>> sitting right next to it on the same subnet connects without problems.
>>>>
>>>> I also contacted the developer of the mythtvfrontend Android app and
>>>> relayed your theory to him. He was very helpful and tried installing
>>>> and
>>>> connecting and it all worked fine for him. After his testing he said
>>>> "So
>>> it
>>>> is not an incompatibility with mysql or with recent versions that is
>>>> causing the problem".
>>>>
>>>> I've also tried to install a MySQL client on the device. But there's
>>>> only
>>>> one I could find, and it doesn't work on Google TV because the UI won't
>>> let
>>>> you create a connection database using a remote control. The
>>>> developer is
>>>> going to address that in the next release but I have no idea when that
>>> will
>>>> be.
>>>>
>>>> So I'm now even more stumped than I was before.
>>>
>>> If you capture the TCP/IP packets again, is it the same as before - is
>>> it still the same error message?
>>>
>>
>> Thanks very much, Stephen, for your patient assistance with this one. I
>> didn't try your last suggestion. But I have fixed the problem. When I
>> disconnected  the wired ethernet connection and connected with WiFi
>> instead,Mythfrontend connected without any issues. Obviously I'm
>> delighted
>> with this development. But I have no idea why it can connect over WiFi
>> but
>> not ethernet when they're on the same subnet. It doesn't make sense to
>> me.
>> Do you think there could be a bug of some sort with the devices' ethernet
>> implementation? The ethernet cable connects into the power supply
>> which is
>> an adaptor sold by Google -
>> https://store.google.com/au/product/chromecast_ethernet_adapter_gen_2?hl=en-GB
>>
>>
>> It's good news that it's working. But the WiFi connection obviously isn't
>> as fast as the ethernet connection, so I would like to get it going over
>> ethernet eventually if I can. I might try a powered USB hub and
>> connect the
>> ethernet to that instead of the power supply and see if that works. i did
>> have one but I've lost it!
>>
> It is possible that you are misunderstanding the function of the device
> you link to. (It is also possible that I am misunderstanding it!)
>
> From my reading of the very sketchy description, this device is
> designed for locations where a WiFi signal is poor or non-existent.
> Therefore, I would think that all it has is a mini-WiFi access point
> from which the Chromecast can get a local signal.
>
> It won't be sending Ethernet up the power cable, if that's what you
> assumed.
>

That page does say that the Chromecast with Google TV 'requires a Wi-Fi
network'.

The FireTVstick 4k has an optional Ethernet adapter that does apparently
provide 'Ethernet up the power cable'. I didn't get one because my
Firestick is only 1m from my router. The wifi connection works well for
me, but I have never tried 4k content or had other wifi users online.

John P

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

1 2  View All