[mythtv-users] Can't start backend on Debian 9 (Stretch)

Greg Oliver oliver.greg at gmail.com
Thu Jul 27 21:04:26 UTC 2017


On Thu, Jul 27, 2017 at 3:19 PM, Mike Perkins <mikep at randomtraveller.org.uk>
wrote:

> On 27/07/17 20:05, Ian Campbell wrote:
>
>> 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.
>>
>> Yes, and that's what I did find, that systemd generates a temporary
> .service file.
>
> Trouble is, the log lies:
>
> root at jade:/home/micheal# systemctl status mythtv-backend
> ● mythtv-backend.service - LSB: Start/Stop the MythTV server.
>    Loaded: loaded (/etc/init.d/mythtv-backend; generated; vendor preset:
> enabled)
>    Active: active (exited) since Thu 2017-07-27 15:42:01 BST; 5h 24min ago
>      Docs: man:systemd-sysv-generator(8)
>     Tasks: 0 (limit: 4915)
>    CGroup: /system.slice/mythtv-backend.service
>
> Jul 27 15:41:56 jade systemd[1]: Starting LSB: Start/Stop the MythTV
> server....
> Jul 27 15:42:01 jade mythtv-backend[706]: Starting MythTV server:
> mythbackend .
> Jul 27 15:42:01 jade systemd[1]: Started LSB: Start/Stop the MythTV
> server..
> root at jade:/home/micheal#
>
> Unfortunately, 15:42 is the time I shut down the working system before I
> redid the database. Apart from the time I ran it manually, all attempts to
> start or restart mythtv-backend produce exactly nothing. NO activity I did
> afterwards appears to exist in the logs, such as I could figure out of them.


Just a quick note - I am sure you have tried, but I should mention it.  If
you try to stop a service with systemd (systemctl) that was not started
with systemctl, systemd will silently not stop it for you.  If mythbackend
is not running, systemd should start it though (in a perfect world where
units exist, etc)..

Just tossing that out in case you already had it running and tried to stop
it with systemd.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170727/73236c0d/attachment.html>


More information about the mythtv-users mailing list