[mythtv-users] I broke my mythTV, help!

[Stephen Worthington]

On Tue, 6 Nov 2018 19:32:14 -0800, you wrote:

>I put the mythbackend.system back in place since removing it did not improve anything, and the system was working with both
>files in place before I swapped my /home raid.
>
>
>$ sudo systemctl cat mythbackend
>
># /etc/systemd/system/mythbackend.service
>[Unit]
>Description=MythTV backend service
># The following line will cause mythbackend to be terminated if the database dies.
># If you do not want this then use a weaker binding such as "Requires" or "Wants".
>BindsTo=mysql.service
>Wants=network-online.target
>After=mysql.service network-online.target
>
># Persistently named adapters
># Needs a systemd tag added to your udev persistent naming rules
>#Requires=dev-dvb-adapter0-frontend0.device
>#After=dev-dvb-adapter0-frontend0.device
>
>[Service]
># Wait for a dbus notification from mythbackend before starting other services
># This is enabled by default 0.28 onwards (may be in 0.27 as well)
># To disable this change type to simple
>Type=notify
>NotifyAccess=main
>
># Allow core dumps
># The core resource limit on the user specified below can reduce what
># is specified here. So it needs to be set as well.
>LimitCORE=infinity
>
>User=mythtv
>
>StandardOutput=null
>StandardError=journal
>
>ExecStart=/full/path/to/mythbackend $MYTHBACKEND_ARGS
>
>[Install]
>WantedBy=multi-user.target
>
># /etc/systemd/system/mythbackend.service.d/environment.conf
>[Service]
># Command line arguments to be passed by systemd to mythbackend on startup.
># This variable must be defined or the service will not start.
>Environment="MYTHBACKEND_ARGS=--logpath=/home/roger/logs --verbose=none,dvbsicache,tempdebug:debug"
>
># Environment variables for the mythbackend program itself
>Environment=MYTHCONFDIR=/etc/mythtv
>
>
>
>
>
>$ sudo systemctl cat mythtv-backend
># /lib/systemd/system/mythtv-backend.service
>[Unit]
>Description=MythTV Backend
>Documentation=https://www.mythtv.org/wiki/Mythbackend
>After=mysql.service network.target
> 
>[Service]
>User=mythtv
>EnvironmentFile=-/etc/mythtv/additional.args
>ExecStart=/usr/bin/mythbackend --quiet --syslog local7 $ADDITIONAL_ARGS
>StartLimitBurst=10
>StartLimitInterval=10m
>Restart=on-failure
>RestartSec=1
> 
>[Install]
>WantedBy=multi-user.target
>

I do not think you have said yet what distro you are running.  If it
is Ubuntu, then you definitely do not want the
/lib/systemd/system/mythbackend.service file - you must have created
it yourself, as it is not part of any Ubuntu package.  And the
mythbackend.service file will not ever work as it currently is, since
its ExecStart line is invalid - it does not have the correct path to
find the mythbackend executable file.  So if you are running Ubuntu, I
would recommend that you delete
/lib/systemd/system/mythbackend.service.  It is a red herring.

In Ubuntu from 16.04+, mythbackend is run by systemd from the
/lib/systemd/system/mythtv-backend.service file.  To find out what
that file is doing, use this command:

sudo systemctl status mythtv-backend

To make sure that mythtv-backend.service is enabled and that it has
tried to start mythbackend, do these commands:

sudo systemctl daemon-reload
sudo systemctl enable mythtv-backend
sudo systemctl start mythtv-backend

Those commands tell systemd to 1) re-read all its configuration files,
2) set up the mythtv-backend.service unit so that it will
automatically be started at boot time, and 3) start the
mythtv-backend.service unit.  Which hopefully will then attempt to
start mythbackend.

Then repeat this command:

sudo systemctl status mythtv-backend

and you can also take a look at /var/log/mythtv/mythbackend.log to see
more detail about mythbackend starting up or not.

To check if there are any override config files installed for
mythtv-backend.service, it would be helpful to see the output of:

sudo systemctl cat mythtv-backend