ERROR from element nvmsg-broker: Could not configure supporting library?

• Hardware Platform (Jetson / GPU) → dGPU
• DeepStream Version → 5.1
• TensorRT Version → 7.2
• NVIDIA GPU Driver Version (valid for GPU only) → 465.82
• docker → nvcr.io/nvidia/deepstream:5.1-21.02-triton


So, I was testing the deepstream-test4 app. I have run the docker container nvcr.io/nvidia/deepstream:5.1-21.02-triton, and in the dicker I have install kafka and have test the producer-consumer program. it is all ok.

After making the deepstream-test4-app, I conduct this command in a terminal:


deepstream-test4-app -i /opt/nvidia/deepstream/deepstream-5.1/samples/streams/sample_720p.mp4 -p /opt/nvidia/deepstream/deepstream-5.1/lib/libnvds_kafka_proto.so --conn-str=172.17.0.2:9092 --topic=test -s 1


And then I encountered this error:


Now playing: /opt/nvidia/deepstream/deepstream-5.1/samples/streams/sample_720p.mp4
Running…
ERROR from element nvmsg-broker: Could not configure supporting library.
Error details: gstnvmsgbroker.c(388): legacy_gst_nvmsgbroker_start (): /GstPipeline:dstest4-pipeline/GstNvMsgBroker:nvmsg-broker:
unable to connect to broker library
Returned, stopping playback
Deleting pipeline


**I have read the earlier question /GstPipeline:dstest4-pipeline/GstNvMsgBroker:nvmsg-broker: unable to connect to broker library.It seems not helpful. **
I have check the library .so file and it is there all right. The path of the library is OK.
Any help are appreciated. Thank in advance.

Please enable logging, and get more log for analysis.
sources/tools/nvds_logger/setup_nvds_logger.sh
echo “if ($msg contains ‘DSLOG’) and ($syslogseverity <= 7) then $nvdslogfilepath” >> 11-nvds.conf //default 6, change to 7 for debug-level messages
sudo ./sources/tools/nvds_logger/setup_nvds_logger.sh

If I run


…/…/…/…/sources/tools/nvds_logger/setup_nvds_logger.sh


the reply is folowing:


Using logging location: /tmp/nvds/

    • Stopping enhanced syslogd rsyslogd [ OK ] *
    • Starting enhanced syslogd rsyslogd [ OK ] *
      nvds logging setup. Logging to /tmp/nvds/ds.log

I am not clear about the command.


echo “if ($msg contains ‘DSLOG’) and ($syslogseverity <= 7) then $nvdslogfilepath” >> 11-nvds.conf //default 6, change to 7 for debug-level messages


please provide more details. Thanks.

I have read the blog"



It is same with my question. It seems no way to deal with this error. Seek for help. Thanks.

Please run with super priority.
sudo “command to run”
after that, you can see the log from /tmp/nvds/ds.log

The content in /tmp/nvds/ds.log is,


Aug 25 06:48:59 deepstream-app: DSLOG:NVDS_KAFKA_PROTO: kafka partition key field name = sensor.id#012
Aug 25 06:48:59 deepstream-app: DSLOG:NVDS_KAFKA_PROTO: Consumer group id not specified in cfg. Using default group id: test-consumer-group #012
Aug 25 06:48:59 deepstream-app: DSLOG:NVDS_KAFKA_PROTO: Kafka connection successful#012


I am still confused on,
**(1). Why does kafka consumer still not receive any message? It seems that the connection is built. **
(2). The app is not set as a consumer. What is the consumer-group?
(3). What is the sensor.id? Configed in nvmsgconv config file? What is the meaning?

Thanks a lot.

Please change echo “if ($msg contains ‘DSLOG’) and ($syslogseverity <= 6) then $nvdslogfilepath” >> 11-nvds.conf
to
echo “if ($msg contains ‘DSLOG’) and ($syslogseverity <= 7) then $nvdslogfilepath” >> 11-nvds.conf
in sources/tools/nvds_logger/setup_nvds_logger.sh
get debug level message.

**(1). Why does kafka consumer still not receive any message? It seems that the connection is built. **
(2). The app is not set as a consumer. What is the consumer-group?
[amycao] Please specify details how you check kafka consumer did not receive message. if you want the app as a consumer, please enable [message-consumerX] in configuration, check this IoT — DeepStream 5.1 Release documentation
(3). What is the sensor.id? Configed in nvmsgconv config file? What is the meaning?
[amycao] These are the predefined values for cameras/sensors/location. it’s for endeavor garage sensor/location description.