Project

General

Profile

Bug #5348

SATIP client: constant reconnection breaks satip client working until tvh restart

Added by Pablo R. almost 6 years ago. Updated almost 6 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
Jaroslav Kysela
Category:
SAT>IP
Target version:
-
Start date:
2018-11-25
Due date:
% Done:

100%

Estimated time:
Found in version:
4.3-1557
Affected Versions:

Description

Attached files (--trace satip)

--> satip.txt; log where the problem ocurrs, cant longer connect on adapter to the satip server since 12:05:16
--> satip2.txt; log after tvh restart (now works fine)

To reproduce this I have cut the satip server's network cable (physically) during the following period;
12:05:16 - satip server network cable cut
12:05:52 - satip server network cable reconnection

After reconnecting cable, you can not connect to the server until you reboot tvheadend.

Important: During the "fall" period, client keeps reconnecting multiple times.

Files

satip.txt (84.7 KB) satip.txt Pablo R., 2018-11-25 12:13
satip2.txt (56 KB) satip2.txt Pablo R., 2018-11-25 12:13
dumpreal.pcapng (11.5 KB) dumpreal.pcapng Pablo R., 2018-11-25 21:08
5501.pcapng (25.5 KB) 5501.pcapng Pablo R., 2018-11-25 21:37
38690.pcapng (1.22 MB) 38690.pcapng Pablo R., 2018-11-25 21:37
38691.pcapng (1.96 KB) 38691.pcapng Pablo R., 2018-11-25 21:37
5500.pcapng (22.7 MB) 5500.pcapng Pablo R., 2018-11-25 21:37
554 5500 5501.pcapng (22.7 MB) 554 5500 5501.pcapng Pablo R., 2018-11-25 21:52

History

#1

Updated by Jaroslav Kysela almost 6 years ago

Could you capture the RTSP communication using wireshart/tcpdump ? (TCP port 554 - decode TCP stream in wireshark)

#2

Updated by Pablo R. almost 6 years ago

Dump attached, the first time it works, then I disconnect the network cable (there seems to be no network activity in that period) and when the network comes back it starts with the reconnection without stopping (and no streaming)...

Is the dump correct?

I'm not very familiar with wireshark

#3

Updated by Pablo R. almost 6 years ago

Note; as I see in minisatip the connection arrives, in fact the channel is selected, but it does not seem that tvheadend receives it (it is strange).

P.S.: I can reproduce also this issue with my satip server Triax TSS 400 with a cable disconnection but it is easier for me to do it with minisatip by way of tests

#4

Updated by Jaroslav Kysela almost 6 years ago

Ok, so tvh restores the connection to the satip server, but the new MPEG-TS data are not visible to tvh? Correct? So the bandwidth in the status tab is zero?

#5

Updated by Jaroslav Kysela almost 6 years ago

Could you try to use TCP data transfer mode? It appears like an UDP data transfer issue.

#6

Updated by Pablo R. almost 6 years ago

Jaroslav Kysela wrote:

Ok, so tvh restores the connection to the satip server, but the new MPEG-TS data are not visible to tvh? Correct? So the bandwidth in the status tab is zero?

Yes, it is at 0... and then streaming restarts again and again

Jaroslav Kysela wrote:

Could you try to use TCP data transfer mode? It appears like an UDP data transfer issue.

Im gonna try

#7

Updated by Jaroslav Kysela almost 6 years ago

Anyway, if TCP data transfer mode works, it would be good to analyze which UDP ports are used on the tvh side (use wireshark and grab UDP packets from the satip server with the RTSP communication to analyze what's going on).

#8

Updated by Pablo R. almost 6 years ago

For TCP it works properly on the second reconnection after reconnecting the network cable.

Is some kind of solution for UDP possible?

#9

Updated by Jaroslav Kysela almost 6 years ago

Show the another dump like I described before. So the filter should be like 'ip host SATIP_IP_ADDRESS and (udp or tcp port 554)'.

#10

Updated by Pablo R. almost 6 years ago

For this transfers (from the previous wireshark dump):

RTP/AVP;unicast;destination=192.168.2.66;source=192.168.2.89;client_port=38690-38691;server_port=5500-5501

I grabbed ports 38690, 38691, 5500 and 5501 UDP data.

#11

Updated by Pablo R. almost 6 years ago

Tell me if it is correct, if you need --trace satip from tvheadend at the same time or anything.

To consider for the size of the files in that period there were TS packages from the SATIP server.

#12

Updated by Jaroslav Kysela almost 6 years ago

Please, don't split the data. I need to see interleaved (all) data together. Please, use this filter in wireshark:

tcp.port == 554 or udp.port == 5500 or udp.port  == 5501
#13

Updated by Pablo R. almost 6 years ago

Jaroslav Kysela wrote:

Please, don't split the data. I need to see interleaved (all) data together. Please, use this filter in wireshark:

[...]

#14

Updated by Jaroslav Kysela almost 6 years ago

v4.3-1562-g0d101eb91

#15

Updated by Pablo R. almost 6 years ago

Working. Thanks! You are a boss :) (/)

#16

Updated by Jaroslav Kysela almost 6 years ago

Fixed in v4.3-1562-g0d101eb91 .

#17

Updated by Pablo R. almost 6 years ago

@Jaroslav I've noticed that although UDP mode now works properly, TCP mode is broken. Tvheadend gives RTSP errors constantly and stream restarts on loop.

2018-11-26 19:23:02.078 subscription: 00C1: "HTTP" subscribing on channel "SCT", weight: 100, adapter: "SAT>IP DVB-S Tuner #1 (192.168.2.128@TCP)", network: "HOTBIRD", mux: "11727V", provider: "xxx", service: "xxx", profile="pass", hostname="192.168.2.147", client="VLC/3.0.4 LibVLC/3.0.4" 
2018-11-26 19:23:07.082 satip: SAT>IP DVB-S Tuner #1 (192.168.2.128@TCP) - no data received, restarting RTSP
2018-11-26 19:23:08.077 subscription: 00C1: service instance is bad, reason: Tuning failed

Even tunning failed appears when channel is perfectly seen (before autorestart)

#18

Updated by Jaroslav Kysela almost 6 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Applied in changeset commit:tvheadend|e72b431564c860d5fc711779856dd7f61ed4f568.

Also available in: Atom PDF