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

[marcus hall]

On Thu, Dec 24, 2020 at 04:30:47PM +1300, Stephen Worthington wrote:
> # MariaDB seems to have a systemd related bug and tells systemd that
> it is
> # ready to accept connections before it really is. If you have this
> problem
> # try uncommenting the following lines:
> # Restart=on-failure
> # StartLimitBurst=5
> # StartLimitInterval=1
 
Yeah, that's what Geoff had pointed out..

> So the above settings are not a good workaround at all.  It would be
> better to use something like this:
> 
> Restart=on-failure
> RestartSec=5
> StartLimitBurst=5
> StartLimitInterval=30
 
I had at the time installed an override file with Restart=always and
RestartSec=3 in it.  As you pointed out, that might flood things if
mythbackend started failing rapidly, but it seemed like a "good enough"
fix.  But, systemd fires up mythbackend once and then leaves it in a
failed state.

If mythbackend dies for some other reason, I would really want it to be
restarted.  Like the old-school inittab.  And systemd's configuration
clearly implies that it is intended to do this, but I was unable to find
any clue from systemd as to why it was ignoring the Restart setting.
If it was something that could be broken apart into pieces, I could
easily instrument pieces, or run strace on it, or something to get an
idea of why different paths are taken, but systemd is too monolithic
and impenetrable to yeild to such techniques.  So I gave up.

marcus hall
marcsu at tuells.org