Actual rtsp reconnect duration is longer than rtsp-reconnect-interval

Accelerated Computing Intelligent Video Analytics DeepStream SDK
1

PC: RTX 2070 Super
Deepstream: 6.4
Driver Version: 535.154.05
Docker image: deepstream:6.4-gc-triton-devel

I am working on the sample app deepstream-test3 in C++ for deepstream 6.4. I can compile and use the app correctly.

i am testing rtsp-reconnect-interval functionality in nvurisrcbin, thus I make the following changes.

export NVDS_TEST3_PERF_MODE=1

  if (PERF_MODE) {
    uri_decode_bin = gst_element_factory_make ("nvurisrcbin", "uri-decode-bin");
    g_object_set (G_OBJECT (uri_decode_bin), "file-loop", TRUE, NULL);
    g_object_set (G_OBJECT (uri_decode_bin), "cudadec-memtype", 0, NULL);
    g_object_set(G_OBJECT(uri_decode_bin), "rtsp-reconnect-interval", 1, NULL);
  }

For simplicity I remove the pgie element linking and compile and run the app on 4 simulated rtsp sources as below

./deepstream-test3-app rtsp://127.0.0.1:8550/test rtsp://127.0.0.1:8551/test rtsp://127.0.0.1:8552/test rtsp://127.0.0.1:8553/test

