[mythtv-users] Can't start backend on Debian 9 (Stretch)
Ian Campbell
ijc at hellion.org.uk
Thu Jul 27 19:05:55 UTC 2017
On Thu, 2017-07-27 at 19:59 +0100, Ian Campbell wrote:
>
> I would expect that even LSB compat based stuff would show up on
> systemd based systems in things like "systemctl" and "system status"
> output, and with that you should be able to find the name it has given
> the compat unit for use with journalctl (I think it's "-u <unit>" to
> inspect a particular unit, but I don't have a running systemd system to
> check on).
I found a (non-myth) systemd system. On it I have:
$ sudo systemctl | grep LSB
cgroupfs-mount.service loaded active exited LSB: Set up cgroupfs mounts.
cpufrequtils.service loaded active exited LSB: set CPUFreq kernel parameters
● docker.service loaded failed failed LSB: Create lightweight, portable, self-sufficient containers.
I can examine the failed service with (sudo or you don't get logs, just the info):
$ sudo systemctl status docker.service
● docker.service - LSB: Create lightweight, portable, self-sufficient containers.
Loaded: loaded (/etc/init.d/docker; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2017-06-11 13:27:42 BST; 1 months 15 days ago
Docs: man:systemd-sysv-generator(8)
Process: 1501 ExecStart=/etc/init.d/docker start (code=exited, status=1/FAILURE)
Jun 11 13:27:41 dagon systemd[1]: Starting LSB: Create lightweight, portable, self-sufficient containers....
Jun 11 13:27:42 dagon docker[1501]: /usr/bin/docker not present or not executable ... failed!
Jun 11 13:27:42 dagon systemd[1]: docker.service: Control process exited, code=exited status=1
Jun 11 13:27:42 dagon systemd[1]: Failed to start LSB: Create lightweight, portable, self-sufficient containers..
Jun 11 13:27:42 dagon systemd[1]: docker.service: Unit entered failed state.
Jun 11 13:27:42 dagon systemd[1]: docker.service: Failed with result 'exit-code'.
As you can see it is using an automatically generated unit file which
is calling the LSB/sysvinit script (which is actually stale because
docker isn't installed on this machine).
I would expect you would find something similar based on
/etc/init.d/mythtv-backend on your system, and probably some sort of
error message.
Ian.
More information about the mythtv-users
mailing list