[mythtv-users] Unable to connect to the master backend at 192.168.1.100:6543 (16.04 & 0.28)

Fred Hamilton fred at yonkitime.com
Sun Apr 17 02:13:44 UTC 2016


On Sat, Apr 16, 2016 at 5:50 PM, Bill Meek <keemllib at gmail.com> wrote:

> Be sure to check all copies of config.xml, e.g.:
>
>     grep "<Host>" {~mythtv,~}/.mythtv/config.xml
>
> Having localhost in the config.xml causes a socket connection
> rather than using a TCP connection, which is good.
>

Check - the grep command returned 2 instances of localhost:

/home/mythtv/.mythtv/config.xml:    <Host>localhost</Host>
/home/fred/.mythtv/config.xml:    <Host>localhost</Host>

To try to reduce this sort of confusion, I actually
made /home/mythtv/.mythtv/config.xml a link to the editable
/home/fred/.mythtv/config.xml.

What do these (run on the backend) return:
>
>     nmap -p6543 --reason -6 ::1
>     nmap -p6543 --reason 127.0.0.1
>     nmap -p6543 --reason 192.168.1.100
>
> You want to see this:
>
>    PORT     STATE SERVICE REASON
>    6543/tcp open  mythtv  syn-ack


The first two work as above.   192.168.1.100 returns
Nmap scan report for MythPC (192.168.1.100)
Host is up, received syn-ack (0.00012s latency).
PORT     STATE  SERVICE REASON
6543/tcp closed mythtv  conn-refused

Not so good...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160416/0dd6ee6f/attachment.html>


More information about the mythtv-users mailing list