[mythtv-users] systemd suddenly won't start backend
jksjdevelop
jksjdevelop at gmail.com
Fri Apr 27 19:33:38 UTC 2018
Just spent a day resolving this issue after upgrading from Ubuntu 16.04
to 18.04. It seems the latter boots faster revealing a fault that has
always been there in my mythbackend.service.
I had
After=mysqld.service network.target
which is wrong for ubuntu - should be
After=mysql.service network.target
My point is the faulty config worked for 2 years it is only the speed
change that revealed it
On 27/04/18 17:01, Bill Meek wrote:
> ...
>
> On 04/27/2018 08:31 AM, Michael T. Dean wrote:
>>
>> Most likely a different environment (though not necessarily/likely
>> PATH). Your user's environment is properly configured--has a good
>> $HOME, which has a good $HOME/.mythtv/config.xml (based on "su -c
>> mythtv mythbackend" working). I'm guessing that the systemctl
>> environment isn't set up right (anymore). Compare the logs and look
>> at the "Using configuration directory" lines...
>
> And ...
>
> systemctl cat mythtv-backend.service will show what's in play. If the
> OP manually
> changed things in /lib/systemd/system rather than making them in
> /etc/systemd/system,
> then the package manager could have released a new version that
> overwrote the changes.
>
> systemctl edit [--full] is useful if the above is true.
>
More information about the mythtv-users
mailing list