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

[Bill Meek]

On 04/16/2016 09:13 PM, Fred Hamilton wrote:
> On Sat, Apr 16, 2016 at 5:50 PM, Bill Meek <keemllib at gmail.com> wrote:
...
> 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

OK, that plus your earlier post:

$ sudo netstat -tnlp | grep :6543
     tcp    0      0 127.0.0.1:6543 0.0.0.0:*  LISTEN 2550/mythbackend
     tcp6   0      0 ::1:6543            :::*  LISTEN 2550/mythbackend

says the backend isn't listening on the Private Network address.
It is listening on localhost and localhost6.

When the backend starts, you should see lines similar to these in
mythbackend.log:

     ... CoreContext serverpool.cpp:407 (listen) - Listening on TCP 127.0.0.1:6543
     ... CoreContext serverpool.cpp:407 (listen) - Listening on TCP 192.168.1.100:6543

I suspect the 1st is there, but the 2nd isn't (there are more, this is just a sample.)

Since earlier you mentioned changing some /etc/hosts entries, I'd
give this box a warm restart. Just restarting the backend might work.
As I recall, the BE only detects available addresses when it starts up.

Then when it comes backup, does ifconfig show your 192.168.1.100 address on
a line like this:

     inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0

-- 
Bill