[mythtv-users] Problem with MythWeb and mythtv-backend being ran from "mythtv" user
Steve Boyer
steveboyer85 at gmail.com
Sun Jul 30 12:09:58 UTC 2017
>
> >Good morning,
> >
> >I'm having an issue ...
>
> That "service" command is out of date - 16.04 uses systemd so you
> really should be using the systemd commands to run things. So that
> would be:
>
> systemctl start mythtv-backend
> systemctl stop mythtv-backend
> systemctl status mythtv-backend
>
> The old service command is now a script that calls systemd anyway, but
> it is better to use the right commands as I think that service can run
> things the wrong way if there is any misconfiguration.
>
>
Good to know. I am still retraining myself on commands/programs that are
depricated/obsoleted from time to time.
> If mythbackend is set up properly, even when it started from root as a
> service, it will be switching to be running under user mythtv. That
> is done by the systemd unit file that runs mythbackend:
>
> root at lith:/lib/systemd/system# cat 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
>
> The line "User=mythtv" means that systemd will be starting mythbackend
> under that user.
>
> A possible reason that mythweb is unable to talk to mythbackend is
> that it may be using the PC's external IP address to connect to. If
> so, then mythbackend may be starting up before the external IP address
> is up and will only be available on localhost. If that is the case,
> then stopping and restarting mythbackend using systemctl should result
> in it being able to bind the external IP address and mythweb should
> start working. The fix for that is available in several threads on
> this list, such as "Mythbackend may be starting too soon?".
>
>
>
I will definitely look into that as a possibility. The config files I've
seen seem to be pointing to localhost, while I know the mythtv-setup
process points to the local LAN IP.
Killing the backend from my user and then doing # systemctl start
mythtv-backend.service it connects in -- It is looking like this is the
culprit at the moment.
Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170730/b09cc8b1/attachment.html>
More information about the mythtv-users
mailing list