Hi BoxSon,
I noticed the same error and can confirm that the CPU load first increases to 100%, then the process crashes and the disconnect occurs. After that the connection is automatically established, as above in your syslog.
After struggling with that problem over the past months I did some research and can now narrow down where the problem is. However, I don't have the ability to write a patch...
What I can say, is that the bug was built into the commit onJanuary 4, 2018.
So all versions before January 4, 2018 work, all versions after have this bug.
And indeed, on January 4, 2018 the following files were modified:cclient, cwc, cccam...
To try it out quickly, you can simply run the following docker command (some path modifications are required), enter a newcamd server, observe the errors:
with thelast working version 133 (Dec 3, 2017):
docker create \
--name=tvheadend \
--net=bridge \
-v /opt/tvh/config:/config \
-v /opt/tvh/rec:/recordings \
-e PGID=1000 -e PUID=1000 \
-p 9981:9981 \
-p 9982:9982 \
--device=/dev/dvb \
--device=/dev/dri
linuxserver/tvheadend:133
The version 134 or above with the
bug:
docker create \
--name=tvheadend \
--net=bridge \
-v /opt/tvh/config:/config \
-v /opt/tvh/rec:/recordings \
-e PGID=1000 -e PUID=1000 \
-p 9981:9981 \
-p 9982:9982 \
--device=/dev/dvb \
--device=/dev/dri
linuxserver/tvheadend:134
More details how to run: https://hub.docker.com/r/linuxserver/tvheadend/
Best regards
Master-Lee
