[mythtv-users] culprit found? (was: Web Frontend stopped working yesterday)
Stephen Worthington
stephen_agent at jsw.gen.nz
Sat Jul 20 08:10:06 UTC 2019
On Fri, 19 Jul 2019 20:33:13 +0200, you wrote:
>On Fri, Jul 19 2019 at 13:54 -04, David Hampton wrote:
>> On Fri, 2019-07-19 at 18:34 +0200, Janusz S. Bie? wrote:
>>> On Fri, Jul 19 2019 at 11:59 -04, Jay Harbeston wrote:
>
>[...]
>
>>> If ps says the truth, there is only one backend running:
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> ps ax | grep mythbackend
>>> 1295 ? Ssl 3:04 /usr/bin/mythbackend --logpath
>>> /var/log/mythtv --logl
>>> 8222 pts/1 S+ 0:00 grep mythbackend
>>> --8<---------------cut here---------------end--------------->8---
>>>
>>> If nmap says the truth, the port 6543 is open and assigned to mythtv
>>> service:
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> nmap -p 6543 0.0.0.0
>>> Starting Nmap 7.70 ( https://nmap.org ) at 2019-07-19 18:21 CEST
>>> Nmap scan report for 0.0.0.0
>>> Host is up (0.00013s latency).
>>>
>>> PORT STATE SERVICE
>>> 6543/tcp open mythtv
>>> --8<---------------cut here---------------end--------------->8---
>>>
>>> If the message
>>>
>>> 0.0.0.0:6543 - ERROR 8: THE BOUND ADDRESS IS ALREADY IN USE
>>>
>>> is the true, then some other mythtv service (is there any?) is using
>>> it...
>>
>> Try the command: sudo netstat -tapn | grep 6543
>
>Thanks, I was not familiar with this invocation.
>
>
>> That will tell you what process pid/name has the port open.
>
>--8<---------------cut here---------------start------------->8---
> netstat -tapn | grep 6543
>
>tcp 0 0 0.0.0.0:6543 0.0.0.0:* LISTEN 1295/mythbackend
>tcp6 0 0 :::6543 :::* LISTEN 1295/mythbackend
>
>ps ax | grep mythbackend
> 1295 ? Ssl 6:33 /usr/bin/mythbackend --logpath /var/log/mythtv --loglevel crit
>13947 pts/1 S+ 0:00 grep mythbackend
>--8<---------------cut here---------------end--------------->8---
>
>I just realized that I have both mythbackend and mythtv-backend and my system
>toggles between mythbackend and mythtv-backend in a semi-random way
>without my intervention. The change can be causes e.g. by some package
>update or reboot.
>
>When mythbackend is running then WebFrontend seems to work.
>
>Looks like mythbackend is started by systemd, and mythtv-backend by
>init. Now the question is how to get rid of mythtv-backend.
>
>Best regards
>
>Janusz
You can either disable the /etc/init.d script, or you can rename your
mythbackend.service file to mythtv-backend.service, in which case
systemd will ignore the init script in favour of the proper systemd
unit. To disable the init script, I think this is the right way to do
it:
update-rc.d mythtv-backend disable
More information about the mythtv-users
mailing list