[mythtv-users] frontend fails

[Peter Bennett]

On 02/24/2017 10:57 AM, Curtis Gedak wrote:
> On 2017-02-24 08:29 AM, Peter Bennett wrote:
>> For the next version (29) I am building code in mythfrontend to wait for
>> the network during startup. It looks like it would be useful to have it
>> for backend startup also.
>>
>> Peter
>>
>
> Hi Peter,
>
> Regarding mythbackend waiting for network during startup, I can think of
> one potential issue.
>
> What would happen with a combined backend/frontend that received it's
> schedule information Over-The-Air via antenna, and was not connected to
> a network?
>
> I am thinking of a standalone MythTV system running in a remote location
> without Internet access.
>
> Of course this issue would not be present with a separate frontend
> system because it would require a network to access the backend.
>
> Regards,
> Curtis
>
>
> _______________________________________________
>

Hi Curtis

My thinking was for the backend to wait until (in sequence)

1. Database can connect
2. The backend's IP address is available on an interface (backend IP 
address is stored in the mythtv database for each backend, by name).

If you do not have a (external) network you must set the database and 
backend to ip address 127.0.0.1 (or ::1 if using IPV6) for it to work. 
It would find that address on the loopback interface and would continue 
startup. I think you always need at least the loopback network interface.

If you have a network, you need to set up your network ip address in the 
database, then it will wait for that ip address to be available before 
backend can proceed with startup.

Item 1. is already done in master. Item 2. should not be hard.

Let me know if there are any issues with all this.

Peter