June 29Jun 29 Author 10 minutes ago, JWMutant said:s6-rc: info: service frigate successfully stoppeds6-rc: info: service go2rtc: stoppings6-rc: info: service frigate-log: stoppings6-rc: info: service frigate-log successfully stoppeds6-rc: info: service go2rtc successfully stoppeds6-rc: info: service prepare: stoppings6-rc: info: service go2rtc-log: stoppings6-rc: info: service prepare successfully stoppeds6-rc: info: service go2rtc-log successfully stoppeds6-rc: info: service log-prepare: stoppings6-rc: info: service s6rc-fdholder: stoppings6-rc: info: service log-prepare successfully stoppeds6-rc: info: service legacy-cont-init: stoppings6-rc: info: service s6rc-fdholder successfully stoppeds6-rc: info: service legacy-cont-init successfully stoppeds6-rc: info: service fix-attrs: stoppings6-rc: info: service fix-attrs successfully stoppeds6-rc: info: service s6rc-oneshot-runner: stoppings6-rc: info: service s6rc-oneshot-runner successfully stoppedERROR: driverInitFileInfo 578 result=11ERROR: init 664 result=11ERROR: init 250 result=11s6-rc: info: service s6rc-fdholder: startings6-rc: info: service s6rc-oneshot-runner: startings6-rc: info: service s6rc-oneshot-runner successfully starteds6-rc: info: service fix-attrs: startings6-rc: info: service s6rc-fdholder successfully starteds6-rc: info: service fix-attrs successfully starteds6-rc: info: service legacy-cont-init: startings6-rc: info: service legacy-cont-init successfully starteds6-rc: info: service prepare: startings6-rc: info: service log-prepare: startings6-rc: info: service log-prepare successfully starteds6-rc: info: service nginx-log: startings6-rc: info: service go2rtc-log: startings6-rc: info: service frigate-log: startings6-rc: info: service certsync-log: startings6-rc: info: service nginx-log successfully starteds6-rc: info: service go2rtc-log successfully starteds6-rc: info: service frigate-log successfully starteds6-rc: info: service certsync-log successfully starteds6-rc: info: service prepare successfully starteds6-rc: info: service go2rtc: startings6-rc: info: service go2rtc successfully starteds6-rc: info: service go2rtc-healthcheck: startings6-rc: info: service frigate: startings6-rc: info: service go2rtc-healthcheck successfully starteds6-rc: info: service frigate successfully starteds6-rc: info: service nginx: startings6-rc: info: service nginx successfully starteds6-rc: info: service certsync: startings6-rc: info: service certsync successfully starteds6-rc: info: service legacy-services: startings6-rc: info: service legacy-services successfully started2026-06-29 20:03:06.916540896 [2026-06-29 20:03:06] frigate.record.maintainer INFO : Exiting recording maintenance...2026-06-29 20:03:06.963346576 [2026-06-29 20:03:06] frigate.app INFO : Detection queue closed2026-06-29 20:03:07.464434414 [2026-06-29 20:03:07] frigate.app INFO : Detected frames queue closed2026-06-29 20:03:07.965491043 [2026-06-29 20:03:07] frigate.app INFO : Timeline queue closed2026-06-29 20:03:08.433575419 [2026-06-29 20:03:08] frigate.comms.ws INFO : Exiting websocket client...2026-06-29 20:03:08.924227189 [2026-06-29 20:03:08] peewee.sqliteq INFO : writer received shutdown request, exiting.2026-06-29 20:03:09.595304728 [INFO] Service Frigate exited with code 0 (by signal 0)2026-06-29 20:03:09.598518464 exit with signal: terminated2026-06-29 20:03:09.606208760 [INFO] The go2rtc service exited with code 0 (by signal 0)2026-06-29 20:03:13.831539599 [INFO] Starting NGINX...2026-06-29 20:03:13.918619515 [INFO] Preparing Frigate...2026-06-29 20:03:14.278419744 [INFO] Preparing new go2rtc config...2026-06-29 20:03:14.357538598 [INFO] Starting Frigate...2026-06-29 20:03:14.729370752 [INFO] Starting go2rtc...2026-06-29 20:03:15.135468780 20:03:15.132 INF go2rtc platform=linux/amd64 revision=df95ce3 version=1.9.102026-06-29 20:03:15.135474080 20:03:15.133 INF config path=/config/go2rtc_homekit.yml2026-06-29 20:03:15.135476464 20:03:15.133 INF [rtsp] listen addr=:85542026-06-29 20:03:15.135478809 20:03:15.134 INF [api] listen addr=:19842026-06-29 20:03:15.135481063 20:03:15.134 INF [webrtc] listen addr=:85552026-06-29 20:03:15.321143591 [INFO] Starting certsync...2026-06-29 20:03:15.896723589 127.0.0.1 - - [29/Jun/2026:20:03:15 +0930] "" 400 0 "-" "-" "-" request_time="0.000" upstream_response_time="-"2026-06-29 20:03:18.647144947 2026/06/29 20:03:18 [error] 288#288: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"2026-06-29 20:03:18.647170786 2026/06/29 20:03:18 [error] 288#288: *2 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"2026-06-29 20:03:18.984423628 [2026-06-29 20:03:18] frigate.util.config INFO : Checking if frigate config needs migration...2026-06-29 20:03:18.988220419 [2026-06-29 20:03:18] frigate.util.config INFO : frigate config does not need migration...2026-06-29 20:03:20.032561495 [2026-06-29 20:03:20] frigate.util.services INFO : Automatically detected nvidia hwaccel for video decoding2026-06-29 20:03:20.044798352 [2026-06-29 20:03:20] frigate.app INFO : Starting Frigate (0.17.2-3d4dd3a)2026-06-29 20:03:20.052265311 [2026-06-29 20:03:20] peewee_migrate.logs INFO : Starting migrations2026-06-29 20:03:20.053442950 [2026-06-29 20:03:20] peewee_migrate.logs INFO : There is nothing to migrate2026-06-29 20:03:20.077129070 [2026-06-29 20:03:20] frigate.app INFO : Recording process started: 7142026-06-29 20:03:20.089310712 [2026-06-29 20:03:20] frigate.app INFO : Review process started: 7152026-06-29 20:03:20.092242821 [2026-06-29 20:03:20] frigate.app INFO : go2rtc process pid: 1712026-06-29 20:03:20.107554089 [2026-06-29 20:03:20] frigate.app INFO : Embedding process started: 7292026-06-29 20:03:20.139370245 [2026-06-29 20:03:20] frigate.detectors WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.2026-06-29 20:03:20.141948438 [2026-06-29 20:03:20] frigate.app INFO : Output process started: 7612026-06-29 20:03:20.142368170 INFO: Created TensorFlow Lite XNNPACK delegate for CPU.2026-06-29 20:03:20.310334966 [2026-06-29 20:03:20] frigate.api.fastapi_app INFO : Starting FastAPI app2026-06-29 20:03:20.477175913 [2026-06-29 20:03:20] frigate.api.fastapi_app INFO : FastAPI started2026-06-29 20:03:23.830692932 [INFO] Starting go2rtc healthcheck service...2026-06-29 20:04:16.001587468 127.0.0.1 - - [29/Jun/2026:20:04:16 +0930] "" 400 0 "-" "-" "-" request_time="0.000" upstream_response_time="-"From your logs, I notice that Frigate is starting successfully, but I don't see any specific detector initialization logs that would indicate whether the YOLOv9 model is loading correctly. The logs show the detector process starting but don't show model compilation or loading details.Check your config file and check if the model file is in the correct place.
June 29Jun 29 8 hours ago, yayitazale said:From your logs, I notice that Frigate is starting successfully, but I don't see any specific detector initialization logs that would indicate whether the YOLOv9 model is loading correctly. The logs show the detector process starting but don't show model compilation or loading details.Check your config file and check if the model file is in the correct place.Yes I haven’t gotten as far as setting up the detector because I’m getting the 400 error when trying to access the UI.
June 29Jun 29 From what I can work out the internal port mapping is not correct. But am not sure how to resolve it purely because I haven’t changed anything in regards the initial set up. I haven’t changed any ports or anything like that.
June 30Jun 30 Author 9 hours ago, JWMutant said:From what I can work out the internal port mapping is not correct. But am not sure how to resolve it purely because I haven’t changed anything in regards the initial set up. I haven’t changed any ports or anything like that.I cannot help you without more info, can you share a screenshot of the configuration of the container and the configuration file (config.yaml) created during the initial startup?
June 30Jun 30 I worked out what the problem was/is.Frigate 0.17 serves the UI over HTTPS on port 8971, not HTTP. But when you left click on the Frigate docker and select webui it automatically launches a new webpage as http://192.168.178.22:8971. But what it should be doing is opening a new webpage as https://192.168.178.22:8971.I get the warning but at least I can open it now.Not sure if it is defaulting the new webpage to http because of something on my end or if its how the docker does things. Edited June 30Jun 30 by JWMutant
June 30Jun 30 Author 10 minutes ago, JWMutant said:I worked out what the problem was/is.Frigate 0.17 serves the UI over HTTPS on port 8971, not HTTP. But when you left click on the Frigate docker and select webui it automatically launches a new webpage as http://192.168.178.22:8971. But what it should be doing is opening a new webpage as https://192.168.178.22:8971.I get the warning but at least I can open it now.Not sure if it is defaulting the new webpage to http because of something on my end or if its how the docker does things.https://docs.frigate.video/frigate/installation#ports8971Authenticated UI and API access without TLS. Reverse proxies should use this port.EDIT: You're right, https://docs.frigate.video/configuration/tls, so I just modified the template so that future new installations will use HTTPS by default for the web UI. Thanks Edited June 30Jun 30 by yayitazale
June 30Jun 30 52 minutes ago, yayitazale said:https://docs.frigate.video/frigate/installation#ports8971Authenticated UI and API access without TLS. Reverse proxies should use this port.Thanks very very much for your help and patients.I think I am almost there.For the record when it comes to using my 1080ti I have the following config.But I dont think I have something set up correctly as I am getting the following error : 2026-06-30 17:21:29.010640640 2026-06-30 17:21:29.010578883 [W:onnxruntime:, transformer_memcpy.cc:83 ApplyImpl] 14 Memcpy nodes are added to the graph main_graph for CUDAExecutionProvider. It might have negative impact on performance (including unable to run CUDA graph). Set session_options.log_severity_level=1 to see the detail logs before this message.2026-06-30 17:21:29.013960480 2026-06-30 17:21:29.013926115 [E:onnxruntime:, inference_session.cc:2094 Initialize] This session cannot use the graph capture feature as requested by the user as all compute graph nodes have not been partitioned to the CUDAExecutionProvider2026-06-30 17:21:29.021954998 Process frigate.detector:onnx:2026-06-30 17:21:29.021960147 Traceback (most recent call last):2026-06-30 17:21:29.021962161 File "/usr/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap2026-06-30 17:21:29.021963434 self.run()2026-06-30 17:21:29.021965027 File "/opt/frigate/frigate/object_detection/base.py", line 143, in run2026-06-30 17:21:29.021966590 object_detector = LocalObjectDetector(detector_config=self.detector_config)2026-06-30 17:21:29.021971950 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.021997579 File "/opt/frigate/frigate/object_detection/base.py", line 62, in init2026-06-30 17:21:29.021998992 self.detect_api = create_detector(detector_config)2026-06-30 17:21:29.022000124 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022035772 File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector2026-06-30 17:21:29.022036844 return api(detector_config)2026-06-30 17:21:29.022037886 ^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022039108 File "/opt/frigate/frigate/detectors/plugins/onnx.py", line 39, in init2026-06-30 17:21:29.022058646 self.runner = get_optimized_runner(2026-06-30 17:21:29.022059738 ^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022061020 File "/opt/frigate/frigate/detectors/detection_runners.py", line 592, in get_optimized_runner2026-06-30 17:21:29.022062042 ort.InferenceSession(2026-06-30 17:21:29.022063535 File "/usr/local/lib/python3.11/dist-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 472, in init2026-06-30 17:21:29.022064797 self._create_inference_session(providers, provider_options, disabled_optimizers)2026-06-30 17:21:29.022066471 File "/usr/local/lib/python3.11/dist-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 561, in createinference_session2026-06-30 17:21:29.022087260 sess.initialize_session(providers, provider_options, disabled_optimizers)2026-06-30 17:21:29.022089625 onnxruntime.capi.onnxruntime_pybind11_state.Fail: [ONNXRuntimeError] : 1 : FAIL : This session cannot use the graph capture feature as requested by the user as all compute graph nodes have not been partitioned to the CUDAExecutionProvidermqtt: enabled: false ffmpeg: hwaccel_args: preset-nvidia detectors: onnx: type: onnx device: GPU-6174797f-a41e-9293-c52f-5abb9464f868 providers: - CUDAExecutionProvider cuda_graphs: false model: path: /config/model_cache/yolov9-t-320.onnx model_type: yolo-generic width: 320 height: 320 input_tensor: nchw input_dtype: float labelmap_path: /labelmap/coco-80.txt
June 30Jun 30 Author 13 minutes ago, JWMutant said:Thanks very very much for your help and patients.I think I am almost there.For the record when it comes to using my 1080ti I have the following config.But I dont think I have something set up correctly as I am getting the following error :2026-06-30 17:21:29.010640640 2026-06-30 17:21:29.010578883 [W:onnxruntime:, transformer_memcpy.cc:83 ApplyImpl] 14 Memcpy nodes are added to the graph main_graph for CUDAExecutionProvider. It might have negative impact on performance (including unable to run CUDA graph). Set session_options.log_severity_level=1 to see the detail logs before this message.2026-06-30 17:21:29.013960480 2026-06-30 17:21:29.013926115 [E:onnxruntime:, inference_session.cc:2094 Initialize] This session cannot use the graph capture feature as requested by the user as all compute graph nodes have not been partitioned to the CUDAExecutionProvider2026-06-30 17:21:29.021954998 Process frigate.detector:onnx:2026-06-30 17:21:29.021960147 Traceback (most recent call last):2026-06-30 17:21:29.021962161 File "/usr/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap2026-06-30 17:21:29.021963434 self.run()2026-06-30 17:21:29.021965027 File "/opt/frigate/frigate/object_detection/base.py", line 143, in run2026-06-30 17:21:29.021966590 object_detector = LocalObjectDetector(detector_config=self.detector_config)2026-06-30 17:21:29.021971950 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.021997579 File "/opt/frigate/frigate/object_detection/base.py", line 62, in init2026-06-30 17:21:29.021998992 self.detect_api = create_detector(detector_config)2026-06-30 17:21:29.022000124 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022035772 File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector2026-06-30 17:21:29.022036844 return api(detector_config)2026-06-30 17:21:29.022037886 ^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022039108 File "/opt/frigate/frigate/detectors/plugins/onnx.py", line 39, in init2026-06-30 17:21:29.022058646 self.runner = get_optimized_runner(2026-06-30 17:21:29.022059738 ^^^^^^^^^^^^^^^^^^^^^2026-06-30 17:21:29.022061020 File "/opt/frigate/frigate/detectors/detection_runners.py", line 592, in get_optimized_runner2026-06-30 17:21:29.022062042 ort.InferenceSession(2026-06-30 17:21:29.022063535 File "/usr/local/lib/python3.11/dist-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 472, in init2026-06-30 17:21:29.022064797 self._create_inference_session(providers, provider_options, disabled_optimizers)2026-06-30 17:21:29.022066471 File "/usr/local/lib/python3.11/dist-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 561, in createinference_session2026-06-30 17:21:29.022087260 sess.initialize_session(providers, provider_options, disabled_optimizers)2026-06-30 17:21:29.022089625 onnxruntime.capi.onnxruntime_pybind11_state.Fail: [ONNXRuntimeError] : 1 : FAIL : This session cannot use the graph capture feature as requested by the user as all compute graph nodes have not been partitioned to the CUDAExecutionProvidermqtt:enabled: false ffmpeg:hwaccel_args: preset-nvidia detectors:onnx: type: onnx device: GPU-6174797f-a41e-9293-c52f-5abb9464f868 providers: - CUDAExecutionProvider cuda_graphs: false model:path: /config/model_cache/yolov9-t-320.onnxmodel_type: yolo-genericwidth: 320height: 320input_tensor: nchwinput_dtype: floatlabelmap_path: /labelmap/coco-80.txt Not sure but I think you don't need this:providers: - CUDAExecutionProvider cuda_graphs: falsehttps://github.com/blakeblackshear/frigate/discussions/23546#discussioncomment-17412679 Edited June 30Jun 30 by yayitazale
June 30Jun 30 Turns out it was the detector model I was using.I was using yolov9, after switching to v8 it started working just fine.
Wednesday at 08:17 AM5 days Author 13 hours ago, JWMutant said:Turns out it was the detector model I was using.I was using yolov9, after switching to v8 it started working just fine.Did you created a V9 model?
Wednesday at 10:02 AM5 days On 5/13/2026 at 3:31 PM, Glodenox said:I ran into an issue where the Docker container didn't want to start any more after the upgrade to Unraid 7.3.0, with the following error:Error response from daemon: error while creating mount source path '/etc/localtime': mkdir /etc/localtime: file existsIn the end, it turned out that the /etc/localtime symlink on my Unraid instance was pointing towards a file in /usr/share/zoneinfo/ that doesn't exist (any more?). Changing the timezone of the Unraid instance in the settings fixed that reference, and as such fixed the docker bind mount. I hope it helps someone else, so they don't lose half an hour trying to figure this out as well.Either way, this doesn't seem like a bug with the container. I'm not sure if it is fully related to 7.3.0, but that's what things seem to point to for me.Just to be sure: Did you create a ticket for that issue?
Wednesday at 11:10 AM5 days Author 1 hour ago, p0p said:Just to be sure: Did you create a ticket for that issue?I think the problem resides on the Unraid side, not on the container side. Edited Wednesday at 11:11 AM5 days by yayitazale
Wednesday at 11:27 AM5 days I had a similar issue when 7.3.x came up and i had to add this key to the frigate docker:-faxxe
Wednesday at 08:18 PM5 days On 6/30/2026 at 4:26 PM, yayitazale said:https://docs.frigate.video/frigate/installation#ports8971Authenticated UI and API access without TLS. Reverse proxies should use this port.EDIT: You're right, https://docs.frigate.video/configuration/tls, so I just modified the template so that future new installations will use HTTPS by default for the web UI.ThanksAll good. Happy to help resolve it to the communities benefit.. I’m still having problems with the tensor docker when it comes to recording footage and am pretty sure by now that it’s not my config. But after trying to problem solve for the past 3 days I’m giving it a break for a day before I tackle it again.It’s basically not capturing any footage.Any in regards to your earlier question I stupidly downloaded a pre-compiled yolov9 which was the original issue with the detector not working. After compiling. V8 myself I had no more problems
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.