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

M D weworama at gmail.com
Fri Jul 28 16:20:23 UTC 2017


> Stephen Worthington stephen_agent at jsw.gen.nz via mythtv.org
> 6:38 AM (5 hours ago)

>...  I have seen a
> suggestion to use a "pingnetwork.service" which pings an external
> address (eg the main switch or router on the network) and becomes
> active only after it gets a reply. It does not seem to be a builtin
> service though, so you would have to write the systemd unit file
> yourself to do that.  It would not be too difficult to do, but does
> require a bit of experience with systemd.  I have thought about doing
> it myself, but have not found the time yet.

Shouldn't the " After=mysql.service network.target" in the service file do
that?

With the caveat, I currently do not have a backend running on Stretch.  I
found on a Stretch re-install about a year ago that I yet again forgot to
check that "ping server"  box was unchecked in the backend setup - that has
stopped the backend from starting for me since about .24 (it went straight
to set-up) even on a combined FE/BE with local DB.   That has been the
default setup on deb-multimedia (and likely Mythbuntu?) for some time,
although it might have changed recently.

I use the old System V commands.  They may be buggy but they work (service
mythtv-backend).

You asked about systemd logs.  There are others around more familiar with
systemd, but my crib notes contain:

>  Look for errors in the systemd journal with
> root at debian:~/.kde/share/config# journalctl -b -p 3
(Increasing number increases verbosity)
>
> journalctl with no arguments lists all entries

I seem to recall that I had to turn that journal on/give it a quota as the
logs can overwhelm small drives.

As for systemd itself, you probably have found something similar already.

> systemctl start httpd.service
> systemctl stop httpd.service
> These commands take effect immediately to start or stop the web server
(httpd) based on its unit file. You can think of stop as the first level of
“off” for a unit in systemd.
>
> systemctl enable httpd.service
> systemctl disable httpd.service
> These commands do not take effect immediately. They ensure the service
will be started (or not) after the next system boot. You can think of
disable as the second level of “off” for systemd units.
>
> Masking is a third level, less often used but quite powerful. But before
we look at masking, we need to understand why it exists: dependencies.
> To record unit masking, systemd uses the local system configuration files
in /etc/systemd/. It writes a link file pointing to /dev/null, the famous
“nothing” file in UNIX and Linux. So for instance, masking httpd.service
would result in this link:
> $ sudo systemctl mask httpd.service
> Created symlink from /etc/systemd/system/httpd.service to /dev/null.
> Note this is equivalent to running this command:
> $ sudo ln -s /dev/null /etc/systemd/system/httpd.service

Good luck.

W
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170728/3bb0bea0/attachment.html>


More information about the mythtv-users mailing list