Project

General

Profile

Bug #5132

TVH server CRASH when network force scan called from SAT>IP client

Added by g siviero over 2 years ago. Updated over 2 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
Crashes
Target version:
-
Start date:
2018-06-21
Due date:
% Done:

0%

Estimated time:
Found in version:
4.3-1282~g1c2a21399
Affected Versions:

Description

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[18209]: mpegts: 626MHz in DVB-T Network - tuning on DiBcom 7000PC #1 : DVB-T #0
Jun 20 17:57:19 openHABianPi tvheadend[18209]: 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[18209]: linuxdvb: Unhandled ERROR_BLOCK_COUNT scale: 0
Jun 20 17:57:24 openHABianPi systemd[1]: tvheadend.service: Main process exited, code=killed, status=6/ABRT
Jun 20 17:57:24 openHABianPi systemd[1]: tvheadend.service: Unit entered failed state.
Jun 20 17:57:24 openHABianPi systemd[1]: 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.


Files

tvheadend_syslog.log (737 Bytes) tvheadend_syslog.log syslog g siviero, 2018-06-21 09:25
tvheadend.log (28.3 KB) tvheadend.log trace g siviero, 2018-06-21 09:25
gdb.txt (6.63 KB) gdb.txt g siviero, 2018-06-21 21:32

History

#1

Updated by g siviero over 2 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.

#3

Updated by g siviero over 2 years ago

Please find attached a stack trace obtained with gdb.

#4

Updated by Jaroslav Kysela over 2 years ago

Fixed in v4.3-1287-g65c2ebb60.

#5

Updated by Jaroslav Kysela over 2 years ago

  • Status changed from New to Fixed

Also available in: Atom PDF