rtspsrc ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not read from resource

Diego Buffa diego.buffa at gmail.com
Mon Oct 24 10:29:01 UTC 2016


On Mon, Oct 24, 2016 at 9:05 AM, Sebastian Dröge <sebastian at centricular.com>
wrote:

> So it was running for a while? That would indeed mean that the problem
> is with the last packets you provided.
>
> The next step would then be to dive into the code and check why it
> considers the packet as invalid, what is confusing it. And if the
> packet is indeed broken in one way or another.
>
> Can you provide again that the last packet that it successfully parses
> and the one where it fails? Which might not be the last one from your
> pcap capture, but an earlier one.
>
>
Yes Sebastian, it run for a while.
I guess the last good packet was the one of 1055 received at
1:53:05.895046809

1:53:05.893728142   414   0x77c230 DEBUG                rtspsrc
gstrtspsrc.c:4431:gst_rtspsrc_handle_data:<rtspsrc0> pushing data of size
1446 on channel 0
1:53:05.894069476   414   0x77c230 DEBUG                rtspsrc
gstrtspsrc.c:4561:gst_rtspsrc_loop_interleaved:<rtspsrc0> doing receive
with timeout 114 seconds, 991176 usec
1:53:05.894463809   414   0x77c230 DEBUG                rtspsrc
gstrtspsrc.c:4571:gst_rtspsrc_loop_interleaved:<rtspsrc0> we received a
server message
1:53:05.894605809   414   0x77c230 DEBUG                rtspsrc
gstrtspsrc.c:4607:gst_rtspsrc_loop_interleaved:<rtspsrc0> got data message
1:53:05.894743809   414   0x77c230 DEBUG                rtspsrc
gstrtspsrc.c:4431:gst_rtspsrc_handle_data:<rtspsrc0> pushing data of size
1055 on channel 0
1:53:05.895046809   414   0x77c230 DEBUG                rtspsrc
gstrtspsrc.c:4561:gst_rtspsrc_loop_interleaved:<rtspsrc0> doing receive
with timeout 114 seconds, 990192 usec
1:53:06.151676476   414   0x77c230 WARN                 rtspsrc
gstrtspsrc.c:4641:gst_rtspsrc_loop_interleaved:<rtspsrc0> error: Could not
receive message. (Parse error)
ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not
read from resource.

Anyway I cannot find a packet of size 1055 in my pcap file while I see the
previous ones of 1446 (end of pcap file attached).
Is there better way to identify the last good packet and  the bad one than
looking at the size?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20161024/23c555f4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: end_pcap
Type: application/octet-stream
Size: 10273 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20161024/23c555f4/attachment.obj>


More information about the gstreamer-devel mailing list