Bug #5357
SAT>IP client broken since version 1562 "service instance is bad"
0%
Description
With up-to-date build I saw my TV feed always frozen after a few seconds. I tracked the versions back and the issue was definitely invented in build 1562 (1560 is working fine).
My feed is a Digibit R1 receiver running the minisatip-axe firmware 201810211549. Transport is configured as RTP/AVP/TCP.
Tuning to any channel works for a few seconds, then breaking with the error message "service instance is bad, reason: Tuning failed". See a log below.
It also happened with unencrypted channels.
2018-11-27 16:36:29.914 mpegts: 10832.25H in Astra 19.2 - tuning on SAT>IP DVB-S Tuner #1 (10.32.6.100@TCP) 2018-11-27 16:36:29.914 capmt: OSCAM: Starting CAPMT server for service "RTL HD" on adapter 0 2018-11-27 16:36:29.914 subscription: 0001: "HTTP" subscribing on channel "RTL Television|RTL Austria|RTL HH SH", weight: 100, adapter: "SAT>IP DVB-S Tuner #1 (10.32.6.100@TCP)", network: "Astra 19.2", mux: "10832.25H", provider: "CBC", service: "RTL HD", profile="pass", hostname="10.0.6.3", client="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.85 Safari/537.36" 2018-11-27 16:36:30.934 TS: Astra 19.2/10832.25H/RTL HD: TELETEXT @ #32 Continuity counter error (total 1) 2018-11-27 16:36:34.935 satip: SAT>IP DVB-S Tuner #1 (10.32.6.100@TCP) - no data received, restarting RTSP 2018-11-27 16:36:35.914 subscription: 0001: service instance is bad, reason: Tuning failed 2018-11-27 16:36:35.915 mpegts: 10832.25H in Astra 19.2 - tuning on SAT>IP DVB-S Tuner #2 (10.32.6.100@TCP) 2018-11-27 16:36:35.915 capmt: OSCAM: Starting CAPMT server for service "RTL HD" on adapter 0 2018-11-27 16:36:35.915 subscription: 0001: "HTTP" subscribing on channel "RTL Television|RTL Austria|RTL HH SH", weight: 100, adapter: "SAT>IP DVB-S Tuner #2 (10.32.6.100@TCP)", network: "Astra 19.2", mux: "10832.25H", provider: "CBC", service: "RTL HD", profile="pass", hostname="10.0.6.3", client="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.85 Safari/537.36" 2018-11-27 16:36:40.957 satip: SAT>IP DVB-S Tuner #2 (10.32.6.100@TCP) - no data received, restarting RTSP 2018-11-27 16:36:41.914 subscription: 0001: service instance is bad, reason: Tuning failed 2018-11-27 16:36:41.915 mpegts: 10832.25H in Astra 19.2 - tuning on SAT>IP DVB-S Tuner #3 (10.32.6.100@TCP) 2018-11-27 16:36:41.915 capmt: OSCAM: Starting CAPMT server for service "RTL HD" on adapter 0 2018-11-27 16:36:41.915 subscription: 0001: "HTTP" subscribing on channel "RTL Television|RTL Austria|RTL HH SH", weight: 100, adapter: "SAT>IP DVB-S Tuner #3 (10.32.6.100@TCP)", network: "Astra 19.2", mux: "10832.25H", provider: "CBC", service: "RTL HD", profile="pass", hostname="10.0.6.3", client="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.85 Safari/537.36" 2018-11-27 16:36:46.958 satip: SAT>IP DVB-S Tuner #3 (10.32.6.100@TCP) - no data received, restarting RTSP 2018-11-27 16:36:47.915 subscription: 0001: service instance is bad, reason: Tuning failed 2018-11-27 16:36:47.916 mpegts: 10832.25H in Astra 19.2 - tuning on SAT>IP DVB-S Tuner #4 (10.32.6.100@TCP) 2018-11-27 16:36:47.916 capmt: OSCAM: Starting CAPMT server for service "RTL HD" on adapter 0 2018-11-27 16:36:47.917 subscription: 0001: "HTTP" subscribing on channel "RTL Television|RTL Austria|RTL HH SH", weight: 100, adapter: "SAT>IP DVB-S Tuner #4 (10.32.6.100@TCP)", network: "Astra 19.2", mux: "10832.25H", provider: "CBC", service: "RTL HD", profile="pass", hostname="10.0.6.3", client="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.85 Safari/537.36" 2018-11-27 16:36:52.952 satip: SAT>IP DVB-S Tuner #4 (10.32.6.100@TCP) - no data received, restarting RTSP 2018-11-27 16:36:53.915 subscription: 0001: service instance is bad, reason: Tuning failed
History
Updated by Pablo R. almost 6 years ago
Did you try v4.3-1566 ?
satip client: fix activity timestamp for TCP data transfer mode
Updated by Jaroslav Kysela almost 6 years ago
- Status changed from New to Invalid
Yes, it's already fixed in v4.3-1566-ge72b43156 (sorry).
Updated by Mark Clarkstone almost 6 years ago
- Subject changed from SAT>IP client broken since version 1652 "service instance is bad" to SAT>IP client broken since version 1562 "service instance is bad"
Updated by Marco Jakobs almost 6 years ago
Thanks, 1767 works fine! :-) Sorry for the false report.
Updated by Marco Jakobs almost 6 years ago
Marco Jakobs wrote:
Thanks, 1567 works fine! :-) Sorry for the false report.