yayitazale Posted September 5 Author Share Posted September 5 (edited) 14 hours ago, MTerracciano said: Hi, I installed a 2nd GPU in my machine (nvidia M2000) to take the load off my larger GPU, I updated the GPUID in the frigate container template but it's still using my original GPU, any idea what could be wrong here? Are you launching the container in privileged mode? Try in not privileged mode first. Otherwise try adding a new environmental variable: CUDA_VISIBLE_DEVICES=1 The value is the index of the GPU as seen by the container. Edited September 5 by yayitazale Quote Link to comment
MTerracciano Posted September 5 Share Posted September 5 16 hours ago, yayitazale said: Are you launching the container in privileged mode? Try in not privileged mode first. Otherwise try adding a new environmental variable: CUDA_VISIBLE_DEVICES=1 The value is the index of the GPU as seen by the container. I actually abandoned the idea, turns out the M2000 barely uses less power than my GTX1070 when running frigate and compreface, 33W vs. 17W so I can't really justify having a separate GPU, really thought I'd be saving more energy 1 Quote Link to comment
matew Posted September 9 Share Posted September 9 Hi, is anybody else experiencing issues after upgrading Frigate container to ver 0.14 during ffmpeg decoding using iGPU the whole container starts to be unresponsive and iGPU crashes as well? Meaning to output from the onboard graphic card. In case you are using GPU statistics plugin this causes as well GUI unresponsiveness. Setup is AMD ryzen 7900. Unraid version 6.12.10. With older version of Frigate there were no issues, it was stable for months. Quote Link to comment
ConnerVT Posted September 9 Share Posted September 9 5600GT and 6.12.11 - No issues seen here. Currently running only 3 cameras. I also run GPU Stats, and it reports the iGPU usage between 0.8 and 2.5%. Quote Link to comment
yayitazale Posted September 9 Author Share Posted September 9 36 minutes ago, matew said: Hi, is anybody else experiencing issues after upgrading Frigate container to ver 0.14 during ffmpeg decoding using iGPU the whole container starts to be unresponsive and iGPU crashes as well? Meaning to output from the onboard graphic card. In case you are using GPU statistics plugin this causes as well GUI unresponsiveness. Setup is AMD ryzen 7900. Unraid version 6.12.10. With older version of Frigate there were no issues, it was stable for months. https://github.com/blakeblackshear/frigate/issues/8470#issuecomment-2337858655 Quote Link to comment
i-B4se Posted September 11 Share Posted September 11 Hello, maybe someone can help me. My frigate docker no longer starts properly after I updated unraid and frigate. Frigate Version: last stable Unraid version: 6.12.13 If i hit "start" it will go to an reboot loop 2024-09-11 20:21:20.604014796 [INFO] Preparing Frigate... 2024-09-11 20:21:20.605006474 [INFO] Starting NGINX... 2024-09-11 20:21:20.610554256 [INFO] Preparing new go2rtc config... 2024-09-11 20:21:20.620547933 [INFO] Starting Frigate... 2024-09-11 20:21:20.900755159 [INFO] Starting go2rtc... 2024-09-11 20:21:20.989145189 20:21:20.989 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2 2024-09-11 20:21:20.989152243 20:21:20.989 INF config path=/dev/shm/go2rtc.yaml 2024-09-11 20:21:20.989462688 20:21:20.989 INF [rtsp] listen addr=:XXXX 2024-09-11 20:21:20.989801419 20:21:20.989 INF [api] listen addr=:XXXX 2024-09-11 20:21:20.989888442 20:21:20.989 INF [webrtc] listen addr=:XXXX/tcp s6-rc: info: service nginx successfully started s6-rc: info: service certsync: starting s6-rc: info: service certsync successfully started s6-rc: info: service legacy-services: starting 2024-09-11 20:21:21.701488661 [INFO] Starting certsync... s6-rc: info: service legacy-services successfully started 2024-09-11 20:21:21.731178802 [2024-09-11 20:21:21] frigate.app INFO : Starting Frigate (0.14.1-f4f3cfa) 2024-09-11 20:21:21.731242149 [2024-09-11 20:21:21] frigate.util.config INFO : Checking if frigate config needs migration... 2024-09-11 20:21:21.769712403 127.0.0.1 - - [11/Sep/2024:20:21:21 +0200] "" 400 0 "-" "-" "-" 2024-09-11 20:21:21.775685101 [2024-09-11 20:21:21] frigate.util.config INFO : frigate config does not need migration... 2024-09-11 20:21:21.799919651 ************************************************************* 2024-09-11 20:21:21.799925797 ************************************************************* 2024-09-11 20:21:21.799933409 *** Your config file is not valid! *** 2024-09-11 20:21:21.799938578 *** Please check the docs at *** 2024-09-11 20:21:21.799942419 *** https://docs.frigate.video/configuration/index *** 2024-09-11 20:21:21.799976013 ************************************************************* 2024-09-11 20:21:21.799980203 ************************************************************* 2024-09-11 20:21:21.799985022 *** Config Validation Errors *** 2024-09-11 20:21:21.799989213 ************************************************************* 2024-09-11 20:21:21.800019035 ui.use_experimental: Extra inputs are not permitted 2024-09-11 20:21:21.800022806 record.events.required_zones: Extra inputs are not permitted 2024-09-11 20:21:21.800027067 ************************************************************* 2024-09-11 20:21:21.800031327 *** End Config Validation Errors *** 2024-09-11 20:21:21.800035587 ************************************************************* 2024-09-11 20:21:23.065697133 [INFO] Service Frigate exited with code 1 (by signal 0) s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service go2rtc-healthcheck: stopping s6-rc: info: service certsync: stopping 2024-09-11 20:21:23.078514918 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15) s6-rc: info: service go2rtc-healthcheck successfully stopped 2024-09-11 20:21:23.080638725 [INFO] Service CERTSYNC exited with code 256 (by signal 15) s6-rc: info: service certsync successfully stopped s6-rc: info: service nginx: stopping s6-rc: info: service certsync-log: stopping s6-rc: info: service certsync-log successfully stopped 2024-09-11 20:21:23.130114240 [INFO] Service NGINX exited with code 0 (by signal 0) s6-rc: info: service nginx successfully stopped s6-rc: info: service nginx-log: stopping s6-rc: info: service frigate: stopping s6-rc: info: service frigate successfully stopped s6-rc: info: service go2rtc: stopping s6-rc: info: service frigate-log: stopping s6-rc: info: service nginx-log successfully stopped 2024-09-11 20:21:23.134485823 exit with signal: terminated s6-rc: info: service frigate-log successfully stopped 2024-09-11 20:21:23.140425346 [INFO] The go2rtc service exited with code 0 (by signal 0) s6-rc: info: service go2rtc successfully stopped s6-rc: info: service go2rtc-log: stopping s6-rc: info: service go2rtc-log successfully stopped s6-rc: info: service log-prepare: stopping s6-rc: info: service s6rc-fdholder: stopping s6-rc: info: service log-prepare successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service s6rc-fdholder successfully stopped s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped I haven't changed anything except updating Unraid and frigate. Thank you Quote Link to comment
ConnerVT Posted September 11 Share Posted September 11 I would comment these two out of your config.yaml file. My best guess and 5 minutes of Googling make me think that they are not supported and/or no longer needed in 0.14. 3 hours ago, i-B4se said: 2024-09-11 20:21:21.799976013 ************************************************************* 2024-09-11 20:21:21.799980203 ************************************************************* 2024-09-11 20:21:21.799985022 *** Config Validation Errors *** 2024-09-11 20:21:21.799989213 ************************************************************* 2024-09-11 20:21:21.800019035 ui.use_experimental: Extra inputs are not permitted 2024-09-11 20:21:21.800022806 record.events.required_zones: Extra inputs are not permitted 2024-09-11 20:21:21.800027067 ************************************************************* 2024-09-11 20:21:21.800031327 *** End Config Validation Errors *** 2024-09-11 20:21:21.800035587 ************************************************************* 1 Quote Link to comment
John Graham Posted September 12 Share Posted September 12 time for me to have another question: i have seen a lot of people are using "go2rtc" i am not .. 1) is Go2RTC built in to Frigate? 2) i see un-raid has a docker for go2rtc can we use that? 3) here is what i tried and did not working: (Added this to the Frigate config and all worked goot) go2rtc: streams: Front_Door: - rtsp://+++:[email protected]:88/videoMain Porch_Swing: - rtsp://++++:[email protected]:88/videoMain Camera_Number-3: - rtsp://+++:[email protected]:88/videoMain Camera_Number-4: - rtsp://++++:[email protected]:88/videoMain Back_Yard: - rtsp://++++:[email protected]:554/1/mpeg4 now chaned this from : a_Frount_Door: # <------ Name the camera enabled: true ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: Front_Door: roles: - detect Is this all i NEEED??? thank as always OvO Quote Link to comment
yayitazale Posted September 12 Author Share Posted September 12 12 hours ago, John Graham said: time for me to have another question: i have seen a lot of people are using "go2rtc" i am not .. 1) is Go2RTC built in to Frigate? 2) i see un-raid has a docker for go2rtc can we use that? 3) here is what i tried and did not working: (Added this to the Frigate config and all worked goot) go2rtc: streams: Front_Door: - rtsp://+++:[email protected]:88/videoMain Porch_Swing: - rtsp://++++:[email protected]:88/videoMain Camera_Number-3: - rtsp://+++:[email protected]:88/videoMain Camera_Number-4: - rtsp://++++:[email protected]:88/videoMain Back_Yard: - rtsp://++++:[email protected]:554/1/mpeg4 now chaned this from : a_Frount_Door: # <------ Name the camera enabled: true ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: Front_Door: roles: - detect Is this all i NEEED??? thank as always OvO Hi: You have all the info in the docs: https://docs.frigate.video/guides/configuring_go2rtc Yes it is embedded into the container so you can use it just configuring it in the config file. Quote Link to comment
kcmccombs Posted September 13 Share Posted September 13 ok back with a little more info on my problem trying to find out why frigate seems to be dropping frames in the browser i looked in the browser developer tools and i can see this under the network tab any help would be great. thanks Quote Link to comment
awediohead Posted Monday at 12:04 PM Share Posted Monday at 12:04 PM (edited) Update: OK so without changing anything in the set up file I changed the url to http and changed the port to 5000 so now it works, but when you choose the webui for Frigate you get 'bad request' - how to fix this please? I'm probably doing something dumb - I had Frigate 0.14 working pretty well having just upgraded it from previous versions within Unraid's Docker Window, then I noticed the recommendation to delete and do a fresh install for 0.14 which I hadn't done - so I saved my config.yaml file and now I have a login screen which I didn't have previously? The only change I made was to add a Frigate+ API key in the relevant field, but my Frigate+ login credentials return as invalid, though they work to sign me in the the Frigate+ website. The other thing I notice is the "Authenticated UI and API access without TLS. Reverse proxies should use this port: 8971 - but I don't have a reverse proxy ? The old HTTP port of 5000 is missing from the set up - should I add it back? Edited Monday at 12:11 PM by awediohead more info Quote Link to comment
yayitazale Posted Monday at 06:10 PM Author Share Posted Monday at 06:10 PM 6 hours ago, awediohead said: Update: OK so without changing anything in the set up file I changed the url to http and changed the port to 5000 so now it works, but when you choose the webui for Frigate you get 'bad request' - how to fix this please? I'm probably doing something dumb - I had Frigate 0.14 working pretty well having just upgraded it from previous versions within Unraid's Docker Window, then I noticed the recommendation to delete and do a fresh install for 0.14 which I hadn't done - so I saved my config.yaml file and now I have a login screen which I didn't have previously? The only change I made was to add a Frigate+ API key in the relevant field, but my Frigate+ login credentials return as invalid, though they work to sign me in the the Frigate+ website. The other thing I notice is the "Authenticated UI and API access without TLS. Reverse proxies should use this port: 8971 - but I don't have a reverse proxy ? The old HTTP port of 5000 is missing from the set up - should I add it back? Please read the changelog and the docs. https://github.com/blakeblackshear/frigate/releases/tag/v0.14.0 https://docs.frigate.video/ Quote Link to comment
mesencephalon Posted Tuesday at 02:39 AM Share Posted Tuesday at 02:39 AM I am trying to set up Frigate on UNRAID. My system is a Dell R740XD Xeon Gold 6148 with Intel Arc Pro A40 GPU. OpenVino with GPU setting gives me errors. This user (topic is below) has a work around to make it work but in Proxmox and this is the problem statement; Intel Compute is a dependency for OpenVino in Frigate, and it needs to be updated to the latest version in order to use the latest kernel; https://github.com/blakeblackshear/frigate/issues/12266#issuecomment-2328314441. Can somebody help me how to do it on UNRAID? I downloaded the required packages on UNRAID terminal connecting to the docker but I am not sure how can I repack these packages with a script on UNRAID as this user mentioned this on Proxmox. I am not able to install ztsd in docker to repack. Quote Link to comment
Kilrah Posted Tuesday at 08:33 AM Share Posted Tuesday at 08:33 AM 5 hours ago, mesencephalon said: I am trying to set up Frigate on UNRAID. My system is a Dell R740XD Xeon Gold 6148 with Intel Arc Pro A40 GPU. OpenVino with GPU setting gives me errors. Are you on unraid 7 beta? 6.x does not support Arc. Quote Link to comment
mesencephalon Posted Tuesday at 11:15 AM Share Posted Tuesday at 11:15 AM (edited) 2 hours ago, Kilrah said: Are you on unraid 7 beta? 6.x does not support Arc. Yes, my GPU works great with Plex already. I am on unraid 7 beta 2. Edited Tuesday at 11:16 AM by mesencephalon Quote Link to comment
Bruceflix Posted Tuesday at 11:59 PM Share Posted Tuesday at 11:59 PM 12 hours ago, mesencephalon said: Yes, my GPU works great with Plex already. Off-topic but that is great to hear. Next upgrade has plans for arc to replace my 1050ti Quote Link to comment
Recommended Posts
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.