Hello, sorry to disturb you
Hardware Platform: x86 dGPU
GPU: Tesla T4
NVIDIA Driver Version: 590.48.01
Operating System: Ubuntu 24.04.4 LTS
DeepStream Version: 9.0 and 9.1
Application: Python / GStreamer
I configured nvmultiurisrcbin with:
rtsp-reconnect-interval=10
rtsp-reconnect-attempts=-1
When an RTSP source disconnects, nvmultiurisrcbin does not reconnect.
The application bus also does not receive the expected warning:
No data from source since last ... Trying reconnection
After enabling GStreamer debug logs, only the underlying rtspsrc
disconnection can be seen:
WARNING from src: Could not read from resource.
Debug info: ../gst/rtsp/gstrtspsrc.c(5993):
gst_rtspsrc_loop_interleaved ():
/GstPipeline:multi-rtsp-pipeline/GstDsNvMultiUriBin:src/
GstBin:src_creator/GstDsNvUriSrcBin:dsnvurisrcbin0/
GstRTSPSrc:src:
The server closed the connection.
However, GstDsNvUriSrcBin does not print “No data from source since
last”, “Trying reconnection”, or “Resetting source”.
Test results on the same x86 server:
| Environment / component | Result |
|---|---|
| DS 9.0 standalone nvurisrcbin | Works |
| DS 9.0 nvmultiurisrcbin with static uri-list | Fails |
| DS 9.0 nvmultiurisrcbin with REST-added source | Fails |
| DS 9.1 nvmultiurisrcbin | Fails |
| DS 7.1 x86 nvmultiurisrcbin | Works |
The same RTSP source and the same reconnect properties were used in
these tests.
This does not appear to be specific to REST dynamic source creation,
because static uri-list sources also fail on DS 9.0.
It appears that the internal GstDsNvUriSrcBin created by
nvmultiurisrcbin does not start its reconnect monitoring on
DeepStream 9.0 and 9.1 x86, while standalone nvurisrcbin works.
Is this a known regression in nvmultiurisrcbin?
Is there a patch or additional property required to enable its internal
RTSP reconnect monitoring?
If the current version cannot be resolved, I hope it can be fixed. Thank you!