Deepstream app not working after reset_source_pipeline

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU) Quadro RTX 6000
• DeepStream Version Deepstream 5.1
• JetPack Version (valid for Jetson only)
• TensorRT Version
• NVIDIA GPU Driver Version (valid for GPU only) Cuda 11.7
• Issue Type( questions, new requirements, bugs) Question
• How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing) I’m using single-RTSP stream as an input
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)

I’m getting a following log when I run a deepstream-app, after that, it is not getting either terminated or killed, it is just stuck at that point. This happens, whenever reset_source_pipeline is getting called. I’ve provided 2 different logs which I got from running the app.

Log1:
[2023-12-07T19:38:18.512604Z] pid=2236 tid=2236 component=deepstream-app deepstream_source_bin.cpp:1189:reset_source_pipeline Resetting source 0
[2023-12-07T19:38:18.604992Z] pid=2236 tid=2236 component=deepstream-app deepstream_app_main.cpp:656:perf_cb **PERF: 1.070000 (29.049999
[2023-12-07T19:38:18.605465Z] pid=2236 tid=2236 component=deepstream-app deepstream_app.cpp:101:bus_callback WARNING from src_bin_muxer: Either host or Source 0 seems to be out of NTP sync SYS TIME = 2023-12-07T19:38:18.351Z CALCULATED NTP TIME = 2023-12-07T19:37:59.057Z
[2023-12-07T19:38:18.605486Z] pid=2236 tid=2236 component=deepstream-app deepstream_app.cpp:106:bus_callback Debug info: gstnvstreammux_ntp.cpp(97): check_if_sys_rtcp_time_is_ntp_sync (): /GstPipeline:pipeline/GstBin:multi_src_bin/GstNvStreamMux:src_bin_muxer
[2023-12-07T19:38:23.817787Z] pid=2236 tid=2236 component=deepstream-app deepstream_app_main.cpp:656:perf_cb **PERF: 0.000000 (29.040001

Log2:
[2023-12-16T21:42:33.723367Z] pid=389 tid=389 component=deepstream_app deepstream_source_bin.cpp:1189:reset_source_pipeline Resetting source 0
[2023-12-16T21:42:33.748290Z] pid=389 tid=389 component=deepstream_app deepstream_source_bin.cpp:1189:reset_source_pipeline Resetting source 0
[2023-12-16T21:42:33.879280Z] pid=389 tid=389 component=deepstream_app deepstream_app_main.cpp:656:perf_cb **PERF: 0.240000 (29.719999
[2023-12-16T21:42:33.879624Z] pid=389 tid=389 component=deepstream_app deepstream_app.cpp:101:bus_callback WARNING from src_bin_muxer: Either host or Source 0 seems to be out of NTP sync SYS TIME = 2023-12-16T21:42:30.749Z CALCULATED NTP TIME = 2023-12-16T21:40:12.519Z
[2023-12-16T21:42:33.879659Z] pid=389 tid=389 component=deepstream_app deepstream_app.cpp:106:bus_callback Debug info: gstnvstreammux_ntp.cpp(97): check_if_sys_rtcp_time_is_ntp_sync (): /GstPipeline:pipeline/GstBin:multi_src_bin/GstNvStreamMux:src_bin_muxer
[2023-12-16T21:42:33.879716Z] pid=389 tid=389 component=deepstream_app deepstream_app.cpp:101:bus_callback WARNING from src_elem0: Could not write to resource.
[2023-12-16T21:42:33.879739Z] pid=389 tid=389 component=deepstream_app deepstream_app.cpp:106:bus_callback Debug info: gstrtspsrc.c(4884): gst_rtspsrc_send_keep_alive (): /GstPipeline:pipeline/GstBin:multi_src_bin/GstBin:src_sub_bin0/GstRTSPSrc:src_elem0:
Could not send keep-alive. (Operation interrupted)
[2023-12-16T21:42:33.904650Z] pid=389 tid=389 component=deepstream_app deepstream_app.cpp:118:bus_callback ERROR from src_elem0: Could not read from resource.
[2023-12-16T21:42:33.904699Z] pid=389 tid=389 component=deepstream_app deepstream_app.cpp:118:bus_callback ERROR from src_elem0: Could not write to resource.
[2023-12-16T21:42:33.904722Z] pid=389 tid=389 component=deepstream_app deepstream_app.cpp:101:bus_callback WARNING from src_elem0: Could not read from resource.
[2023-12-16T21:42:33.904734Z] pid=389 tid=389 component=deepstream_app deepstream_app.cpp:106:bus_callback Debug info: gstrtspsrc.c(5200): gst_rtspsrc_loop_interleaved (): /GstPipeline:pipeline/GstBin:multi_src_bin/GstBin:src_sub_bin0/GstRTSPSrc:src_elem0:
The server closed the connection.
[2023-12-16T21:42:33.907139Z] pid=389 tid=389 component=deepstream_app deepstream_app.cpp:118:bus_callback ERROR from src_elem0: Could not open resource for reading and writing.
Warning: Color primaries 5 not present and will be treated BT.601
[2023-12-16T21:42:48.949205Z] pid=389 tid=389 component=deepstream_app deepstream_app_main.cpp:656:perf_cb **PERF: 0.000000 (29.700001
[2023-12-16T21:42:51.825665Z] pid=389 tid=389 component=deepstream_app deepstream_app_main.cpp:656:perf_cb **PERF: 0.000000 (29.690001

I just want to know 2 things,

  1. Why reset_source_pipeline is getting called in the first place?
  2. And why after the call, the app got stuck? Any solution, to fix this problem. Other than porting to higher version.

Deepstream 5.1 is an old version. could you test the latest DS6.4 version? here is the link.

Hi @fanzh,

I just want to know 2 things,

  1. Why reset_source_pipeline is getting called in the first place?
  2. And why after the call, the app got stuck? Any solution, to fix this problem. Other than porting to higher version

There is no update from you for a period, assuming this is not an issue anymore.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

deepstrea-app code is opensource. the path is /opt/nvidia/deepstream/deepstream/sources/apps/apps-common.

    if (time_since_last_reconnect_sec >= SOURCE_RESET_INTERVAL_SEC) {
      if (time_diff_msec_since_last_reset > 3000) {
  1. as the code shown in watch_source_status, when source can’t get data after specific time-length, the app will call reset_source_pipeline.
  2. it should not be hung, the app will set source to GST_STATE_PLAYING after reset_source_pipeline. please refer to the test in this topic, please wait for a while. please refer to the test in this topic.

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