[mythtv-users] Mythbackend may be starting too soon?

[Don Brett]

I have a new build of Mythbuntu 16.04 and having problems getting HD-PVR 
to do anything.  I've traced it down to an error reported in the 
mythbackend log:

May 21 12:35:34 nick mythbackend: mythbackend[1124]: C CoreContext 
serverpool.cpp:269 (SelectDefaultListen) ServerPool: Host is configured 
to listen on 192.168.0.124, but address is not used on any local network 
interfaces.
....followed by several errors about the HDHR's.
....then, it's followed by:

May 21 12:35:36 nick mythbackend: mythbackend[1124]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 127.0.0.1:6544
May 21 12:35:36 nick mythbackend: mythbackend[1124]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP [::1]:6544
May 21 12:35:36 nick mythbackend: mythbackend[1124]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 127.0.0.1:6554
May 21 12:35:36 nick mythbackend: mythbackend[1124]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP [::1]:6554
May 21 12:35:36 nick mythbackend: mythbackend[1124]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 127.0.0.1:6549
May 21 12:35:36 nick mythbackend: mythbackend[1124]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP [::1]:6549

I added a backend restart into rc.local, which resulted in: (sudo 
service mythtv-backend restart)

Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 127.0.0.1:6544
Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 192.168.0.124:6544
Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP [::1]:6544
Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 
[fe80::c81f:a37c:7ce5:d43c%enp2s0]:6544
Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 127.0.0.1:6554
Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 192.168.0.124:6554
Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP [::1]:6554
Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 
[fe80::c81f:a37c:7ce5:d43c%enp2s0]:6554
Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 127.0.0.1:6549
Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 192.168.0.124:6549
Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP [::1]:6549
Jul  2 12:02:03 nick mythbackend: mythbackend[1828]: I CoreContext 
serverpool.cpp:407 (listen) Listening on TCP 
[fe80::c81f:a37c:7ce5:d43c%enp2s0]:6549

Now the HD-PVR works better (but the remote stopped working, don't know 
if restart has anything to do with it).  Is there a way make mythbackend 
wait until the network is ready?


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus