[mythtv-users] systemd suddenly won't start backend

[Robin Gilks]

> Hoi stinga,
>
> Friday, April 27, 2018, 1:36:15 PM, you wrote:
>
>> On 27/04/18 03:31, Robin Gilks wrote:
>>> Apr 27 00:31:00 woden mythbackend: mythbackend[2047]: E CoreContext
>>> mythdbcon.cpp:230 (OpenDatabase) Driver error was [1/2003]:
>>> QMYSQL: Unable to connect
>>> Database error was:
>>> Can't connect to MySQL server on '192.168.1.12' (111)
>>>
>>>
>>> If I run the backend from a terminal using
>>>      su -c mythtv mythbackend
>>> everything works fine
>>>
>>> Nothing has been updated as far as I know, I can only assume some mysql
>>> setting has changed due to a regular upgrade/update.
>> If it runs one way and not another it usually is due to different PATH
>> setting, privileges or timing.
>
>> the errors you gave don't say it failed permanently, it would keep
>> trying until it can connect.
>
> My guess would be that for whatever reason your network or database
> are not jet fully up when mythbackend starts. It's known to happen
> unpredictably. So try setting a delay on the start of mythbackend. See
> the "Lose TV tuners after PC reboot" thread earlier this week on
> suggestions on how to go about that.

I know its not a timing issue as a manual attempt (several in fact) at using
   systemctl start mythtv-backend.service
12 hours after the reboot failed as well.

Can't think what may have changed since the last reboot (even when there
is months between them!!).


-- 
Robin Gilks