[mythtv-users] SystemD (Was: Recommended Linux Distro post CentOS)

[Mike Perkins]

On 26/12/2020 04:04, marcus hall wrote:
> On Fri, Dec 25, 2020 at 10:59:18PM -0500, R. G. Newbury wrote:
>>
>> Ah HAH! You have the db server and an FE on one box. So where is the BE? If
>> it is on another box, then quite possibly your BE box cannot access the
>> dbserver and (drum-roll....) the BE will not start.
>> If the BE is on the same box with the db server (and an FE) there is still
>> the possibility that the BE 'user' is not properly authenticated to the
>> mariadb server.
> 
> One box has mariadb, mythbackend, and one instance of frontend.  Other
> frontends scattered throughout the house.
> 
> I do not believe that there is any issue with mythtv.  Once the system boots
> and I can ssh into it, I run systemctl restart mythbackend and all comes up
> just fine.  It's just annoying that systemd can't keep trying to start
> mythbackend until it succeeds.  I've set the StartLimitInterval to 0 now,
> so we'll see if that fixes things, whenever the box needs a reboot.  That
> may not be for some time, which is why I was not too put out to have to
> start it manually, since that is only once or twice a year.
> 
You aren't addressing the actual problem. This is not why systemd isn't restarting the myth backend 
but why it is failing to start in the first place.

Granted, this can be some set of obscure systemd interactions at startup but until you investigate 
logically you will always have the same problem.

I would point out that most of us have no problems starting up the backend/host that contains the 
backend. Most difficulties seem to originate at installation time, with database connections being 
high on the list, network connections coming close. Check through as described above and see what 
you turn up.

-- 

Mike Perkins