Tvheadend

If a container runs correctly on platform A, and doesn't run correctly on platform B, then it would point to platform B being the issue.

I'm afraid I don't open .rtf files from unknown sources, if you attached as a text file it would be more conducive to being read.

Yes sure platform B is the issue. But what on platform B. The new kernel?
here the log in .txt

thats the application saying that there are continuity issues, you might look at what is happening on the host networking, and possibly take a wireshark trace to see if packets are being dropped somewhere.

Add some network optimisations
The buffer size in the /etc/sysctl.conf

net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.ipv4.udp_mem = 8388608 12582912 16777216
net.ipv4.tcp_rmem = 4096 87380 8388608
net.ipv4.tcp_wmem = 4096 65536 8388608
net.core.wmem_default = 16777216
net.core.rmem_default = 16777216
net.ipv4.tcp_tw_reuse = 1

also can disable firewall

After upgrading the container to bullseye the issue still persists, but there are much less errors. It is nearly possible to watch tv (with some lag).
In the standard log I get only the continuity errors. Which subsystem do I need to log? and witch of these subsystems do I need to trace?

Same problem here. LXC Container in Promox 7 and Kernel version great equal 5.4.157 cannot host tvheadend.
Tons of continuity errors make the server practically useless.
People reported when performing an inplace upgrade from Promox 6 to 7, they are having (sometimes) no problems. Could be that they are still using an older kernel that 5.4.157.

I also tried with a VM under Promox. This is working better and test recordings were fine. I notices though that after about 20-30 minutes life tV, the video stalls for about 15 seconds.

It looks to me that it is definitely a promox 7 problem and not tvheadend fault.

Hi,

I've seen that tvheadend continues to open new tasks. After some time there are so many tasks to fill up the ram and tvheadend reports continuity errors.