[mythtv-users] frontend fails

James Linder jam at tigger.ws
Fri Feb 24 14:46:26 UTC 2017



On 24/2/17 8:00 pm, mythtv-users-request at mythtv.org wrote:
>> Hi
>> I'm building a myth system for a mate.
>> Because of hastles with mythbuntu I've built from source (MythTV Version
>> : v0.28.1-3-gfc737ff-dirty) and made a deb and am running on ubuntu 16.04.
>> Backend / Frontend machine works normally.
>>
>> A seperate frontend machine cannot find the backend.
>>
>> myth at slave:~$ telnet ws132 6543
>> Trying 192.168.5.132...
>> telnet: Unable to connect to remote host: Connection refused
>>
>> OK that's clearly the reason
>>
>> myth at master:~$ netstat -anp |grep 6543
>> tcp        0      0 127.0.0.1:6543          0.0.0.0:* LISTEN      -
>> tcp6       0      0 fe80::fc70:940a:21:6543 :::* LISTEN      -
>> tcp6       0      0 ::1:6543                :::* LISTEN      -
>>
>> Hmm nothing in setup mentions 127... or localhost.
>> I see nothing in config that would say localhost.
>> My own master backend (also compiled from source  MythTV Version :
>> v0.28.1-3-gfc737ff) is quite different:
>>
>> [sandypit] /home/jam [628]% netstat -anp |grep 6543
>> tcp        0      0 192.168.5.33:6543       0.0.0.0:* LISTEN      -
>> tcp        0      0 127.0.0.1:6543          0.0.0.0:* LISTEN      -
>> tcp        0      0 ::1:6543                :::* LISTEN      -
>>
>> Can anyone cast light light on what is happening, more importantly why?
>>
>>
>> Thanks
>> James
>> _______________________________________________
> If it is only listening on 127.0.0.1 as it appears from netstat then you will need to rerun mythtv-setup on the master backend and check the values for IPv4 address and Master Backend IP address. One of them appears to be either localhost or 127.0.0.1.
Both are the valid 192.168 addresses
> The remote frontend also needs access to the database. Check the machine hosting the database that mysql / mariadb / etc needs to be remotely accessible. Out of the box mysql / mariadb are probably only binding to localhost:3306. Check on the machine hosting the database (I'll guess your backend) by running:
> netstat -anp |grep 3306
mysql -umythtv -pmythtv -hws132 mythconverg (from the remote frontend 
machine)
works properly
> If it is also only listening on localhost check mysql / mariadb conf file for bind address and change to backend IP or 0.0.0.0 (assuming IPv4).
> Check firewall on backend is not blocking ports 6306, 6543 and 6544
no iptables load or in effect
> mysql / mariadb database needs to be configured for remote access. Check here for more infohttps://www.mythtv.org/wiki/Database_Setup  but may need to run something like this inside mysql / mariadb
> mysql -uroot -p
> mysql> grant all on mythconverg.* to mythtv@"my.remote.ip.addr" identified by "myth_tv_password";
> mysql> flush privileges;
 > show grants for mythtv@'%';

gives the correct answers


So my confusion is justified. I'll try changing '%' to '192.168.5.%' to 
see what happens. Meanwhile I'm really confused.

Thanks Mark
James


More information about the mythtv-users mailing list