Opened 3 years ago

Closed 3 years ago

#12711 closed Bug Report - General (Invalid)

Frontend Services API Not listening on local ipv4 address

Reported by: Jon Heizer <jheizer@…> Owned by:
Priority: minor Milestone: unknown
Component: MythTV - Services API - Frontend Version: 0.28.0
Severity: medium Keywords:
Cc: Ticket locked: no

Description (last modified by Bill Meek)

The Frontend Services API is only listening on

Apr  5 11:10:37 mythtv-familyroom mythfrontend.real: mythfrontend[3695]: I CoreContext serverpool.cpp:407 (listen) Listening on TCP 127.0.0.1:6547

Apr  5 11:10:37 mythtv-familyroom mythfrontend.real: mythfrontend[3695]: I CoreContext serverpool.cpp:407 (listen) Listening on TCP [::1]:6547

Apr  5 11:10:37 mythtv-familyroom mythfrontend.real: mythfrontend[3695]: I CoreContext serverpool.cpp:407 (listen) Listening on TCP [fe80::4a5b:39ff:fea7:9d9b%eth0]:6547

And not the local ipv4 or the (standard?)ipv6 address. It is accessible via the link-local ipv6 address.

MythTV Version : v0.28-rc1-3-g2520617

Attachments (2)

mythfrontend.g2520617.log (470.5 KB) - added by Jon Heizer <jheizer@…> 3 years ago.
mythfrontend.g721e5cb.log (22.3 KB) - added by Jon Heizer <jheizer@…> 3 years ago.
Updated to g721e5cb

Download all attachments as: .zip

Change History (9)

comment:1 Changed 3 years ago by Bill Meek

Description: modified (diff)
Status: newinfoneeded_new
Summary: Frontend Service API Not listening on local ipv4 addressFrontend Services API Not listening on local ipv4 address

Jon, please attach the file generated by

mythfrontend --logpath /tmp -v general:debug,http:debug,upnp:debug

This 'works for me' on v0.28-pre-3733-g0538318.

Changed 3 years ago by Jon Heizer <jheizer@…>

Attachment: mythfrontend.g2520617.log added

Changed 3 years ago by Jon Heizer <jheizer@…>

Attachment: mythfrontend.g721e5cb.log added

Updated to g721e5cb

comment:2 Changed 3 years ago by Jon Heizer <jheizer@…>

They are a bit big as my home automation stuff maps out to Upnp devices.

I'm not sure why it has:

ServerPool: Host is configured to listen on 10.0.0.197, but address is not used on any local network interfaces.

That is the IP of my master backend.

And

(listen) - Failed listening on TCP 127.0.0.1:6547 - Error 8: The bound address is already in use

jon@mythtv-familyroom:/tmp$ lsof -i :6547
COMMAND    PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
mythfront 2322  jon   27u  IPv4  15841      0t0  TCP localhost:6547 (LISTEN)
mythfront 2322  jon   28u  IPv6  15842      0t0  TCP ip6-localhost:6547 (LISTEN)
mythfront 2322  jon   29u  IPv6  15846      0t0  TCP [fe80::4a5b:39ff:fea7:9d9b]:6547 (LISTEN)

comment:3 Changed 3 years ago by Bill Meek

The in use message says something else had the address in use (e.g. a FE that hadn't fully stopped.)

Does ifconfig display the skipped addresses?

54	2016-04-05 16:53:46.721903 D [5152/5152] CoreContext serverpool.cpp:195 (SelectDefaultListen) - Skipping address: 10.0.0.208
55	2016-04-05 16:53:46.721939 D [5152/5152] CoreContext serverpool.cpp:258 (SelectDefaultListen) - Skipping address: [2601:246:8201:c37c:1d1d:da88:1182:6134]
56	2016-04-05 16:53:46.721972 D [5152/5152] CoreContext serverpool.cpp:258 (SelectDefaultListen) - Skipping address: [2601:246:8201:c37c:4a5b:39ff:fea7:9d9b]

comment:4 Changed 3 years ago by Jon Heizer <jheizer@…>

jon@mythtv-familyroom:~$ sudo pkill mythfrontend
jon@mythtv-familyroom:~$ lsof -i :6547
jon@mythtv-familyroom:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 48:5b:39:a7:9d:9b
          inet addr:10.0.0.208  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: 2601:246:8201:c37c:5818:2941:a502:a0fe/64 Scope:Global
          inet6 addr: 2601:246:8201:c37c:4a5b:39ff:fea7:9d9b/64 Scope:Global
          inet6 addr: fe80::4a5b:39ff:fea7:9d9b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8436454 errors:0 dropped:0 overruns:0 frame:0
          TX packets:672533 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12459508103 (12.4 GB)  TX bytes:48890552 (48.8 MB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:370 errors:0 dropped:0 overruns:0 frame:0
          TX packets:370 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:29432 (29.4 KB)  TX bytes:29432 (29.4 KB)

jon@mythtv-familyroom:~$ sudo service lightdm restart
lightdm stop/waiting
lightdm start/running, process 3805
jon@mythtv-familyroom:~$ lsof -i :6547
COMMAND    PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
mythfront 4037  jon   30u  IPv4  25482      0t0  TCP localhost:6547 (LISTEN)
mythfront 4037  jon   31u  IPv6  25483      0t0  TCP ip6-localhost:6547 (LISTEN)
mythfront 4037  jon   32u  IPv6  25487      0t0  TCP [fe80::4a5b:39ff:fea7:9d9b]:6547 (LISTEN)

comment:5 Changed 3 years ago by Bill Meek <keemllib@…>

Please add the value of BackendServerIP from your settings. It appears to be 10.0.0.197, but the only way that the Skipping address messages print is if it is empty.

comment:6 Changed 3 years ago by Jon Heizer <jheizer@…>

mysql> select * from settings where value = 'BackendServerIP';
+-----------------+------------+---------------------+
| value           | data       | hostname            |
+-----------------+------------+---------------------+
| BackendServerIP | 10.0.0.197 | mythmasterbackend   |
| BackendServerIP | 10.0.0.197 | mythtv-familyroom   |
+-----------------+------------+---------------------+

This machine years ago had a slave backend running on it so I guess that is why only these 2 hosts have that setting set. Note this is trying to connect to the services on a now frontend only machine. I didn't think to try before, but it work connecting to the frontend on my masterbackend server.

Removing the BackendServerIP setting for that frontend seems to have solved it. I can now connect.

comment:7 Changed 3 years ago by Bill Meek

Resolution: Invalid
Status: infoneeded_newclosed

Thanks for getting back. I have a secondary backend too and can tell you that the FE on it connects to my master. The difference appears to be that its BackendServerIP = its own IP, not the master IP as as you found above. If necessary, please continue on the mailing list/forum/IRC.

Note: See TracTickets for help on using tickets.