<div dir="ltr">On Thu, Jul 27, 2017 at 3:19 PM, Mike Perkins <span dir="ltr"><<a href="mailto:mikep@randomtraveller.org.uk" target="_blank">mikep@randomtraveller.org.uk</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 27/07/17 20:05, Ian Campbell wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, 2017-07-27 at 19:59 +0100, Ian Campbell wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I would expect that even LSB compat based stuff would show up on<br>
systemd based systems in things like "systemctl" and "system status"<br>
output, and with that you should be able to find the name it has given<br>
the compat unit for use with journalctl (I think it's "-u <unit>" to<br>
inspect a particular unit, but I don't have a running systemd system to<br>
check on).<br>
</blockquote>
<br>
I found a (non-myth) systemd system. On it I have:<br>
$ sudo systemctl | grep LSB<br>
cgroupfs-mount.service loaded active exited LSB: Set up cgroupfs mounts.<br>
cpufrequtils.service loaded active exited LSB: set CPUFreq kernel parameters<br>
● docker.service loaded failed failed LSB: Create lightweight, portable, self-sufficient containers.<br>
<br>
I can examine the failed service with (sudo or you don't get logs, just the info):<br>
<br>
$ sudo systemctl status docker.service<br>
● docker.service - LSB: Create lightweight, portable, self-sufficient containers.<br>
Loaded: loaded (/etc/init.d/docker; generated; vendor preset: enabled)<br>
Active: failed (Result: exit-code) since Sun 2017-06-11 13:27:42 BST; 1 months 15 days ago<br>
Docs: man:systemd-sysv-generator(8)<br>
Process: 1501 ExecStart=/etc/init.d/docker start (code=exited, status=1/FAILURE)<br>
<br>
Jun 11 13:27:41 dagon systemd[1]: Starting LSB: Create lightweight, portable, self-sufficient containers....<br>
Jun 11 13:27:42 dagon docker[1501]: /usr/bin/docker not present or not executable ... failed!<br>
Jun 11 13:27:42 dagon systemd[1]: docker.service: Control process exited, code=exited status=1<br>
Jun 11 13:27:42 dagon systemd[1]: Failed to start LSB: Create lightweight, portable, self-sufficient containers..<br>
Jun 11 13:27:42 dagon systemd[1]: docker.service: Unit entered failed state.<br>
Jun 11 13:27:42 dagon systemd[1]: docker.service: Failed with result 'exit-code'.<br>
<br>
As you can see it is using an automatically generated unit file which<br>
is calling the LSB/sysvinit script (which is actually stale because<br>
docker isn't installed on this machine).<br>
<br>
I would expect you would find something similar based on<br>
/etc/init.d/mythtv-backend on your system, and probably some sort of<br>
error message.<br>
<br>
</blockquote>
Yes, and that's what I did find, that systemd generates a temporary .service file.<br>
<br>
Trouble is, the log lies:<br>
<br>
root@jade:/home/micheal# systemctl status mythtv-backend<br>
● mythtv-backend.service - LSB: Start/Stop the MythTV server.<br>
Loaded: loaded (/etc/init.d/mythtv-backend; generated; vendor preset: enabled)<br>
Active: active (exited) since Thu 2017-07-27 15:42:01 BST; 5h 24min ago<br>
Docs: man:systemd-sysv-generator(8)<br>
Tasks: 0 (limit: 4915)<br>
CGroup: /system.slice/mythtv-backend.s<wbr>ervice<br>
<br>
Jul 27 15:41:56 jade systemd[1]: Starting LSB: Start/Stop the MythTV server....<br>
Jul 27 15:42:01 jade mythtv-backend[706]: Starting MythTV server: mythbackend .<br>
Jul 27 15:42:01 jade systemd[1]: Started LSB: Start/Stop the MythTV server..<br>
root@jade:/home/micheal#<br>
<br>
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.<span class="HOEnZb"></span></blockquote><div><br></div><div>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)..<br><br></div><div>Just tossing that out in case you already had it running and tried to stop it with systemd.<br></div><div> </div></div></div></div>