Delayed startup of specific components like DeepStream and VST within the AI NVR setup

Hi everyone,

How can I troubleshoot the delayed startup of specific components like DeepStream and VST within the AI NVR setup, following a system reboot due to power cut? Despite NVStreamer Docker being up and running, these components failed to start for over an hour, which is unusual. Any insights or suggestions on resolving this issue would be greatly appreciated.

Thanks,
Tanisha

Can you remove all those images and start up again? you also can check log by: docker logs deepstream

$ docker compose -f compose_agx.yaml down --remove-orphans --volumes --rmi all
$ docker volume prune
$ sudo rm -rf /data/

Hi,
Thanks for your reply.
But, I’m facing the following error while running these commands.
image
Could you pls suggest the further steps.

Regards,
Tanisha

1 Like

Always run all docker commands as a sudo user.

sudo docker compose -f compose_agx.yaml down --remove-orphans --volumes --rmi all

The manual fix will be to edit the base_compose.yaml
Update all init container ubuntu image
image: ubuntu
to
image: ubuntu@sha256:77906da86b60585ce12215807090eb327e7386c8fafb5402369e421f44eff17e

Hi,
Thank you for your reply.
I tried to manually update all init container ubuntu image as suggested by you, but still facing errors.
Attaching a screenshot for your reference.

Regards,
Tanisha

Seems there is docker issue on your setup. Can you have a try: sudo systemctl restart docker?

@kesong
Hey, my docker setup is correct but still some containers aren’t working.


I also checked the ubuntu image that you had mentioned earlier and I also have the same updated one (image: ubuntu@sha256:77906da86b60585ce12215807090eb327e7386c8fafb5402369e421f44eff17e).

Please refer here for AI NVR: AI NVR — Metropolis on Jetson documentation 0.1.0 documentation
You needn’t any change for this version.

I assume you have the latest files; if not, please download the newest application bundle. Please first start the Ingress, Redis, and VST services, then run docker-compose. These three services are not running behind, and Docker Compose is waiting for them to start.

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