[mythtv-users] No live tv and not recording
Klaus Becker
colonius at free.fr
Sun Mar 18 21:17:50 UTC 2018
Le dimanche 18 mars 2018, 18:40:56 CET Stephen Worthington a écrit :
> On Sun, 18 Mar 2018 11:45:39 +0100, you wrote:
> >Le dimanche 18 mars 2018, 11:07:22 CET Mark Perkins a écrit :
> >> On 18 March 2018 6:55:12 pm Klaus Becker <colonius at free.fr> wrote:
> >
> >> Le samedi 17 mars 2018, 23:04:17 CET Mark Perkins a écrit :
> >.....
> >
> >> That shows an instance currently running. I would shutdown all backends,
> >
> >> confirm that by:
> > ps aux | grep myth
> >
> >> netstat -peanut | grep 6543
> >
> >I did it.
> >
> >> Then restart the backend / try to play LiveTV / recording / etc /
> >> whatever
> >> is still causing problems then check the backend log file for errors (and
> >> post to the list so others can check too).
> >
> >$ mythbackend --loglevel debug -v record-loglevel
>
> [snip]
>
> >2018-03-18 11:38:49.681508 E Failed listening on TCP 127.0.0.1:6544 -
> >Error 8: The bound address is already in use
> >2018-03-18 11:38:49.681524 E MediaServer: HttpServer Create Error
> >2018-03-18 11:38:49.682195 E Failed listening on TCP 127.0.0.1:6543 -
> >Error 8: The bound address is already in use
>
> Mythbackend is still unable to bind its ports, which means something
> is broken. If another copy of mythbackend is not running, it must be
> some other problem, such as permissions.
>
> How are you starting and stopping mythbackend? I have just tried
> installing Debian Testing with MythTV packages from
> deb-multimedia.org, and it seems that the packages for MythTV are
> still using /etc/init.d/mythtv-backend to control the backend. That
> is unreliable in Debian now, as Debian has changed to use systemd and
> systemd does not properly handle /etc/init.d files. In particular, it
> does not recognise that things started and stopped using /etc/init.d
> files have actually started or stopped - you always have to verify
> that the start or stop actually worked. If it did not work, the
> status (started or stopped) that systemd thinks it has for the program
> is out of sync with reality.
>
> To start mythbackend:
>
> systemctl start mythtv-backend
>
> To stop mythbackend:
>
> systemctl stop mythtv-backend
>
> If you just run mythbackend manually from your normal user prompt, it
> will be run from that user. But to work properly, it must be run from
> the /etc/init.d script via systemd. When run that way, it is run as a
> daemon and started as user root. After it is started it has its user
> changed to mythtv. Then it will be able to operate properly - running
> under your user will likely not give it the right permissions.
>
> However, on my Debian Testing setup, the user mythtv was not created
> automatically when I installed the MythTV packages, so if that also
> does not happen in Debian Sid, mythbackend will still not work
> correctly for you with the above commands. If I have enough time
> tomorrow, I will try creating a mythtv user and its .mythtv directory
> and .mythtv/config.xml file, and see if that helps. Along with the
> mythtv user, the mythtv group needs to be created, and all users who
> run mythtv need to be added to the mythtv group. And I also need to
> find out how MythTV expects to create logs when running as a daemon,
> as the /var/log/mythtv directory is not created either. But I am
> expecting my new Ethernet switch to arrive on the courier tomorrow or
> the day after, so if it comes tomorrow, I may not have much spare time
> to look at the Debian setup until I get that installed properly.
>
> Ideally, mythbackend should be run using a proper systemd unit file
> mythtv-backend.service which would be put in the /lib/systemd/system
> or /etc/systemd/system directory. Ubuntu does it that way now, but
> the way mythbackend gets run in Ubuntu is not quite the same as how it
> is run in Debian, so I need to carefully read through the
> /etc/init.d/mythtv-backend script to see what needs to be put in the
> Debian unit file and what the differences are between Debian and
> Ubuntu.
Hi Stephen and everybody,
There is indeed a problem with group mythtv.
Christian Marillat, the maintainer of the MythTV packages on deb-
multimedia.org, told me that his scripts don't create a group "mythtv".
But this group exists after installation on Debian, but I had to add manually
user "klaus" to the group "mythtv".
As mythtv did not work, I did "apt purge mythtv*" to rebegin everything from
the scratch. But I only could reinstall mythtv after deleting the group
"mythtv", as Christian told me. Otherwise installation was impossible.
Copy for Christian, he will tell us if I am wrong.
There also is a problem with "mythtv-status". It was not easy to install it,
finally I succeeded but I don't remember how.
So I reinstalled mythtv entirely and I added user "klaus" to the group
"mythtv". But it still does not work.
# mythtv-status --verbose
Today: 20180318
Tomorrow: 20180319
Considering: One Liners
Going to process: One Liners
Considering: Status
Going to process: Status
Loaded XML from localhost
Considering: Encoders
Going to process: Encoders
Considering: Encoders
Going to process: Encoders
Considering: Encoders
Going to process: Encoders
We have the correct protocol version for Encoders
Considering: Recording Now
Going to process: Recording Now
Considering: Scheduled Recordings
Going to process: Scheduled Recordings
Considering: Schedule Conflicts
Going to process: Schedule Conflicts
No backends found. Please copy config.xml from a working MythTV installation
to /root/.mythtv.
Compilation failed in require at /usr/bin/mythtv-status line 771.
Considering: Shows due to Auto Expire
Considering: Total Disk Space
Going to process: Total Disk Space
Considering: Total Disk Space
Going to process: Total Disk Space
We have the correct protocol version for Total Disk Space
We have the correct xml version for Total Disk Space
Unable to find any value for drive_total_used while at Total Disk Space,
marked as optional, skipping block.
Considering: Total Disk Space
Going to process: Total Disk Space
We have the correct protocol version for Total Disk Space
Considering: Disk Space
Going to process: Disk Space
We have the correct protocol version for Disk Space
Considering: Next Recording In
Going to process: Next Recording In
Considering: Guide Data
Going to process: Guide Data
Considering: Guide Data
Going to process: Guide Data
MythTV status for localhost
===========================
Status...........: 2018-03-18 22:13:11
Total Disk Space.: Total space is 7.1 TB, with 1,630.9 GB used (22.4%)
Next Recording In: Never
Schedule Conflicts:
Unable to access MythTV Perl API. Try with --verbose to find out why.
Disk Space:
Total space for group 1 is 7.1 TB, with 1,630.9 GB used (22.4%)
Are there people here who use MythTV under Debian and who can tell us if it
works?
Bye
Klaus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20180318/c936ff6b/attachment-0001.html>
More information about the mythtv-users
mailing list