Advices on debugging DeepStream

[f.carmone]

• Hardware Platform (Jetson / GPU)
Jetson Orin Nano 8GB
• DeepStream Version
7.1
• JetPack Version (valid for Jetson only)
6.1
• TensorRT Version
10.3

Hello, I’m still experimenting with deepstream-app configuration files, and I was wondering if you had any advice on how to debug them when errors arise.

Sometimes it gives a a more-or-less significant issue such as

ERROR from primary_gie: Configuration file parsing failed

which clearly indicates where the problem is.

Other times everything runs correctly, but I couldn’t see the results I was hoping for; on that occasions, the cause was a missing sink in order for the nvdosd plugin to work.

Right now I’m stuck with this problem, and I would like to dig deeper into it

(deepstream-app:228772): GStreamer-CRITICAL **: 09:56:14.354: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed
** ERROR: <create_pipeline:1927>: create_pipeline failed
** ERROR: <main:695>: Failed to create pipeline
Quitting
App run failed

Is there any environment variable I can use, or maybe attaching a certain plugin, that would allow me to understand the cause of such errors?

[yuweiw]

1. You can try to add GST_DEBUG=3 in front of your command line to open more log info.
2. You can add some logs in the source code directly. deepstream\sources\apps\sample_apps\deepstream-app

[f.carmone]

Thank you for that environment variable, I will use it

Right now I’m working with a config file (the ones you run with deepstream-app -c config.txt), so I don’t have access to the source code, unless you meant the DeepStream libraries

[yuweiw]

@f.carmone

Right now I’m working with a config file (the ones you run with deepstream-app -c config.txt), so I don’t have access to the source code, unless you meant the DeepStream libraries

This part is open source, you can customize it according to your needs. The source path of the deepstream-app is as follows /opt/nvidia/deepstream/deepstream/sources/apps/sample_apps/deepstream-app.