After about 5 seconds of running the pipeline I stop the simulated rtsp source (rtsp://127.0.0.1:8551/test) for 3 seconds and start it back up. I expect the deepstream app to reconnect within 1 second as per the timeout, however it takes almost 30 seconds, and I do not see any log messages trying to reconnect every second as expected.

**PERF : FPS_0 (20.00)	FPS_1 (20.00)	FPS_2 (20.00)	FPS_3 (20.00)	
**PERF : FPS_0 (20.00)	FPS_1 (20.00)	FPS_2 (20.00)	FPS_3 (20.00)	
**PERF : FPS_0 (20.00)	FPS_1 (20.00)	FPS_2 (20.00)	FPS_3 (20.00)	
**PERF : FPS_0 (20.00)	FPS_1 (20.00)	FPS_2 (20.00)	FPS_3 (20.00)	
**PERF : FPS_0 (20.00)	FPS_1 (20.00)	FPS_2 (20.00)	FPS_3 (20.00)	
WARNING from element src: Could not read from resource.
Warning: Could not read from resource.
WARNING from element src: Could not open resource for reading and writing.
Warning: Could not open resource for reading and writing.
WARNING from element src: Internal data stream error.
Warning: Internal data stream error.
Resetting source rtsp://127.0.0.1:8551/test
WARNING from element uri-decode-bin: No data from source rtsp://127.0.0.1:8551/test since last 1 sec. Trying reconnection
Warning: No data from source rtsp://127.0.0.1:8551/test since last 1 sec. Trying reconnection
WARNING from element src: Could not open resource for reading and writing.
Warning: Could not open resource for reading and writing.
**PERF : FPS_0 (19.96)	FPS_1 (17.96)	FPS_2 (19.96)	FPS_3 (19.96)	
**PERF : FPS_0 (19.97)	FPS_1 (15.40)	FPS_2 (19.97)	FPS_3 (19.97)	
**PERF : FPS_0 (19.97)	FPS_1 (13.47)	FPS_2 (19.97)	FPS_3 (19.97)	
**PERF : FPS_0 (19.97)	FPS_1 (11.98)	FPS_2 (19.97)	FPS_3 (19.97)	
**PERF : FPS_0 (19.98)	FPS_1 (10.78)	FPS_2 (19.98)	FPS_3 (19.98)	
**PERF : FPS_0 (19.98)	FPS_1 (9.80)	FPS_2 (19.98)	FPS_3 (19.98)	
**PERF : FPS_0 (19.98)	FPS_1 (8.98)	FPS_2 (19.98)	FPS_3 (19.98)	
**PERF : FPS_0 (19.98)	FPS_1 (8.29)	FPS_2 (19.98)	FPS_3 (19.98)	
**PERF : FPS_0 (19.98)	FPS_1 (7.70)	FPS_2 (19.98)	FPS_3 (19.98)	
**PERF : FPS_0 (19.98)	FPS_1 (7.19)	FPS_2 (19.98)	FPS_3 (19.98)	
**PERF : FPS_0 (19.98)	FPS_1 (6.74)	FPS_2 (19.98)	FPS_3 (19.98)	
**PERF : FPS_0 (19.99)	FPS_1 (6.34)	FPS_2 (19.99)	FPS_3 (19.99)	
Resetting source rtsp://127.0.0.1:8551/test
Decodebin child added: h264parse4
Decodebin child added: capsfilter4
Decodebin child added: nvv4l2decoder4
**PERF : FPS_0 (20.00)	FPS_1 (6.40)	FPS_2 (20.00)	FPS_3 (20.00)	
**PERF : FPS_0 (20.00)	FPS_1 (7.11)	FPS_2 (20.00)	FPS_3 (20.00)	
**PERF : FPS_0 (20.00)	FPS_1 (7.76)	FPS_2 (20.00)	FPS_3 (20.00)	
**PERF : FPS_0 (20.00)	FPS_1 (8.34)	FPS_2 (20.00)	FPS_3 (20.00)

To add more context, if the source is down at first and then the application is started up, the deepstream app, will try reconnection (Resetting source) very frequently (almost every second), as expected.

3

I am checking.

4

rtsp-reconnect-interval=1 is too short. As you known, rtsp reconnection needs to cost some time. you can try 10 seconds first. if 10 seconds is fine, you can lower the interval further.

5

Hi,
Thanks for the reply, I have tried with rtsp-reconnect-interval=30, but the behavior I observe is still the same. When the camera goes down, it will try to reconnect after 30 seconds, and if the camera is still down, it tries to reconnect every 60 seconds instead of the configured 30. The re-connection works fine, but I am wondering about the discrepancies of following 30 seconds initially and then using 60 seconds thereafter.

6

could you share the log with rtsp-reconnect-interval=30? Thanks!

7

Hi,
Please find the full log attached
The brief timeline of the events are here as well. The very first try is indeed after 30 seconds, but subsequent tries are after 60 seconds.
log.txt (7.5 KB)

------RUN APP------

**PERF : FPS_0 (20.00)	FPS_1 (20.00)	FPS_2 (20.00)	FPS_3 (20.00)

------Disconnect Stream 1 (Time 00:00)------

WARNING from element src: Could not read from resource.
Warning: Could not read from resource.
WARNING from element src: Could not open resource for reading and writing.
Warning: Could not open resource for reading and writing.
WARNING from element src: Internal data stream error.
Warning: Internal data stream error.

------DS try reconnect(Time 00:30)------

Resetting source rtsp://127.0.0.1:8551/test
WARNING from element uri-decode-bin: No data from source rtsp://127.0.0.1:8551/test since last 30 sec. Trying reconnection
Warning: No data from source rtsp://127.0.0.1:8551/test since last 30 sec. Trying reconnection
WARNING from element src: Could not open resource for reading and writing.
Warning: Could not open resource for reading and writing.

------DS try reconnect(Time 01:30)------

Resetting source rtsp://127.0.0.1:8551/test
WARNING from element src: Could not open resource for reading and writing.
Warning: Could not open resource for reading and writing.

------DS try reconnect(Time 02:30)------

Resetting source rtsp://127.0.0.1:8551/test
WARNING from element src: Could not open resource for reading and writing.
Warning: Could not open resource for reading and writing.

------Actual camera reconnect(Time 02:35)------

------DS try reconnect(Time 03:30)------
Resetting source rtsp://127.0.0.1:8551/test
Decodebin child added: h264parse4
Decodebin child added: capsfilter4
Decodebin child added: nvv4l2decoder4


------DS successfully reconnect to camera------
8

I am not able to reproduce this issue on dgpu with DS7.0. here is the log and test code.
deepstream_test3_app.c (20.2 KB)
log0719.txt (8.4 KB)

9

Hi,
Thanks for the reply. I have tested the same code and stream server as before with DS 7.0 and cannot reproduce it as well, which means it was fixed in DS 7.0.
However I am sure the problem still persists with DS 6.4 for future reference.

10

Thanks for sharing! Currently nvurisrcbin plugin is closesource. deepstream-app can support RTSP reconnection and is opensource. you can port RTSP reconnection logics to your application.

1 Like
11

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.