catalinii / minisatip

minisatip is an SATIP server for linux using local DVB-S2, DVB-C, DVB-T or ATSC cards
https://minisatip.org
331 stars 81 forks source link

RTSP error 22 - Multicast breaks stream #328

Closed netforceatg closed 7 years ago

netforceatg commented 8 years ago

Hi Guys, thanks for a great project!

I have a Tvheadend server, running version 4.1-2280~g47af3cd. This works great with a Digital Devices Cine DVB-S2 6.5 card. And a local instance of oscam running for decrypting.

Last week I added a Digibit R1 connected to a GT-Sat LNB, type GT-S3SCR4. I ran the stock firmware for a a few hours connected to Tvheadend and this worked. The Digibit R1 is connected with 1gbit to a Mikrotik CCR1009 router, that is connected to VMWare ESXI host(10Gbit) running Debian with TVHeadend on it.

I then upgraded the firmware of the Digibit to satip-axe project. However, I’m having big troubles with getting this to work stable. It seems I get the following error message that prevents it from working stable: “ satip: SAT>IP DVB-S Tuner #3 (192.168.2.16) - RTSP error -22 (Invalid argument) [8-200]

“ My problem is that it works about 1/5 of the times, I may have to try to start a stream form Tvheadend 5-10 times before it works, and it can randomly stop. With the Digital Devices DVB-S2 card it just works, but I am then limited to 2 tuners.

Over the last 3 days, I have tried changing almost all settings in the DVB input under TVheadend, and the 3 lastest version of of satip-axe(version 11, 12 and the current Alpha/Beta from june, version14), all with the same result. Tvheadend and their clients work, but extremely unstable.

I created a issue at the satip-axe project page: https://github.com/perexg/satip-axe/issues/74#issuecomment-254417784

After I isolated the minisatip5 server and the TVHeadend backend on a closed vlan/subnet streaming works as it should. And my understanding is that the stream breaks due to a bug related to multicast and minisatip.

A few notes: I have tried both minisatip and minisatip5 of the satip-axe firmware, same result. Currently running the following satip-axe config option: MINISATIP5_OPTS="-u 0:1-1420,1:0-1210,2:2-1680,3:3-2040"

Debug log: https://dl.dropboxusercontent.com/u/14615299/tvheadend-debuglog.txt https://dl.dropboxusercontent.com/u/14615299/tvheadend-debuglog-2.txt

Here are some links to a few config screenshots: https://dl.dropboxusercontent.com/u/14615299/satip-axe-webint.png https://dl.dropboxusercontent.com/u/14615299/tvheadend-2.png https://dl.dropboxusercontent.com/u/14615299/tvheadend.png

catalinii commented 8 years ago

Hi,

I suggest starting minisatip, tvh, try to tune 1 channel if it fails stop both and upload both logs.

Thanks

perexg commented 8 years ago

@catalanii: Check https://dl.dropboxusercontent.com/u/14615299/tvheadend-debuglog.txt , "httpc: 017F:" lines and hex dumps of the communication. There's a wrong multicast reply in the RTSP TCP stream:

2016-10-17 21:17:01.239 [  TRACE]:httpc: 017F: client flush 0
2016-10-17 21:17:01.239 [  TRACE]:httpc: 017F: RTSP/1.0 answer 'HTTP/1.1 200 OK' (rcseq: 1)
2016-10-17 21:17:01.239 [  TRACE]:httpc: 48 54 54 50 2F 31 2E 31 20 32 30 30 20 4F 4B 00 HTTP/1.1 200 OK.
2016-10-17 21:17:01.239 [  TRACE]:httpc: 0A 43 41 43 48 45 2D 43 4F 4E 54 52 4F 4C 3A 20 .CACHE-CONTROL: 
2016-10-17 21:17:01.239 [  TRACE]:httpc: 6D 61 78 2D 61 67 65 3D 31 38 30 30 0D 0A 44 41 max-age=1800..DA
2016-10-17 21:17:01.239 [  TRACE]:httpc: 54 45 3A 20 4D 6F 6E 2C 20 4F 63 74 20 31 37 20 TE: Mon, Oct 17 
2016-10-17 21:17:01.239 [  TRACE]:httpc: 31 39 3A 31 34 3A 33 31 20 32 30 31 36 20 47 4D 19:14:31 2016 GM
2016-10-17 21:17:01.239 [  TRACE]:httpc: 54 0D 0A 45 58 54 3A 0D 0A 4C 4F 43 41 54 49 4F T..EXT:..LOCATIO
2016-10-17 21:17:01.239 [  TRACE]:httpc: 4E 3A 20 68 74 74 70 3A 2F 2F 31 39 32 2E 31 36 N: http://192.16
2016-10-17 21:17:01.239 [  TRACE]:httpc: 38 2E 32 2E 31 36 3A 38 30 38 30 2F 64 65 73 63 8.2.16:8080/desc
2016-10-17 21:17:01.239 [  TRACE]:httpc: 2E 78 6D 6C 0D 0A 53 45 52 56 45 52 3A 20 4C 69 .xml..SERVER: Li
2016-10-17 21:17:01.239 [  TRACE]:httpc: 6E 75 78 2F 31 2E 30 20 55 50 6E 50 2F 31 2E 31 nux/1.0 UPnP/1.1
2016-10-17 21:17:01.239 [  TRACE]:httpc: 20 6D 69 6E 69 73 61 74 69 70 2F 30 2E 35 2E 35  minisatip/0.5.5
2016-10-17 21:17:01.239 [  TRACE]:httpc: 30 2D 61 78 65 31 30 32 0D 0A 53 54 3A 20 75 72 0-axe102..ST: ur
2016-10-17 21:17:01.239 [  TRACE]:httpc: 6E 3A 73 65 73 2D 63 6F 6D 3A 64 65 76 69 63 65 n:ses-com:device
2016-10-17 21:17:01.239 [  TRACE]:httpc: 3A 53 61 74 49 50 53 65 72 76 65 72 3A 31 0D 0A :SatIPServer:1..
2016-10-17 21:17:01.239 [  TRACE]:httpc: 55 53 4E 3A 20 75 75 69 64 3A 31 31 32 32 33 33 USN: uuid:112233
2016-10-17 21:17:01.239 [  TRACE]:httpc: 34 34 2D 39 39 39 39 2D 30 30 30 30 2D 62 37 61 44-9999-0000-b7a
2016-10-17 21:17:01.239 [  TRACE]:httpc: 65 2D 30 30 32 34 61 36 30 30 30 32 37 30 3A 3A e-0024a6000270::
2016-10-17 21:17:01.239 [  TRACE]:httpc: 75 72 6E 3A 73 65 73 2D 63 6F 6D 3A 64 65 76 69 urn:ses-com:devi
2016-10-17 21:17:01.239 [  TRACE]:httpc: 63 65 3A 53 61 74 49 50 53 65 72 76 65 72 3A 31 ce:SatIPServer:1
2016-10-17 21:17:01.239 [  TRACE]:httpc: 0D 0A 42 4F 4F 54 49 44 2E 55 50 4E 50 2E 4F 52 ..BOOTID.UPNP.OR
2016-10-17 21:17:01.239 [  TRACE]:httpc: 47 3A 20 31 0D 0A 43 4F 4E 46 49 47 49 44 2E 55 G: 1..CONFIGID.U
2016-10-17 21:17:01.239 [  TRACE]:httpc: 50 4E 50 2E 4F 52 47 3A 20 30 0D 0A 44 45 56 49 PNP.ORG: 0..DEVI
2016-10-17 21:17:01.239 [  TRACE]:httpc: 43 45 49 44 2E 53 45 53 2E 43 4F 4D 3A 20 31 00 CEID.SES.COM: 1.
2016-10-17 21:17:01.239 [  TRACE]:httpc: 0A 0D 0A                                        ...             

