mikey6283 Posted September 23, 2022 Share Posted September 23, 2022 4 minutes ago, yayitazale said: I was asking for a image of the container itself like so: sorry Quote Link to comment
yayitazale Posted September 23, 2022 Author Share Posted September 23, 2022 43 minutes ago, mikey6283 said: sorry As I see you are not using nvidia, so can you delete the extra parameter --gpus=all switching to the advanced view mode in there. Quote Link to comment
mikey6283 Posted September 23, 2022 Share Posted September 23, 2022 3 minutes ago, yayitazale said: As I see you are not using nvidia, so can you delete the extra parameter --gpus=all switching to the advanced view mode in there. Sorry but i am unsure which parameter to delete ? is it the intel AMD gpu mapping ? Quote Link to comment
yayitazale Posted September 23, 2022 Author Share Posted September 23, 2022 Just now, mikey6283 said: Sorry but i am unsure which parameter to delete ? is it the intel AMD gpu mapping ? Quote Link to comment
mikey6283 Posted September 23, 2022 Share Posted September 23, 2022 22 minutes ago, yayitazale said: Thank you started, now i need to sort the Config out. Quote Link to comment
Caennanu Posted September 25, 2022 Share Posted September 25, 2022 (edited) I'm sorry if it was mentioned before, but after reading 6 pages i gave up... Has there been a solution yet to passing through the Coral TPU to an VM? NM... figured it out, by editting the XML using this guide. https://www.smsprojects.co.uk/video-unraid-pass-through-hardware-3-ways-to-do-it/ Edited September 25, 2022 by Caennanu 1 Quote Link to comment
digiblur Posted September 26, 2022 Share Posted September 26, 2022 On 9/23/2022 at 2:08 AM, yayitazale said: v11.0 has been released and the new template uploaded. Remember, you must uninstall the old APP what ever your flavor was (standard or nvidia) and install the new unified APP from CA store. Is `<Privileged>true</Privileged>` necessary for most installs? Definitely not a good security practice IMHO. Quote Link to comment
yayitazale Posted September 26, 2022 Author Share Posted September 26, 2022 3 minutes ago, digiblur said: Is `<Privileged>true</Privileged>` necessary for most installs? Definitely not a good security practice IMHO. As I assume that most of the people is using coral TPUs yes, it is a necessary concession. https://github.com/blakeblackshear/frigate/issues/165 https://github.com/blakeblackshear/frigate/issues/171 https://github.com/blakeblackshear/frigate/issues/325 I changed the template to not privileged mode as default in the past but most of the people complained about their TPUs not working and they are not use to change the docker deploy gui to advanced mode. Quote Link to comment
robse Posted September 29, 2022 Share Posted September 29, 2022 (edited) Hi eveybody, I would like to try Frigate but i cannot get it up and running. I am not using Home Assistant but iobroker and like to use the mqtt server provided by iobroker. Please find my config attached. Edited September 29, 2022 by robse Attached log Quote Link to comment
yayitazale Posted September 29, 2022 Author Share Posted September 29, 2022 (edited) 59 minutes ago, robse said: Hi eveybody, I would like to try Frigate but i cannot get it up and running. I am not using Home Assistant but iobroker and like to use the mqtt server provided by iobroker. Please find my config attached. I think the problem is the port, you have to declare it below the IP with the entry "port: 1884" (or just not declare it as you are using the default port), but maybe you have more things to fix. I suggest you for a easier start at the beginning to use the complete example config.yml example of the docs as a template: https://docs.frigate.video/configuration/index Edited September 29, 2022 by yayitazale Quote Link to comment
robse Posted September 30, 2022 Share Posted September 30, 2022 17 hours ago, yayitazale said: I think the problem is the port, you have to declare it below the IP with the entry "port: 1884" (or just not declare it as you are using the default port), but maybe you have more things to fix. I suggest you for a easier start at the beginning to use the complete example config.yml example of the docs as a template: https://docs.frigate.video/configuration/index Thanks, the problem was the port declaration. Quote Link to comment
MasterOfPuppets111 Posted September 30, 2022 Share Posted September 30, 2022 (edited) I dont get the frigate docker to work with the minimal configuration.... Steps I did: -install mosquitto (as unraid docker) -install frigate container Create a config.yml with the following content: mqtt: host: (ip of the unraid server) cameras: back: ffmpeg: inputs: - path: (rtsp stream that works in the vlc player) roles: - detect - rtmp detect: width: 1280 height: 720 But I get the following error in the frigate log: When I start the frigate docker it stopped after a few seconds.... EDIT: Okay i just get it to work, i uninstalled mosquitto and installed mqtt. Edited October 1, 2022 by MasterOfPuppets111 1 Quote Link to comment
joersch Posted October 7, 2022 Share Posted October 7, 2022 Hi! I have frigate working quite well now with an Anke C800 and Coral USB. One thing is annoying: somewhen during night the container is stopped. First suspect was "Backup/Restore Appdata" Plugin, that is backing up my AppData each night at 3. First this was the case, but as frigate stores only the config in AppData no stop for backup is necessary. before: Oct 3 03:00:01 datenhaufen CA Backup/Restore: Stopping frigate Oct 3 03:00:05 datenhaufen kernel: docker0: port 1(vethc84b59a) entered disabled state Oct 3 03:00:05 datenhaufen kernel: vethf852a89: renamed from eth0 Oct 3 03:00:05 datenhaufen avahi-daemon[8102]: Interface vethc84b59a.IPv6 no longer relevant for mDNS. Oct 3 03:00:05 datenhaufen avahi-daemon[8102]: Leaving mDNS multicast group on interface vethc84b59a.IPv6 with address fe80::38bc:a9ff:fe6c:49d0. Oct 3 03:00:05 datenhaufen kernel: docker0: port 1(vethc84b59a) entered disabled state Oct 3 03:00:05 datenhaufen kernel: device vethc84b59a left promiscuous mode Oct 3 03:00:05 datenhaufen kernel: docker0: port 1(vethc84b59a) entered disabled state Oct 3 03:00:05 datenhaufen avahi-daemon[8102]: Withdrawing address record for fe80::38bc:a9ff:fe6c:49d0 on vethc84b59a. Oct 3 03:00:05 datenhaufen CA Backup/Restore: docker stop -t 60 frigate after: Oct 4 03:00:01 datenhaufen CA Backup/Restore: ####################################### Oct 4 03:00:01 datenhaufen CA Backup/Restore: Community Applications appData Backup Oct 4 03:00:01 datenhaufen CA Backup/Restore: Applications will be unavailable during Oct 4 03:00:01 datenhaufen CA Backup/Restore: this process. They will automatically Oct 4 03:00:01 datenhaufen CA Backup/Restore: be restarted upon completion. Oct 4 03:00:01 datenhaufen CA Backup/Restore: ####################################### Oct 4 03:00:01 datenhaufen CA Backup/Restore: frigate set to not be stopped by ca backup's advanced settings. Skipping Oct 4 03:00:01 datenhaufen CA Backup/Restore: Stopping iobroker But still the container is down in the morning. Last lines of the log (including manual restart): [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] done. [services.d] starting services [services.d] done. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] done. [services.d] starting services [services.d] done. Any ideas where I can dig into? Is there a chance to increase the logging of the container to show when/why it shut down? cheers Jörg Quote Link to comment
yayitazale Posted October 9, 2022 Author Share Posted October 9, 2022 On 10/7/2022 at 5:50 PM, joersch said: Hi! I have frigate working quite well now with an Anke C800 and Coral USB. One thing is annoying: somewhen during night the container is stopped. First suspect was "Backup/Restore Appdata" Plugin, that is backing up my AppData each night at 3. First this was the case, but as frigate stores only the config in AppData no stop for backup is necessary. before: Oct 3 03:00:01 datenhaufen CA Backup/Restore: Stopping frigate Oct 3 03:00:05 datenhaufen kernel: docker0: port 1(vethc84b59a) entered disabled state Oct 3 03:00:05 datenhaufen kernel: vethf852a89: renamed from eth0 Oct 3 03:00:05 datenhaufen avahi-daemon[8102]: Interface vethc84b59a.IPv6 no longer relevant for mDNS. Oct 3 03:00:05 datenhaufen avahi-daemon[8102]: Leaving mDNS multicast group on interface vethc84b59a.IPv6 with address fe80::38bc:a9ff:fe6c:49d0. Oct 3 03:00:05 datenhaufen kernel: docker0: port 1(vethc84b59a) entered disabled state Oct 3 03:00:05 datenhaufen kernel: device vethc84b59a left promiscuous mode Oct 3 03:00:05 datenhaufen kernel: docker0: port 1(vethc84b59a) entered disabled state Oct 3 03:00:05 datenhaufen avahi-daemon[8102]: Withdrawing address record for fe80::38bc:a9ff:fe6c:49d0 on vethc84b59a. Oct 3 03:00:05 datenhaufen CA Backup/Restore: docker stop -t 60 frigate after: Oct 4 03:00:01 datenhaufen CA Backup/Restore: ####################################### Oct 4 03:00:01 datenhaufen CA Backup/Restore: Community Applications appData Backup Oct 4 03:00:01 datenhaufen CA Backup/Restore: Applications will be unavailable during Oct 4 03:00:01 datenhaufen CA Backup/Restore: this process. They will automatically Oct 4 03:00:01 datenhaufen CA Backup/Restore: be restarted upon completion. Oct 4 03:00:01 datenhaufen CA Backup/Restore: ####################################### Oct 4 03:00:01 datenhaufen CA Backup/Restore: frigate set to not be stopped by ca backup's advanced settings. Skipping Oct 4 03:00:01 datenhaufen CA Backup/Restore: Stopping iobroker But still the container is down in the morning. Last lines of the log (including manual restart): [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] done. [services.d] starting services [services.d] done. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] done. [services.d] starting services [services.d] done. Any ideas where I can dig into? Is there a chance to increase the logging of the container to show when/why it shut down? cheers Jörg Did the plugin stop the MQTT container? If yes, maybe this is making to stop to frigate. Quote Link to comment
phithor Posted October 17, 2022 Share Posted October 17, 2022 Hi guys, I am trying to start using frigate with my coral usb tpu which i think i have been able to set up just fine for a basic setup. However, after some hours I am experiencing unraid system wide crash and this point I am afraid to try again. Please send help. Happened once when I pushed some buttons on the frigate gui and a second time during the night after 10hrs of uptime. The Unraid GUI and other apps, HA and ssh for example, is unreponsive and I have to hard reboot the machine via holding down the power button. Have any of you experiecned this before or know what can be the cause? Quote Link to comment
yayitazale Posted October 18, 2022 Author Share Posted October 18, 2022 18 hours ago, phithor said: Hi guys, I am trying to start using frigate with my coral usb tpu which i think i have been able to set up just fine for a basic setup. However, after some hours I am experiencing unraid system wide crash and this point I am afraid to try again. Please send help. Happened once when I pushed some buttons on the frigate gui and a second time during the night after 10hrs of uptime. The Unraid GUI and other apps, HA and ssh for example, is unreponsive and I have to hard reboot the machine via holding down the power button. Have any of you experiecned this before or know what can be the cause? I can't help you with no information about the configuration of your container and frigate instance. Quote Link to comment
phithor Posted October 18, 2022 Share Posted October 18, 2022 3 hours ago, yayitazale said: I can't help you with no information about the configuration of your container and frigate instance. OK understandable, please see container config and frigate config: mqtt: host: 192.168.0.90 port: 1884 topic_prefix: frigate client_id: frigate user: **** password: **** cameras: backyard: ffmpeg: inputs: - path: rtsp://admin:***@192.168.0.20:554/h264Preview_01_sub roles: - detect - rtmp detect: width: 640 height: 480 Dafang3: ffmpeg: inputs: - path: rtsp://192.168.0.98:8554/unicast roles: - detect - rtmp rtmp: enabled: False # <-- RTMP should be disabled if your stream is not H264 detect: width: 1280 # <---- update for your camera's resolution height: 720 # <---- update for your camera's resolution detectors: coral: type: edgetpu device: usb Thanks Quote Link to comment
yayitazale Posted October 19, 2022 Author Share Posted October 19, 2022 20 hours ago, phithor said: OK understandable, please see container config and frigate config: mqtt: host: 192.168.0.90 port: 1884 topic_prefix: frigate client_id: frigate user: **** password: **** cameras: backyard: ffmpeg: inputs: - path: rtsp://admin:***@192.168.0.20:554/h264Preview_01_sub roles: - detect - rtmp detect: width: 640 height: 480 Dafang3: ffmpeg: inputs: - path: rtsp://192.168.0.98:8554/unicast roles: - detect - rtmp rtmp: enabled: False # <-- RTMP should be disabled if your stream is not H264 detect: width: 1280 # <---- update for your camera's resolution height: 720 # <---- update for your camera's resolution detectors: coral: type: edgetpu device: usb Thanks First of all, I suggest you to uninstall that frigate APP as it has been changed for a new one on the APP store. As I see, you are using Intel/AMD hardware acceleration but you are not defining any FFMPEG arguments so please check out this part of the docs: https://docs.frigate.video/configuration/hardware_acceleration Other than that, I don't see anything wrong in your setup, so I don't see why is your system behaving like that. Maybe you can open a issue at github: https://github.com/blakeblackshear/frigate/issues Quote Link to comment
tigga69 Posted November 6, 2022 Share Posted November 6, 2022 (edited) Hi I need a little help which might just be clarification. I've got a Coral mini PCIe board. I've installed it OK into the hardware and it is seen by the PCIe bus. (see image below) The apex and gasget drivers are installed. (see below) BUT the apex drivers dont seem to recognise the Coral card and so it doesnt load for frigate. The drivers from @ich777 are just saying "No PCI based Coral TPU Devices found!" (which isnt a surprise because I can see the Apex driver isnt recognising the card. Quote Nov 3 21:18:34 SERVER-UR1 kernel: apex 0000:05:00.0: Cannot get BAR2 base address . . . Nov 3 21:18:34 SERVER-UR1 kernel: apex 0000:05:00.0: error adding gasket device Nov 3 21:18:34 SERVER-UR1 kernel: ahci 0000:07:00.0: SSS flag set, parallel bus scan disabled Nov 3 21:18:34 SERVER-UR1 kernel: ccp 0000:09:00.1: psp enabled Nov 3 21:18:34 SERVER-UR1 kernel: apex: probe of 0000:05:00.0 failed with error -12 So people in 2020 were saying you need to recomile the Apex and Gasket drivers. Question 1. Do we still need to compile new Apex and Gasket Drivers? I got most of the way through and lots were not working because so many bits needed extra install to work, so I thought I would ask... which is the best instructions to follow for the build? is it pgbtech on or DiabloXP on or Jaburges on some other combintion. (yes I know the build number needs to be the latest, but I need to know which sequence to follow!) thanks in advance for any advice, pointers, or direction. R. Quote Nov 3 21:19:01 SERVER-UR1 root: ---------------------------------------------------- Nov 3 21:19:01 SERVER-UR1 root: compose.manager has been installed. Nov 3 21:19:01 SERVER-UR1 root: Version: 2022.10.15 Nov 3 21:19:01 SERVER-UR1 root: ---------------------------------------------------- Nov 3 21:19:01 SERVER-UR1 root: Nov 3 21:19:01 SERVER-UR1 root: plugin: compose.manager.plg installed ### [PREVIOUS LINE REPEATED 1 TIMES] ### Nov 3 21:19:01 SERVER-UR1 root: Executing hook script: post_plugin_checks Nov 3 21:19:01 SERVER-UR1 root: plugin: installing: coral-driver.plg Nov 3 21:19:01 SERVER-UR1 root: Executing hook script: pre_plugin_checks Nov 3 21:19:01 SERVER-UR1 root: plugin: running: anonymous Nov 3 21:19:01 SERVER-UR1 root: plugin: checking: /boot/config/plugins/coral-driver/coral-driver-2022.07.21d.txz - MD5 Nov 3 21:19:01 SERVER-UR1 root: plugin: skipping: /boot/config/plugins/coral-driver/coral-driver-2022.07.21d.txz already exists Nov 3 21:19:01 SERVER-UR1 root: plugin: running: /boot/config/plugins/coral-driver/coral-driver-2022.07.21d.txz Nov 3 21:19:01 SERVER-UR1 root: Nov 3 21:19:01 SERVER-UR1 root: +============================================================================== Nov 3 21:19:01 SERVER-UR1 root: | Installing new package /boot/config/plugins/coral-driver/coral-driver-2022.07.21d.txz Nov 3 21:19:01 SERVER-UR1 root: +============================================================================== Nov 3 21:19:01 SERVER-UR1 root: Nov 3 21:19:01 SERVER-UR1 root: Verifying package coral-driver-2022.07.21d.txz. Nov 3 21:19:01 SERVER-UR1 root: Installing package coral-driver-2022.07.21d.txz: Nov 3 21:19:01 SERVER-UR1 root: PACKAGE DESCRIPTION: Nov 3 21:19:01 SERVER-UR1 root: Package coral-driver-2022.07.21d.txz installed. Nov 3 21:19:01 SERVER-UR1 root: plugin: creating: /usr/local/emhttp/plugins/coral-driver/README.md - from INLINE content Nov 3 21:19:01 SERVER-UR1 root: plugin: running: anonymous Nov 3 21:19:01 SERVER-UR1 root: Nov 3 21:19:01 SERVER-UR1 root: ---------------Coral Accelerator Module Drivers found locally---------------- Nov 3 21:19:01 SERVER-UR1 root: Nov 3 21:19:01 SERVER-UR1 root: --------Installation of Coral Accelerator Module Drivers successful---------- Nov 3 21:19:01 SERVER-UR1 root: Nov 3 21:19:01 SERVER-UR1 root: plugin: coral-driver.plg installed ### [PREVIOUS LINE REPEATED 1 TIMES] ### Nov 3 21:19:01 SERVER-UR1 root: Executing hook script: post_plugin_checks Nov 3 21:19:01 SERVER-UR1 root: plugin: installing: dynamix.system.temp.plg Nov 3 21:19:01 SERVER-UR1 root: Executing hook script: pre_plugin_checks Nov 3 21:19:01 SERVER-UR1 root: plugin: running: anonymous Nov 3 21:19:01 SERVER-UR1 root: plugin: checking: /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz - MD5 Nov 3 21:19:01 SERVER-UR1 root: plugin: skipping: /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz already exists Nov 3 21:19:01 SERVER-UR1 root: plugin: running: /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz Nov 3 21:19:01 SERVER-UR1 root: Edited November 6, 2022 by tigga69 Quote Link to comment
ich777 Posted November 6, 2022 Share Posted November 6, 2022 1 hour ago, tigga69 said: Question 1. Do we still need to compile new Apex and Gasket Drivers? This is done by me and the correct package for the correct Kernel version is then downloaded/installed on boot by the plugin. The drivers in your case are working fine, at least from what I can tell from your screenshots. 1 hour ago, tigga69 said: So people in 2020 were saying you need to recomile the Apex and Gasket drivers. Yes, but my plugin was released in 2021 (to be precise on 2021.02.19) and the posts that you've linked are all outdated since then. 1 hour ago, tigga69 said: Nov 3 21:18:34 SERVER-UR1 kernel: apex 0000:05:00.0: Cannot get BAR2 base address You are facing a completely different issue here, please make sure that you got Above 4G Decoding in your BIOS enabled the driver is working but your hardware has some difficult enabling it or better speaking allocating/finding the address space for the TPU. Please post your Diagnostics for further help and enable the above mentioned option in the BIOS. Quote Link to comment
tigga69 Posted November 7, 2022 Share Posted November 7, 2022 @ich777 everything makes sense, and your comment about the driver makes sense (which is why I was checking) I double checked Bios and I did have Above 4G enables (I did think I had already!). I guess that it it more likely the cheap adapter card I used which was for wifi adapter. I know adapter cards are problematic, I just expected the coral card to not even be recognised. I'll swap that out and report back in a few days (once it turns up) Thanks again for the pointers. Quote Link to comment
LunarstarPony Posted November 7, 2022 Share Posted November 7, 2022 So starting from yesterday I'm not sure why but starting the Frigate Container will cause my entire unraid to crash and rebooted? I have a USB Coral Stick and a GTX1050 I don't really expect anything in the Diag as It always just straight up crash the entire system Tell me if you need anything! lunar-unraid-diagnostics-20221107-0317.zip Quote Link to comment
tigga69 Posted November 8, 2022 Share Posted November 8, 2022 @ich777OK so i ordered and installed a more expensive StarTech PCIe to Mini PCIe adaptor card and have the same problem. Driver doesnt see a PCIe card, and as you said the route of the problem is the Above4G not working. This is seen by the error "Cannot get BAR2 base address" So the coral card is recognised on the bus, but the driver cant find it to address it. The motherboard is a Gigabyte b550m DS3H with F/w F15a from march 2022, there is a newer version but I know that wont make any difference, so I havent flashed it yet. Above4G decoding is enabled and Re-size BAR support is set to Auto (the other option is disabled) Ive also left the PCIEX16 bifurcation to Auto rather than setting the lanes to a fixed setting. Any pointers you can provide to help??? Im kind of at a loss because I've never seen this type of problem before. thanks in advance. R. server-ur1-diagnostics-20221108-2245.zip Quote Link to comment
tigga69 Posted November 9, 2022 Share Posted November 9, 2022 Right! I fixed it!!! I just tried a different slot... which was obvious really. I was using the PCIe X1 slot and then I moved it to the PCIe X16 slot. I wasnt using the PCIe X16 because the hd controller board was in that slot! Big Doh! from me. Shout out to Brian H. because it was his post that gave me the clue. Quote Link to comment
ich777 Posted November 9, 2022 Share Posted November 9, 2022 19 hours ago, tigga69 said: @ich777OK so i ordered and installed a more expensive StarTech PCIe to Mini PCIe adaptor card and have the same problem. I don't think that's an issue with the PCIe card in any way, this seems like a pure hardware combination issue or at least that something is wrong with the BIOS because it can't allocate/find the address in RAM for the device. 19 hours ago, tigga69 said: The motherboard is a Gigabyte b550m DS3H with F/w F15a from march 2022, there is a newer version but I know that wont make any difference, so I havent flashed it yet. Are you really sure that this won't solve the issue? I would at least try it, resizable BAR or even BAR support on most Gigabyte motherboards is a mess, at least from my personal experience with them... Have you yet tried to boot with Legacy (CSM) instead of UEFI? Sorry for the late response, I've somehow missed that comment, luckily I've seen it today... 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.