[mythtv-users] frontend fails

Mike Bibbings mike.bibbings at gmail.com
Fri Feb 24 15:07:27 UTC 2017


On 24/02/17 14:51, Peter Bennett wrote:
>
>
> On 02/24/2017 09:36 AM, Greg Oliver wrote:
>> I have also found that with 0.28, if the backend starts up before the
>> network, 2 things happen:
>>
>> 1.  It only binds to localhost and never binds to the interface IP
>> even after it comes up.
>> 2.  All network tuners cannot be used until it is restarted and it
>> binds to the interface address.  Local tuners work OK.
>>
>> Major step backward from previous (< 0.28) behaviour.
>
> Can you create a ticket for this. If you have created one, let me know 
> the number and I will look into this, as I am currently looking at 
> network issues.
>
> Do you have a way to reproduce this for testing purposes?
>
> Peter
> _______________________________________________ 

Don.t know if a ticket has been raised, but this problem has been 
discussed in a number of threads and on mythtv forum, it is related to 
Systemd starting a whole lot of things in parallel on 16.04 systems, and 
mythtv-backend.service file not having  "wait for network... ".  I have 
done the following (based on thread discussions) :

To make sure backend start after network is properly configured:
In a terminal on the machine running mythtv backend:

sudo systemctl enable NetworkManager-wait-online.service
sudo systemctl edit mythtv-backend.service

Then paste the following 2 lines
[Unit]
After=NetworkManager-wait-online.service

Then exit from the edit screen (it uses nano by default, so Ctrl+x, then 
y, then Return key)

Now reboot the system (sudo reboot)

In the past I have reproduced the problem by having the mythbackend 
machine get its IP address from the Router  (this is slower than 
configuring the mythbackend machine IP address in say 
/etc/network/interfaces). Mythbuntu 16.04 was installed on an SSD so it 
starts much faster than spinning disks.

Mike




More information about the mythtv-users mailing list