TVH server CRASH when network force scan called from SAT>IP client
1) Tvheadend sat>ip client on QNAP NAS
2) Tvheadend sat>ip server on Rpi3b+ 4.3-1282~g1c2a21399 with DVB-T tuner
3) various other sat>ip servers on other Rpi2s with DVB-T and DVB-S tuners
When I launch a DVB-T network force scan from the Tvheadend sat>ip client on the QNAP, the Tvheadend installation (2) on the Rpi3b+ immediately crashes:
Jun 20 17:57:19 openHABianPi tvheadend: mpegts: 626MHz in DVB-T Network - tuning on DiBcom 7000PC #1 : DVB-T #0 Jun 20 17:57:19 openHABianPi tvheadend: subscription: 0002: "SAT>IP" subscribing to mux "626MHz", weight: 6, adapter: "DiBcom 7000PC #1 : DVB-T #0", network: "DVB-T Network", service: "Raw PID Subscription", hostname="192.168.1.32" Jun 20 17:57:20 openHABianPi tvheadend: linuxdvb: Unhandled ERROR_BLOCK_COUNT scale: 0 Jun 20 17:57:24 openHABianPi systemd: tvheadend.service: Main process exited, code=killed, status=6/ABRT Jun 20 17:57:24 openHABianPi systemd: tvheadend.service: Unit entered failed state. Jun 20 17:57:24 openHABianPi systemd: tvheadend.service: Failed with result 'signal'.
All other installations work OK. Force scan launched directly from the web interface of the Rpi3b+ works OK.
The main difference with the Rpi3b+ may be that both LAN and WiFi are enabled, but Tvheadend appears to respond to the SAT>IP client on the NAS from the LAN IP address.
Updated by g siviero over 3 years ago
Edit: If in the SAT>IP Tvheadend client on the QNAP NAS I enable "RTP/AVP/TCP transport supported" on the TV adapter corresponding to the RpiB3+ the server does not crash.
So this crash error can be avoided by enabling this option, but I don't think that a client setting value should make the server crash anyway.