[mythtv-users] Web Frontend stopped working yesterday

[Janusz S. Bień]

On Fri, Jul 19 2019 at  9:18 -05, Bill Meek wrote:

[...]

> In the logs I could find in this thread, a 2nd instance of mythbackend was started:
>
>     ... Error 8: The bound address is already in use

Multiple instances of mythbackend seem an independent problem for me.

>
> Make sure all instances are stopped: sudo systemctl stop mythbackend and then ps ax | grep mythbackend
> to verify that no others are running, kill as required.

Immediately after a reboot I have

--8<---------------cut here---------------start------------->8---
ps ax | grep mythbackend
 1675 ?        Ssl    0:00 /usr/bin/mythbackend --daemon --pidfile /var/run/mythtv/mythbackend.pid --syslog local6 --verbose http:debug,up
 2648 pts/0    S+     0:00 grep mythbackend
--8<---------------cut here---------------end--------------->8---



>
> It appears that you're using /etc/init.d/mythtv-backend, and systemd starts it,
> you can modify the line in that file to get additional HTTP logging at startup
> by editing the line that starts mythbackend there.

The mythbackend process uses the arguments specified in /etc/default/mythtv-backend.

>
> Other info shows a loglevel of crit, change that to general otherwise most logs
> would be lost.

I also noticed it and I have no idea when and how the process with the
loglevel of crit was started.

>
> Use the logging options above that Stephen suggested, e.g. --verbose http:debug.

Done, as you can see above.

>
> Once setup, start the backend again: sudo systemctl start
> mythtv-backend,

I skipped this step because after the reboot the backend is definitely
running (confirmed by systemctl status mythtv-backend)

> attempt to connect to WebFrontend from you favorite browser and put
> the complete log for that run in a pastebin. Post the pastebin link
> here.

http://paste.debian.net/1092348/

> Please be sure to mention the time that the attempt to connect to
> WebFrontend was made so it can be matched with log entries.

An attempt to connect to http://localhost:6544/ was done at 17-13-53 but
left no trace in the log. Actually I expected this: the problem is that
the port 6544 for some reasons is not opened by the backend.

I'm looking forward to your comments.

Best regards

Janusz

-- 
             ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien