[mythtv-users] Web Frontend stopped working yesterday

[Janusz S. Bień]

Hi!

That's happened again after reboot to Windows and back (no other possibly
relevant action on my side).

On Fri, Mar 08 2019 at  8:17 +01, Janusz S. Bień wrote:

[...]

> Frontend works, Web frontend does not:
>
> Firefox can’t establish a connection to the server at localhost:6544.

On Sat, Mar 09 2019 at  6:48 +00, Ian Cameron wrote:

[...]

> Some of these may seem obvious, but off the top of my head, I would:
>

> Check IP and port number configurations in mythtv-setup -

"Port" and "Status port" have their default values 6543 and 6544.  I
changed IP from 127.0.0.1 to the assigned IP as I intend now to use more
than one backend.

> stop the back-end first and start again after running mythtv-setup
> using systemctl.

Is the output of 'systemctl status mythtv-backend' of any use? The backend
is running, the frontend works and the output is

--8<---------------cut here---------------start------------->8---
systemctl status mythtv-backend
● mythtv-backend.service - LSB: Start/Stop the MythTV server.
   Loaded: loaded (/etc/init.d/mythtv-backend; generated)
   Active: inactive (dead) since Fri 2019-07-12 06:48:05 CEST; 17min ago
--8<---------------cut here---------------end--------------->8---

Before starting today's experiments the output was

--8<---------------cut here---------------start------------->8---
systemctl status mythtv-backend
● mythtv-backend.service - LSB: Start/Stop the MythTV server.
   Loaded: loaded (/etc/init.d/mythtv-backend; generated)
   Active: active (exited) since Thu 2019-07-11 21:24:43 CEST; 9h ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1218 ExecStart=/etc/init.d/mythtv-backend start (code=exited, status=0/SUCCESS)

Jul 11 21:24:49 VivoPC-D8 mythbackend[1676]: mythbackend[1676]: I CoreContext serverpool.cpp:415 (listen) Listening on TCP [::]:6554
Jul 11 21:24:49 VivoPC-D8 mythbackend[1676]: mythbackend[1676]: I CoreContext serverpool.cpp:415 (listen) Listening on TCP 0.0.0.0:6549
Jul 11 21:24:49 VivoPC-D8 mythbackend[1676]: mythbackend[1676]: I CoreContext serverpool.cpp:415 (listen) Listening on TCP [::]:6549
Jul 11 21:24:52 VivoPC-D8 mythbackend[1676]: mythbackend[1676]: I Scheduler scheduler.cpp:2357 (HandleReschedule) Reschedule req…dulerInit
Jul 11 21:24:53 VivoPC-D8 mythbackend[1676]: mythbackend[1676]: I Scheduler scheduler.cpp:2473 (HandleReschedule) Scheduled 0 it….01 place
Jul 11 21:24:53 VivoPC-D8 mythbackend[1676]: mythbackend[1676]: I Scheduler scheduler.cpp:2540 (HandleRunSchedulerStartup) Sched…p by USER
Jul 11 21:24:56 VivoPC-D8 mythbackend[1676]: mythbackend[1676]: I CoreContext main_helpers.cpp:698 (run_backend) Main::Registeri…Extension
Jul 11 21:24:56 VivoPC-D8 mythbackend[1676]: mythbackend[1676]: E CoreContext serverpool.cpp:428 (listen) Failed listening on TC…dy in use
Jul 11 21:24:56 VivoPC-D8 mythbackend[1676]: mythbackend[1676]: C CoreContext main_helpers.cpp:713 (run_backend) Backend exiting…on error.
Jul 11 21:24:56 VivoPC-D8 mythbackend[1676]: mythbackend[1676]: I CoreContext bonjourregister.cpp:28 (~BonjourRegister) Bonjour:… '' on ''
--8<---------------cut here---------------end--------------->8---

Please note [::]:6554. The IP6 address the culprit of my problems?

> Check that only one instance of the back-end is running at a given
> time via ps -ef output information.

--8<---------------cut here---------------start------------->8---
ps -ef| grep mythtv
mythtv    1219     1  3 Jul11 ?        00:22:21 /usr/bin/mythbackend --logpath /var/log/mythtv --loglevel crit
root     21070 18102  0 07:09 pts/1    00:00:00 grep mythtv
--8<---------------cut here---------------end--------------->8---

> Check that nothing else is using port 6544 via netstat -anp output information.


--8<---------------cut here---------------start------------->8---
netstat -anp | grep 6544
unix  3      [ ]         STREAM     CONNECTED     36544    2192/dbus-daemon     
--8<---------------cut here---------------end--------------->8---

The backend is not listening at 6444...

--8<---------------cut here---------------start------------->8---
netstat -anp 
Active Internet connections (servers and established)
...
tcp        0      0 0.0.0.0:6543            0.0.0.0:*               LISTEN      1219/mythbackend    
...
tcp        0      0 192.168.0.181:45244     192.168.0.195:65001     ESTABLISHED 1219/mythbackend    
...
tcp6       0      0 :::6543                 :::*                    LISTEN      1219/mythbackend    
...
--8<---------------cut here---------------end--------------->8---

How to interpret this output?


> Enable logging on the back-end and start looking through the logs
> generated to see if the cause of the problem can be found there.

Which loglevel do you suggest?

Best regards

Janusz

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