Open eldadh opened 6 months ago
Interesting, is the issue still present on 3.0.0b7?
unfortunatly yes ( i have tried both gstreamer configuration an ffmpeg) on jetson nano:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes
**** UID/GID ***
User uid: 1000
User gid: 1000
** Done **
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-gid-video-device: executing...
[cont-init.d] 20-gid-video-device: exited 0.
[cont-init.d] 30-edgetpu-permission: executing...
** Setting EdgeTPU permissions *
Coral Vendor IDs:
"1a6e"
"18d1"
No EdgeTPU USB device was found
No EdgeTPU PCI device was found
** Done **
[cont-init.d] 30-edgetpu-permission: exited 0.
[cont-init.d] 40-set-env-vars: executing...
** Checking for hardware acceleration platforms **
OpenCL cannot be used
VA-API cannot be used
CUDA is available!
PostgreSQL major version: 10
PostgreSQL bin: /usr/lib/postgresql/10/bin
* Done ***
[cont-init.d] 40-set-env-vars: exited 0.
[cont-init.d] 50-check-if-rpi: executing...
** Checking if we are running on an RPi **
Not running on any supported RPi
* Done ***
[cont-init.d] 50-check-if-rpi: exited 0.
[cont-init.d] 55-check-if-jetson: executing...
** Checking if we are running on a Jetson Board **
Running on a Jetson Nano
* Done ***
[cont-init.d] 55-check-if-jetson: exited 0.
[cont-init.d] 60-ffmpeg-path: executing...
** Getting FFmpeg path *
FFmpeg path: /usr/bin/ffmpeg
***** Done *****
[cont-init.d] 60-ffmpeg-path: exited 0.
[cont-init.d] 70-gstreamer-path: executing...
* Getting GStreamer path *
GStreamer path: /usr/bin/gst-launch-1.0
*** Done *****
[cont-init.d] 70-gstreamer-path: exited 0.
[cont-init.d] 80-postgres: executing...
* Preparing PostgreSQL *
Database has already been initialized.
***** Done ***
[cont-init.d] 80-postgres: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting PostgreSQL Server...
/var/run/postgresql:5432 - no response
Waiting for PostgreSQL Server to start...
2024-06-19 10:36:39.429 IDT [496] LOG: listening on IPv4 address "127.0.0.1", port 5432
2024-06-19 10:36:39.429 IDT [496] LOG: could not bind IPv6 address "::1": Cannot assign requested address
2024-06-19 10:36:39.429 IDT [496] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2024-06-19 10:36:39.441 IDT [496] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-06-19 10:36:39.487 IDT [498] LOG: database system was interrupted; last known up at 2024-06-19 10:16:32 IDT
2024-06-19 10:36:39.546 IDT [498] LOG: database system was not properly shut down; automatic recovery in progress
2024-06-19 10:36:39.562 IDT [498] LOG: redo starts at 0/16B7928
2024-06-19 10:36:39.562 IDT [498] LOG: invalid record length at 0/16B7A08: wanted 24, got 0
2024-06-19 10:36:39.562 IDT [498] LOG: redo done at 0/16B79D0
2024-06-19 10:36:39.620 IDT [496] LOG: database system is ready to accept connections
/var/run/postgresql:5432 - accepting connections
PostgreSQL Server has started!
[2024-06-19 10:36:44] [INFO ] [viseron.core] - -------------------------------------------
[2024-06-19 10:36:44] [INFO ] [viseron.core] - Initializing Viseron 3.0.0b7
[2024-06-19 10:36:44] [INFO ] [viseron.components] - Setting up component logger
[2024-06-19 10:36:44] [INFO ] [viseron.components] - Setup of component logger took 0.0 seconds
[2024-06-19 10:36:44] [INFO ] [viseron.components] - Setting up component data_stream
[2024-06-19 10:36:44] [DEBUG ] [viseron.components.data_stream] - ulimit -u output: unlimited
[2024-06-19 10:36:44] [DEBUG ] [viseron.components.data_stream] - Max threads: 999999
[2024-06-19 10:36:44] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(data_stream, initial daemon)> in the watchdog
[2024-06-19 10:36:44] [INFO ] [viseron.components] - Setup of component data_stream took 0.0 seconds
[2024-06-19 10:36:44] [INFO ] [viseron.components] - Setting up component webserver
[2024-06-19 10:36:44] [DEBUG ] [asyncio] - Using selector: EpollSelector
[2024-06-19 10:36:44] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method Webserver.stop of <Webserver(Tornado Webserver, initial daemon)>>
[2024-06-19 10:36:44] [INFO ] [viseron.components] - Setup of component webserver took 0.0 seconds
[2024-06-19 10:36:44] [INFO ] [viseron.components] - Setting up component storage
[2024-06-19 10:36:45] [INFO ] [alembic.runtime.migration] - Context impl PostgresqlImpl.
[2024-06-19 10:36:45] [INFO ] [alembic.runtime.migration] - Will assume transactional DDL.
[2024-06-19 10:36:45] [DEBUG ] [viseron.components.storage] - Current database revision: 8462ca6851b2
[2024-06-19 10:36:45] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic event/domain/registered/camera, <bound method Storage._camera_registered of <viseron.components.storage.Storage object at 0x7f5b8cca60>>
[2024-06-19 10:36:45] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/stopping, <bound method Storage._shutdown of <viseron.components.storage.Storage object at 0x7f5b8cca60>>
[2024-06-19 10:36:45] [INFO ] [viseron.components] - Setup of component storage took 0.4 seconds
[2024-06-19 10:36:45] [INFO ] [viseron.components] - Setting up component darknet
[2024-06-19 10:36:45] [INFO ] [viseron.components] - Setting up component gstreamer
[2024-06-19 10:36:45] [INFO ] [viseron.components] - Setting up component mog2
[2024-06-19 10:36:45] [INFO ] [viseron.components] - Setting up component nvr
[2024-06-19 10:36:45] [INFO ] [viseron.components] - Setup of component nvr took 0.0 seconds
[2024-06-19 10:36:45] [INFO ] [viseron.components] - Setup of component mog2 took 0.0 seconds
[2024-06-19 10:36:45] [DEBUG ] [viseron.components.darknet] - Using native Darknet
[2024-06-19 10:36:45] [DEBUG ] [viseron.components.darknet] - Using weights /detectors/models/darknet/yolov7-tiny.weights and config /detectors/models/darknet/yolov7-tiny.cfg, 416x416
[2024-06-19 10:36:45] [DEBUG ] [viseron.components.darknet] - Creating Darknet data file /home/abc/darknet_data.data
[2024-06-19 10:36:45] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(child_process.darknet.object_detector.input_thread, initial daemon)> in the watchdog
[2024-06-19 10:36:45] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(child_process.darknet.object_detector.output_thread, initial daemon)> in the watchdog
[2024-06-19 10:36:45] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method ChildProcessWorker.stop of <viseron.components.darknet.DarknetNative object at 0x7f43bf65f0>>
[2024-06-19 10:36:45] [DEBUG ] [viseron.components.darknet.libdarknet] - Try to load cfg: /detectors/models/darknet/yolov7-tiny.cfg, weights: /detectors/models/darknet/yolov7-tiny.weights, clear = 0
viseron: get_gpu_compute_capability: Unknown error 526785648
[2024-06-19 10:36:45] [DEBUG ] [viseron.components.darknet.libdarknet] - CUDA status Error: file: ./src/dark_cuda.c: func: get_gpu_compute_capability() line: 607
[2024-06-19 10:36:45] [DEBUG ] [viseron.components.darknet.libdarknet] -
[2024-06-19 10:36:45] [DEBUG ] [viseron.components.darknet.libdarknet] - CUDA Error: no CUDA-capable device is detected
[2024-06-19 10:36:45] [INFO ] [viseron.components] - Setup of component gstreamer took 0.0 seconds
[2024-06-19 10:36:49] [DEBUG ] [viseron.components.webserver.websocket_api] - WebSocket opened
[2024-06-19 10:36:49] [DEBUG ] [viseron.components.webserver.websocket_api] - Received {"type":"subscribe_event","event":"domain/registered/camera","command_id":1}
[2024-06-19 10:36:49] [DEBUG ] [viseron.components.webserver.websocket_api] - Received {"type":"subscribe_event","event":"domain/setup/domain_failed/camera/","command_id":2}
[2024-06-19 10:36:49] [DEBUG ] [viseron.components.webserver.websocket_api] - Received {"type":"subscribe_event","event":"domain/setup/domain_loaded/camera/","command_id":3}
[2024-06-19 10:36:49] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic event/domain/registered/camera, <function subscribe_event.
Which Jetpack version are you running on? In v3 i have upgraded to 32.7.1, i am thinking there might be som driver compatibility issues at play
root@jetson:/usr/local/mesh_services/meshagent# sudo apt-cache show nvidia-jetpack Package: nvidia-jetpack Version: 4.6.4-b39 Architecture: arm64 Maintainer: NVIDIA Corporation Installed-Size: 194 Depends: nvidia-l4t-jetson-multimedia-api (>> 32.7-0), nvidia-l4t-jetson-multimedia-api (<< 32.8-0), nvidia-cuda (= 4.6.4-b39), nvidia-tensorrt (= 4.6.4-b39), nvidia-nsight-sys (= 4.6.4-b39), nvidia-cudnn8 (= 4.6.4-b39), nvidia-opencv (= 4.6.4-b39), nvidia-container (= 4.6.4-b39), nvidia-visionworks (= 4.6.4-b39), nvidia-vpi (= 4.6.4-b39) Homepage: http://developer.nvidia.com/jetson Priority: standard Section: metapackages Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_4.6.4-b39_arm64.deb Size: 29388 SHA256: adf7a6660f73cdc4f95bc15c48d8588688e3afa5ee18bfd5b3a3caa3a458aa02 SHA1: 5abbe0df74f71579c1a0ee30ab7c2c236e1bcdbb MD5sum: ec293a56d17f2b2793448d621811330d Description: NVIDIA Jetpack Meta Package Description-md5: ad1462289bdbc54909ae109d1d32c0a8
Package: nvidia-jetpack Version: 4.6.3-b17 Architecture: arm64 Maintainer: NVIDIA Corporation Installed-Size: 194 Depends: nvidia-l4t-jetson-multimedia-api (>> 32.7-0), nvidia-l4t-jetson-multimedia-api (<< 32.8-0), nvidia-cuda (= 4.6.3-b17), nvidia-tensorrt (= 4.6.3-b17), nvidia-nsight-sys (= 4.6.3-b17), nvidia-cudnn8 (= 4.6.3-b17), nvidia-opencv (= 4.6.3-b17), nvidia-container (= 4.6.3-b17), nvidia-vpi (= 4.6.3-b17) Homepage: http://developer.nvidia.com/jetson Priority: standard Section: metapackages Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_4.6.3-b17_arm64.deb Size: 29368 SHA256: 694254a8667ebbf13852548bdd13a5b8ae61481ac059845b706398eefdcb9e01 SHA1: 67140fc8463ec61fd69352b225244b639c799edd MD5sum: afa1382b6caded6b736d494fc481bab4 Description: NVIDIA Jetpack Meta Package Description-md5: ad1462289bdbc54909ae109d1d32c0a8
Package: nvidia-jetpack Version: 4.6.2-b5 Architecture: arm64 Maintainer: NVIDIA Corporation Installed-Size: 194 Depends: nvidia-cuda (= 4.6.2-b5), nvidia-opencv (= 4.6.2-b5), nvidia-cudnn8 (= 4.6.2-b5), nvidia-tensorrt (= 4.6.2-b5), nvidia-visionworks (= 4.6.2-b5), nvidia-container (= 4.6.2-b5), nvidia-vpi (= 4.6.2-b5), nvidia-l4t-jetson-multimedia-api (>> 32.7-0), nvidia-l4t-jetson-multimedia-api (<< 32.8-0) Homepage: http://developer.nvidia.com/jetson Priority: standard Section: metapackages Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_4.6.2-b5_arm64.deb Size: 29378 SHA256: 925f4abff97e6024d86cff3b9e132e7c7554d05fb83590487381b7e925d5b2bb SHA1: e3ef727e87df5c331aece34508c110d57d744fe9 MD5sum: 7cb2e387af41bc8143ac7b6525af7794 Description: NVIDIA Jetpack Meta Package Description-md5: ad1462289bdbc54909ae109d1d32c0a8
Package: nvidia-jetpack Version: 4.6.1-b110 Architecture: arm64 Maintainer: NVIDIA Corporation Installed-Size: 194 Depends: nvidia-cuda (= 4.6.1-b110), nvidia-opencv (= 4.6.1-b110), nvidia-cudnn8 (= 4.6.1-b110), nvidia-tensorrt (= 4.6.1-b110), nvidia-visionworks (= 4.6.1-b110), nvidia-container (= 4.6.1-b110), nvidia-vpi (= 4.6.1-b110), nvidia-l4t-jetson-multimedia-api (>> 32.7-0), nvidia-l4t-jetson-multimedia-api (<< 32.8-0) Homepage: http://developer.nvidia.com/jetson Priority: standard Section: metapackages Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_4.6.1-b110_arm64.deb Size: 29366 SHA256: acfd9e75af780eab165361d61de4b4fe4974890864fe191060b402ac4c2f54d5 SHA1: a016568ac53705acc145a9f7e60505707bea259f MD5sum: 79be976b184a8c885bd9169ea5b7fb7b Description: NVIDIA Jetpack Meta Package Description-md5: ad1462289bdbc54909ae109d1d32c0a8
What is t he output of dpkg-query --show nvidia-l4t-core
?
eldadh@jetson:~$ dpkg-query --show nvidia-l4t-core nvidia-l4t-core 32.7.4-20230608212426
Hmm, seems to match whats inside the container...
Does the docker tag 3.0.0b3
work? That version still used L4T 32.6.1
You might get some database version issues so its best to start fresh by either deleting the postgresql
folder in the config or just create a new temporary config folder for Viseron and mount that in the container
in b3 version, there was SQL issues:
eldadh@jetson:~$ sudo docker logs viseron [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... **** UID/GID *** User uid: 1000 User gid: 1000 ** Done ** [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-gid-video-device: executing... [cont-init.d] 20-gid-video-device: exited 0. [cont-init.d] 30-edgetpu-permission: executing... ** Setting EdgeTPU permissions * Coral Vendor IDs: "1a6e" "18d1" No EdgeTPU USB device was found No EdgeTPU PCI device was found ** Done ** [cont-init.d] 30-edgetpu-permission: exited 0. [cont-init.d] 40-set-env-vars: executing... ** Checking for hardware acceleration platforms ** OpenCL cannot be used VA-API cannot be used CUDA is available! * Done *** [cont-init.d] 40-set-env-vars: exited 0. [cont-init.d] 50-check-if-rpi: executing... ** Checking if we are running on an RPi ** Not running on any supported RPi * Done *** [cont-init.d] 50-check-if-rpi: exited 0. [cont-init.d] 55-check-if-jetson: executing... ** Checking if we are running on a Jetson Board ** Running on a Jetson Nano * Done *** [cont-init.d] 55-check-if-jetson: exited 0. [cont-init.d] 60-ffmpeg-path: executing... ** Getting FFmpeg path * FFmpeg path: /usr/bin/ffmpeg ***** Done ***** [cont-init.d] 60-ffmpeg-path: exited 0. [cont-init.d] 70-gstreamer-path: executing... * Getting GStreamer path * GStreamer path: /usr/bin/gst-launch-1.0 *** Done ***** [cont-init.d] 70-gstreamer-path: exited 0. [cont-init.d] 80-postgres: executing... * Preparing PostgreSQL * Database has already been initialized. ***** Done ***** [cont-init.d] 80-postgres: exited 0. [cont-init.d] done. [services.d] starting services Starting PostgreSQL Server... s6-applyuidgid: fatal: unable to exec /usr/lib/postgresql/12/bin/postgres: No such file or directory
Right, forgot about that. Will revert to 32.6.1 and see if that helps. Takes a while to rebuild all the containers tho
3.0.0b8
is built on 32.6.1. Can you try it and see if you still have problems?
unfortunately yes, same errors :
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
**** UID/GID ***
User uid: 1000
User gid: 1000
** Done **
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-gid-video-device: executing...
[cont-init.d] 20-gid-video-device: exited 0.
[cont-init.d] 30-edgetpu-permission: executing...
** Setting EdgeTPU permissions *
Coral Vendor IDs:
"1a6e"
"18d1"
No EdgeTPU USB device was found
No EdgeTPU PCI device was found
** Done **
[cont-init.d] 30-edgetpu-permission: exited 0.
[cont-init.d] 40-set-env-vars: executing...
** Checking for hardware acceleration platforms **
OpenCL cannot be used
VA-API cannot be used
CUDA is available!
PostgreSQL major version: 10
PostgreSQL bin: /usr/lib/postgresql/10/bin
* Done ***
[cont-init.d] 40-set-env-vars: exited 0.
[cont-init.d] 50-check-if-rpi: executing...
** Checking if we are running on an RPi **
Not running on any supported RPi
* Done ***
[cont-init.d] 50-check-if-rpi: exited 0.
[cont-init.d] 55-check-if-jetson: executing...
** Checking if we are running on a Jetson Board **
Running on a Jetson Nano
* Done ***
[cont-init.d] 55-check-if-jetson: exited 0.
[cont-init.d] 60-ffmpeg-path: executing...
** Getting FFmpeg path *
FFmpeg path: /usr/bin/ffmpeg
***** Done *****
[cont-init.d] 60-ffmpeg-path: exited 0.
[cont-init.d] 70-gstreamer-path: executing...
* Getting GStreamer path *
GStreamer path: /usr/bin/gst-launch-1.0
*** Done *****
[cont-init.d] 70-gstreamer-path: exited 0.
[cont-init.d] 80-postgres: executing...
* Preparing PostgreSQL *
Database has already been initialized.
***** Done *****
[cont-init.d] 80-postgres: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting PostgreSQL Server...
/var/run/postgresql:5432 - no response
Waiting for PostgreSQL Server to start...
2024-07-12 14:06:54.714 IDT [499] LOG: listening on IPv4 address "127.0.0.1", port 5432
2024-07-12 14:06:54.714 IDT [499] LOG: could not bind IPv6 address "::1": Cannot assign requested address
2024-07-12 14:06:54.714 IDT [499] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2024-07-12 14:06:54.750 IDT [499] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-07-12 14:06:54.890 IDT [501] LOG: database system was shut down at 2024-07-11 00:16:22 IDT
2024-07-12 14:06:54.923 IDT [499] LOG: database system is ready to accept connections
/var/run/postgresql:5432 - accepting connections
PostgreSQL Server has started!
[2024-07-12 14:07:10] [INFO ] [viseron.core] - -------------------------------------------
[2024-07-12 14:07:10] [INFO ] [viseron.core] - Initializing Viseron 3.0.0b9
[2024-07-12 14:07:10] [INFO ] [viseron.components] - Setting up component logger
[2024-07-12 14:07:10] [INFO ] [viseron.components] - Setup of component logger took 0.0 seconds
[2024-07-12 14:07:10] [INFO ] [viseron.components] - Setting up component data_stream
[2024-07-12 14:07:10] [DEBUG ] [viseron.components.data_stream] - ulimit -u output: unlimited
[2024-07-12 14:07:10] [DEBUG ] [viseron.components.data_stream] - Max threads: 999999
[2024-07-12 14:07:10] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(data_stream, initial daemon)> in the watchdog
[2024-07-12 14:07:10] [INFO ] [viseron.components] - Setup of component data_stream took 0.0 seconds
[2024-07-12 14:07:10] [INFO ] [viseron.components] - Setting up component webserver
[2024-07-12 14:07:10] [DEBUG ] [asyncio] - Using selector: EpollSelector
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method Webserver.stop of <Webserver(Tornado Webserver, initial daemon)>>
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setup of component webserver took 0.0 seconds
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setting up component storage
[2024-07-12 14:07:11] [INFO ] [alembic.runtime.migration] - Context impl PostgresqlImpl.
[2024-07-12 14:07:11] [INFO ] [alembic.runtime.migration] - Will assume transactional DDL.
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.storage] - Current database revision: 19a2457c5924
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic event/domain/registered/camera, <bound method Storage._camera_registered of <viseron.components.storage.Storage object at 0x7f6be456c0>>
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/stopping, <bound method Storage._shutdown of <viseron.components.storage.Storage object at 0x7f6be456c0>>
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setup of component storage took 0.6 seconds
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setting up component darknet
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setting up component ffmpeg
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setting up component mog2
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setting up component gstreamer
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setting up component nvr
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setup of component nvr took 0.0 seconds
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setup of component mog2 took 0.0 seconds
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setup of component ffmpeg took 0.0 seconds
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.darknet] - Using native Darknet
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.darknet] - Using weights /detectors/models/darknet/yolov7-tiny.weights and config /detectors/models/darknet/yolov7-tiny.cfg, 416x416
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.darknet] - Creating Darknet data file /home/abc/darknet_data.data
[2024-07-12 14:07:11] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(child_process.darknet.object_detector.input_thread, initial daemon)> in the watchdog
[2024-07-12 14:07:11] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(child_process.darknet.object_detector.output_thread, initial daemon)> in the watchdog
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method ChildProcessWorker.stop of <viseron.components.darknet.DarknetNative object at 0x7f68c13dc0>>
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.darknet.libdarknet] - Try to load cfg: /detectors/models/darknet/yolov7-tiny.cfg, weights: /detectors/models/darknet/yolov7-tiny.weights, clear = 0
viseron: get_gpu_compute_capability: Unknown error 852421744
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.darknet.libdarknet] - CUDA status Error: file: ./src/dark_cuda.c: func: get_gpu_compute_capability() line: 607
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.darknet.libdarknet] -
[2024-07-12 14:07:11] [DEBUG ] [viseron.components.darknet.libdarknet] - CUDA Error: no CUDA-capable device is detected
[2024-07-12 14:07:11] [INFO ] [viseron.components] - Setup of component gstreamer took 0.0 seconds
[2024-07-12 14:07:26] [ERROR ] [viseron.components] - Component darknet is not ready. Retrying in 10 seconds in the background. Error: Failed to load Darknet network in child process
[2024-07-12 14:07:26] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <function Component.setup_component.
i have a jetson nano and I was thinking of trying this. Did you ever get the native nvida acceleration running?
I ran the latest beta ( [v3.0.0b6]) however it doesn't seem to recognize cuda on jetson nano
[fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... usermod: no changes **** UID/GID *** User uid: 1000 User gid: 1000 ** Done ** [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-gid-video-device: executing... [cont-init.d] 20-gid-video-device: exited 0. [cont-init.d] 30-edgetpu-permission: executing... ** Setting EdgeTPU permissions * Coral Vendor IDs: "1a6e" "18d1" No EdgeTPU USB device was found No EdgeTPU PCI device was found ** Done ** [cont-init.d] 30-edgetpu-permission: exited 0. [cont-init.d] 40-set-env-vars: executing... ** Checking for hardware acceleration platforms ** OpenCL cannot be used VA-API cannot be used CUDA is available! PostgreSQL major version: 10 PostgreSQL bin: /usr/lib/postgresql/10/bin * Done *** [cont-init.d] 40-set-env-vars: exited 0. [cont-init.d] 50-check-if-rpi: executing... ** Checking if we are running on an RPi ** Not running on any supported RPi * Done *** [cont-init.d] 50-check-if-rpi: exited 0. [cont-init.d] 55-check-if-jetson: executing... ** Checking if we are running on a Jetson Board ** Running on a Jetson Nano * Done *** [cont-init.d] 55-check-if-jetson: exited 0. [cont-init.d] 60-ffmpeg-path: executing... ** Getting FFmpeg path * FFmpeg path: /usr/bin/ffmpeg ***** Done ***** [cont-init.d] 60-ffmpeg-path: exited 0. [cont-init.d] 70-gstreamer-path: executing... * Getting GStreamer path * GStreamer path: /usr/bin/gst-launch-1.0 *** Done ***** [cont-init.d] 70-gstreamer-path: exited 0. [cont-init.d] 80-postgres: executing... * Preparing PostgreSQL * Database has already been initialized. ***** Done ***** [cont-init.d] 80-postgres: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Starting PostgreSQL Server... /var/run/postgresql:5432 - no response Waiting for PostgreSQL Server to start... 2024-05-23 11:45:55.087 IDT [496] LOG: listening on IPv4 address "127.0.0.1", port 5432 2024-05-23 11:45:55.087 IDT [496] LOG: could not bind IPv6 address "::1": Cannot assign requested address 2024-05-23 11:45:55.087 IDT [496] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry. 2024-05-23 11:45:55.097 IDT [496] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2024-05-23 11:45:55.134 IDT [498] LOG: database system was interrupted; last known up at 2024-05-23 11:44:26 IDT 2024-05-23 11:45:55.189 IDT [498] LOG: database system was not properly shut down; automatic recovery in progress 2024-05-23 11:45:55.203 IDT [498] LOG: redo starts at 0/1694608 2024-05-23 11:45:55.203 IDT [498] LOG: invalid record length at 0/1694640: wanted 24, got 0 2024-05-23 11:45:55.203 IDT [498] LOG: redo done at 0/1694608 2024-05-23 11:45:55.253 IDT [496] LOG: database system is ready to accept connections /var/run/postgresql:5432 - accepting connections PostgreSQL Server has started! [2024-05-23 11:45:58] [INFO ] [viseron.core] - ------------------------------------------- [2024-05-23 11:45:58] [INFO ] [viseron.core] - Initializing Viseron 3.0.0b6 [2024-05-23 11:45:58] [INFO ] [viseron.components] - Setting up component logger [2024-05-23 11:45:58] [INFO ] [viseron.components] - Setup of component logger took 0.0 seconds [2024-05-23 11:45:58] [INFO ] [viseron.components] - Setting up component data_stream [2024-05-23 11:45:58] [DEBUG ] [viseron.components.data_stream] - ulimit -u output: unlimited [2024-05-23 11:45:58] [DEBUG ] [viseron.components.data_stream] - Max threads: 999999 [2024-05-23 11:45:58] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(data_stream, initial daemon)> in the watchdog [2024-05-23 11:45:58] [INFO ] [viseron.components] - Setup of component data_stream took 0.0 seconds [2024-05-23 11:45:58] [INFO ] [viseron.components] - Setting up component storage [2024-05-23 11:45:59] [INFO ] [alembic.runtime.migration] - Context impl PostgresqlImpl. [2024-05-23 11:45:59] [INFO ] [alembic.runtime.migration] - Will assume transactional DDL. [2024-05-23 11:45:59] [DEBUG ] [viseron.components.storage] - Current database revision: 5f972755b320 [2024-05-23 11:45:59] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic event/domain/registered/camera, <bound method Storage._camera_registered of <viseron.components.storage.Storage object at 0x7f432c1f60>> [2024-05-23 11:45:59] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/stopping, <bound method Storage._shutdown of <viseron.components.storage.Storage object at 0x7f432c1f60>> [2024-05-23 11:45:59] [INFO ] [viseron.components] - Setup of component storage took 0.2 seconds [2024-05-23 11:45:59] [INFO ] [viseron.components] - Setting up component webserver [2024-05-23 11:45:59] [DEBUG ] [asyncio] - Using selector: EpollSelector [2024-05-23 11:45:59] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method Webserver.stop of <Webserver(Tornado Webserver, initial daemon)>> [2024-05-23 11:45:59] [INFO ] [viseron.components] - Setup of component webserver took 0.0 seconds [2024-05-23 11:45:59] [INFO ] [viseron.components] - Setting up component ffmpeg [2024-05-23 11:45:59] [INFO ] [viseron.components] - Setting up component darknet [2024-05-23 11:45:59] [INFO ] [viseron.components] - Setting up component nvr [2024-05-23 11:45:59] [INFO ] [viseron.components] - Setting up component mog2 [2024-05-23 11:45:59] [INFO ] [viseron.components] - Setup of component nvr took 0.0 seconds [2024-05-23 11:45:59] [INFO ] [viseron.components] - Setup of component ffmpeg took 0.0 seconds [2024-05-23 11:45:59] [INFO ] [viseron.components] - Setup of component mog2 took 0.0 seconds [2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet] - Using native Darknet [2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet] - Using weights /detectors/models/darknet/yolov7-tiny.weights and config /detectors/models/darknet/yolov7-tiny.cfg, 416x416 [2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet] - Creating Darknet data file /home/abc/darknet_data.data [2024-05-23 11:45:59] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(child_process.darknet.object_detector.input_thread, initial daemon)> in the watchdog [2024-05-23 11:45:59] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(child_process.darknet.object_detector.output_thread, initial daemon)> in the watchdog [2024-05-23 11:45:59] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method ChildProcessWorker.stop of <viseron.components.darknet.DarknetNative object at 0x7f40ff8700>> [2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet.libdarknet] - Try to load cfg: /detectors/models/darknet/yolov7-tiny.cfg, weights: /detectors/models/darknet/yolov7-tiny.weights, clear = 0 viseron: get_gpu_compute_capability: Unknown error 1080216688 [2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet.libdarknet] - CUDA status Error: file: ./src/dark_cuda.c: func: get_gpu_compute_capability() line: 607 [2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet.libdarknet] - [2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet.libdarknet] - CUDA Error: no CUDA-capable device is detected