but the request was:

2016-10-17 21:17:01.212 [  TRACE]:httpc: 017F: sending RTSP/1.0 cmd
2016-10-17 21:17:01.212 [  TRACE]:httpc: 53 45 54 55 50 20 72 74 73 70 3A 2F 2F 31 39 32 SETUP rtsp://192
2016-10-17 21:17:01.212 [  TRACE]:httpc: 2E 31 36 38 2E 32 2E 31 36 2F 3F 73 72 63 3D 31 .168.2.16/?src=1
2016-10-17 21:17:01.212 [  TRACE]:httpc: 26 66 65 3D 34 26 66 72 65 71 3D 31 30 37 34 37 &fe=4&freq=10747
2016-10-17 21:17:01.212 [  TRACE]:httpc: 26 73 72 3D 32 35 30 30 30 26 6D 73 79 73 3D 64 &sr=25000&msys=d
2016-10-17 21:17:01.212 [  TRACE]:httpc: 76 62 73 26 6D 74 79 70 65 3D 71 70 73 6B 26 70 vbs&mtype=qpsk&p
2016-10-17 21:17:01.212 [  TRACE]:httpc: 6F 6C 3D 68 26 66 65 63 3D 33 34 26 72 6F 3D 30 ol=h&fec=34&ro=0
2016-10-17 21:17:01.212 [  TRACE]:httpc: 2E 33 35 20 52 54 53 50 2F 31 2E 30 0D 0A 54 72 .35 RTSP/1.0..Tr
2016-10-17 21:17:01.212 [  TRACE]:httpc: 61 6E 73 70 6F 72 74 3A 20 52 54 50 2F 41 56 50 ansport: RTP/AVP
2016-10-17 21:17:01.212 [  TRACE]:httpc: 3B 75 6E 69 63 61 73 74 3B 63 6C 69 65 6E 74 5F ;unicast;client_
2016-10-17 21:17:01.212 [  TRACE]:httpc: 70 6F 72 74 3D 35 30 35 37 38 2D 35 30 35 37 39 port=50578-50579
2016-10-17 21:17:01.212 [  TRACE]:httpc: 0D 0A 43 53 65 71 3A 20 31 0D 0A 0D 0A          ..CSeq: 1....   

It looks like that buffers (memory areas) are overwritten.

catalinii commented 8 years ago

Hi perexg,

yeah, I see the issue... is this problem reproductible for you as well ? If yes, can I get some logs for minisatip ? (with -l -l -l )

Thanks

perexg commented 8 years ago

I cannot reproduce this here, but @netforceatg has a complex network with many PnP devices, which seems to trigger this bug.

netforceatg commented 8 years ago

Hi,

I have started to use this in 'production' (home usage with several clients), it works great after I isolated the devices in seperate vlans.

If you would like me to do some more test please let me know catalinii, and I'll put them back in the subnet that provoked the multicast bugs. But please help me to explain how and what log \ details you would like.

Best Regards

catalinii commented 8 years ago

Hi,

please do, but I need the log from minisatip (with at least -3 l's).

Thanks

catalinii commented 7 years ago

Please reopen if this is still an issue with the latest version of satip-axe. Also please provide both tvh and minisatip debug logs.

Thanks