yayitazale Posted August 15 Author Share Posted August 15 5 hours ago, lexo said: Hey guys, I have an issue with updating as well. Actually earlier today i just clicked "update all containers" and left. After beeing back every docker was updated as usual and I was happy. A little later I realized the frigate container was not showing anymore - just gone. When checking for breaking changes I came here and found out, a little config tweeking will be needed. But actually, my container does not startup anymore at all. docker run -d --name='frigate' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="KAL-NAS" -e HOST_CONTAINERNAME="frigate" -e 'FRIGATE_RTSP_PASSWORD'='xxxxxx' -e 'PLUS_API_KEY'='' -e 'LIBVA_DRIVER_NAME'='radeonsi' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'NVIDIA_DRIVER_CAPABILITIES'='' -e 'YOLO_MODELS'='' -e 'USE_FP16'='' -e 'TRT_MODEL_PREP_DEVICE'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8971]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/yayitazale/unraid-templates/main/frigate.png' -p '8971:8971/tcp' -p '8554:8554/tcp' -p '5000:5000/tcp' -p '8555:8555/tcp' -p '8555:8555/udp' -v '/mnt/user/appdata/frigate':'/config':'rw' -v '/mnt/user/Media/frigate':'/media/frigate':'rw' -v '/etc/localtime':'/etc/localtime':'rw' --device='' --device='' --shm-size=256mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --restart unless-stopped 'ghcr.io/blakeblackshear/frigate:stable' docker: bad format for path: . See 'docker run --help'. The command failed. Now ChatGPT helped me out to understand, that empty --device parameters are the issue here. Ofcourse I could run this command now directly in Docker without those two empty parameters, but I am note sure what that would mean for future updates of the container, so I would like to stick to the "normal" Unraid installation process. On the other hand I am note sure what to do, as I am note able to find out, which parameters dockers show me are relevant for those two entries. There are severall more in the container setup mask, that I am not using. Are there two parameters not marked as optional that should be marked so? Thanks in advance! BR Mario [edit] I understood that I have to re-install from the apps section and tried just that. Another idea that pops up for me - as Frigate is not showing anymore in the docker tab I am not able to delete the old entry anymore. May this cause the issue? Hi, sorry for the delayed anwser, is ban holiday in Spain. First of all, yes you must reinstall the app from scratch because the new v14 version needs a new template with new entries. Device entries weren't never mandatory entries, and aren't in the new template. All the optional entries have the "remove this if you are not using it" so, as it describes, you should remove them. If the container is no longer available in the frontend of unraid, you should be able to install it again. Quote Link to comment
yayitazale Posted August 15 Author Share Posted August 15 21 minutes ago, Disco_Jungle said: Hello everyone, I'm having an issue that I believe is related to the tmpfs for /tmp/cache. The Frigate logs are throwing this warning: frigate.record.maintainer WARNING : Unable to keep up with recording segments in cache for tele-pole-pano. Keeping the 6 most recent segments out of 9 and discarding the rest... I have 16 gigs of RAM, and Unraid dashboard shows not even 3 gigs of use. This server is only running 4 dockers: MQTT, ZWave, Frigate, and HASS. here is the output of disk free: I have the default extra parameter tmpfs: --mount type=tmpfs,destination=/tmp,tmpfs-size=1000000000 I'm assuming that tmpfs mounted to /run is where that is supposed to go? If so, why is it only 128M in size? Overall, this server pretty much never goes over 10% CPU usage on its 2700X, doesn't go over 3 gigs of the available 16, and doesn't use more than 10% of it's 512 gig nvme cache drive. Edit: In Frigate's UI, it's correctly showing that it has 1 gig of tmpfs. I'm guessing it is requesting that much, but there isn't that much available. emove this remove this if you are not using it Hi: tmpfs that goes to /dev/shm is what is usable RAM in the host, in your case 7.8GB. If you go to the console of the container and run the same command you will see that is mapped to /tmp/cache tmpfs 954M 9.0M 945M 1% /tmp/cache If you run the "free" command in the container console you will se that you have 1GB of ram. You should read this to solve your issue: https://docs.frigate.video/troubleshooting/recordings 1 Quote Link to comment
Disco_Jungle Posted August 15 Share Posted August 15 (edited) 2 hours ago, yayitazale said: Hi: tmpfs that goes to /dev/shm is what is usable RAM in the host, in your case 7.8GB. If you go to the console of the container and run the same command you will see that is mapped to /tmp/cache tmpfs 954M 9.0M 945M 1% /tmp/cache If you run the "free" command in the container console you will se that you have 1GB of ram. You should read this to solve your issue: https://docs.frigate.video/troubleshooting/recordings Thank you for the info! It does look like the cache is working correctly, then? This is from container's console: # df -h Filesystem Size Used Avail Use% Mounted on /dev/loop2 20G 4.9G 15G 25% / tmpfs 64M 0 64M 0% /dev shm 256M 6.1M 250M 3% /dev/shm shfs 477G 24G 452G 5% /config overlay 7.8G 137M 7.7G 2% /usr/share/zoneinfo/Etc/UTC /dev/loop2 20G 4.9G 15G 25% /etc/hosts tmpfs 954M 102M 853M 11% /tmp/cache # free -m total used free shared buff/cache available Mem: 15918 2126 231 263 13560 13199 Swap: 0 0 0 I tried adding this from that troubleshoot page: logger: logs: frigate.record.maintainer: debug But doesn't output anything extra, when I look through the log, I don't see any debug lines. This setup is at a remote property, so it hardly ever records since it's not often people go over there since its hot in the Summer. This is the only relevant info when I do docker logs --follow Frigate. The 192.168.30.12 is the tele-pole-pano, and 30.20 is Frigate container. 2024-08-15 13:41:33.206589978 13:41:33.206 INF [streams] can't add track error="wrong response on DESCRIBE" 2024-08-15 13:41:33.206688338 13:41:33.206 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="start from CONN state" url=rtsp://admin:****@192.168.30.12:554/live 2024-08-15 13:41:33.209249877 192.168.1.10 - - [15/Aug/2024:13:41:33 -0500] "GET /api/go2rtc/streams/tele-pole-pano HTTP/1.1" 200 1751 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:33.353179044 192.168.1.10 - - [15/Aug/2024:13:41:33 -0500] "GET /live/mse/api/ws?src=tele-pole-pano HTTP/1.1" 101 886171 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:34.947324097 192.168.1.10 - - [15/Aug/2024:13:41:34 -0500] "GET /api/tele-pole-pano/latest.webp?h=832&cache=1723747293969 HTTP/1.1" 200 432574 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:41.453267456 127.0.0.1 - - [15/Aug/2024:13:41:41 -0500] "" 400 0 "-" "-" "-" 2024-08-15 13:41:43.077453794 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /live/mse/api/ws?src=tele-pole-pano HTTP/1.1" 101 12855913 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.088120923 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/barn-underhang/latest.webp?h=360&cache=1723747303920 HTTP/1.1" 499 0 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.088145423 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/tele-pole-pano/latest.webp?h=360&cache=1723747303921 HTTP/1.1" 499 0 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.098317700 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/outside-barn/latest.webp?h=360&cache=1723747303921 HTTP/1.1" 499 0 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.098321990 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/gate-ptz/latest.webp?h=360&cache=1723747303920 HTTP/1.1" 499 0 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.105746677 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/config HTTP/1.1" 200 33364 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.166000398 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/review?limit=10&severity=alert HTTP/1.1" 200 3 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.173978997 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/barn-underhang/latest.webp?h=302&cache=1723747303936 HTTP/1.1" 200 13780 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.179530798 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747303936 HTTP/1.1" 200 20440 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.182143357 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/outside-barn/latest.webp?h=302&cache=1723747303936 HTTP/1.1" 200 10576 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.287565654 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/tele-pole-pano/latest.webp?h=307&cache=1723747303936 HTTP/1.1" 200 45264 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.494893303 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747304313 HTTP/1.1" 200 20438 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.835030529 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747304639 HTTP/1.1" 200 20262 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:44.180643975 192.168.1.10 - - [15/Aug/2024:13:41:44 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747304983 HTTP/1.1" 200 20354 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:44.508967008 192.168.1.10 - - [15/Aug/2024:13:41:44 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747305323 HTTP/1.1" 200 20378 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:44.810835965 192.168.1.10 - - [15/Aug/2024:13:41:44 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747305630 HTTP/1.1" 200 20278 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:44.994434138 192.168.1.10 - - [15/Aug/2024:13:41:44 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747305815 HTTP/1.1" 200 20352 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:46.301575777 [2024-08-15 13:41:46] frigate.record.maintainer WARNING : Unable to keep up with recording segments in cache for tele-pole-pano. Keeping the 6 most recent segments out of 7 and discarding the rest... I also checked the Unraid logs just now, and found an entry related to Frigate: Aug 15 13:40:41 Ranch-Unraid kernel: x86/PAT: frigate.detecto:13157 map pfn RAM range req uncached-minus for [mem 0xcc190000-0xcc193fff], got write-back My detector is a M.2 pci Coral TPU, and I have the plugin installed, it reports everything is healthy, and Frigate start up logs report TPU found I also have an identical setup at home, the only difference being its TPU is USB, and it has a Nvidia Quadro for decoding instead of AMD RX 550, and it running 0.14 as well, but problem free. Both use Amcrest cameras, but the remote property has 1 panoramic, and 1 PTZ. Edited August 15 by Disco_Jungle Quote Link to comment
John Graham Posted August 16 Share Posted August 16 Hello All, humm seems like i missed something. un-raid docker page, i don't use this much but if i click on frigate then WebUI i get a error http "The plain HTTP request was sent to HTTPS port" i tipe in the https address and it asks for a user name and password. humm never usered a user name or password (where to we set that up 🤪) I use (frigate-proxy) so i never needed to miss with it. the port that asks for the password is port:8971 i use port:5000 and it works with out a username/password did i miss something in the 1.4 upgrade? as allway thanks Quote Link to comment
Bruceflix Posted August 16 Share Posted August 16 2 hours ago, John Graham said: did i miss something in the 1.4 upgrade? To save time you could have read https://docs.frigate.video/configuration/authentication rather than post here. Quote Link to comment
bushbasha Posted August 16 Share Posted August 16 (edited) Hi guys, mega noob here, the update killed my frigate, is anyone kind enough please to supply a working config file template with multiple cameras that i can peruse and replicate with my info please. my old config just doesn't seem to work with the new version and its completely killed it. Edited August 16 by bushbasha Quote Link to comment
bmrowe Posted August 16 Share Posted August 16 I'm running Frigate+ on unraid. When I scroll the frigate (/plus) tab it will glitch and reset the focus to the top of the screen. Meaning, I scroll through 5-10 rows of images and it will auto scroll back up to the top of the screen. This bug is preventing me from categorizing and confirming images since I can't scroll far enough to see them. In chrome debugger, I don't see any errors in the console. it does seem to happen after these two calls: /api/events?limit=100&in_progress=0&is_submitted=0&has_snapshot=1 /api/events?limit=100&in_progress=0&is_submitted=0&has_snapshot=1&before=1723800275.862599 Quote Link to comment
yayitazale Posted August 16 Author Share Posted August 16 20 hours ago, Disco_Jungle said: Thank you for the info! It does look like the cache is working correctly, then? This is from container's console: # df -h Filesystem Size Used Avail Use% Mounted on /dev/loop2 20G 4.9G 15G 25% / tmpfs 64M 0 64M 0% /dev shm 256M 6.1M 250M 3% /dev/shm shfs 477G 24G 452G 5% /config overlay 7.8G 137M 7.7G 2% /usr/share/zoneinfo/Etc/UTC /dev/loop2 20G 4.9G 15G 25% /etc/hosts tmpfs 954M 102M 853M 11% /tmp/cache # free -m total used free shared buff/cache available Mem: 15918 2126 231 263 13560 13199 Swap: 0 0 0 I tried adding this from that troubleshoot page: logger: logs: frigate.record.maintainer: debug But doesn't output anything extra, when I look through the log, I don't see any debug lines. This setup is at a remote property, so it hardly ever records since it's not often people go over there since its hot in the Summer. This is the only relevant info when I do docker logs --follow Frigate. The 192.168.30.12 is the tele-pole-pano, and 30.20 is Frigate container. 2024-08-15 13:41:33.206589978 13:41:33.206 INF [streams] can't add track error="wrong response on DESCRIBE" 2024-08-15 13:41:33.206688338 13:41:33.206 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="start from CONN state" url=rtsp://admin:****@192.168.30.12:554/live 2024-08-15 13:41:33.209249877 192.168.1.10 - - [15/Aug/2024:13:41:33 -0500] "GET /api/go2rtc/streams/tele-pole-pano HTTP/1.1" 200 1751 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:33.353179044 192.168.1.10 - - [15/Aug/2024:13:41:33 -0500] "GET /live/mse/api/ws?src=tele-pole-pano HTTP/1.1" 101 886171 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:34.947324097 192.168.1.10 - - [15/Aug/2024:13:41:34 -0500] "GET /api/tele-pole-pano/latest.webp?h=832&cache=1723747293969 HTTP/1.1" 200 432574 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:41.453267456 127.0.0.1 - - [15/Aug/2024:13:41:41 -0500] "" 400 0 "-" "-" "-" 2024-08-15 13:41:43.077453794 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /live/mse/api/ws?src=tele-pole-pano HTTP/1.1" 101 12855913 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.088120923 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/barn-underhang/latest.webp?h=360&cache=1723747303920 HTTP/1.1" 499 0 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.088145423 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/tele-pole-pano/latest.webp?h=360&cache=1723747303921 HTTP/1.1" 499 0 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.098317700 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/outside-barn/latest.webp?h=360&cache=1723747303921 HTTP/1.1" 499 0 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.098321990 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/gate-ptz/latest.webp?h=360&cache=1723747303920 HTTP/1.1" 499 0 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.105746677 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/config HTTP/1.1" 200 33364 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.166000398 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/review?limit=10&severity=alert HTTP/1.1" 200 3 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.173978997 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/barn-underhang/latest.webp?h=302&cache=1723747303936 HTTP/1.1" 200 13780 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.179530798 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747303936 HTTP/1.1" 200 20440 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.182143357 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/outside-barn/latest.webp?h=302&cache=1723747303936 HTTP/1.1" 200 10576 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.287565654 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/tele-pole-pano/latest.webp?h=307&cache=1723747303936 HTTP/1.1" 200 45264 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.494893303 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747304313 HTTP/1.1" 200 20438 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:43.835030529 192.168.1.10 - - [15/Aug/2024:13:41:43 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747304639 HTTP/1.1" 200 20262 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:44.180643975 192.168.1.10 - - [15/Aug/2024:13:41:44 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747304983 HTTP/1.1" 200 20354 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:44.508967008 192.168.1.10 - - [15/Aug/2024:13:41:44 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747305323 HTTP/1.1" 200 20378 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:44.810835965 192.168.1.10 - - [15/Aug/2024:13:41:44 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747305630 HTTP/1.1" 200 20278 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:44.994434138 192.168.1.10 - - [15/Aug/2024:13:41:44 -0500] "GET /api/gate-ptz/latest.webp?h=302&cache=1723747305815 HTTP/1.1" 200 20352 "http://192.168.30.20:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0" "-" 2024-08-15 13:41:46.301575777 [2024-08-15 13:41:46] frigate.record.maintainer WARNING : Unable to keep up with recording segments in cache for tele-pole-pano. Keeping the 6 most recent segments out of 7 and discarding the rest... I also checked the Unraid logs just now, and found an entry related to Frigate: Aug 15 13:40:41 Ranch-Unraid kernel: x86/PAT: frigate.detecto:13157 map pfn RAM range req uncached-minus for [mem 0xcc190000-0xcc193fff], got write-back My detector is a M.2 pci Coral TPU, and I have the plugin installed, it reports everything is healthy, and Frigate start up logs report TPU found I also have an identical setup at home, the only difference being its TPU is USB, and it has a Nvidia Quadro for decoding instead of AMD RX 550, and it running 0.14 as well, but problem free. Both use Amcrest cameras, but the remote property has 1 panoramic, and 1 PTZ. This is note related with the template so please post your problem in the github https://github.com/blakeblackshear/frigate/issues 1 Quote Link to comment
yayitazale Posted August 16 Author Share Posted August 16 9 hours ago, John Graham said: Hello All, humm seems like i missed something. un-raid docker page, i don't use this much but if i click on frigate then WebUI i get a error http "The plain HTTP request was sent to HTTPS port" i tipe in the https address and it asks for a user name and password. humm never usered a user name or password (where to we set that up 🤪) I use (frigate-proxy) so i never needed to miss with it. the port that asks for the password is port:8971 i use port:5000 and it works with out a username/password did i miss something in the 1.4 upgrade? as allway thanks https://docs.frigate.video/configuration/tls/ Quote Link to comment
yayitazale Posted August 16 Author Share Posted August 16 (edited) 4 hours ago, bushbasha said: Hi guys, mega noob here, the update killed my frigate, is anyone kind enough please to supply a working config file template with multiple cameras that i can peruse and replicate with my info please. my old config just doesn't seem to work with the new version and its completely killed it. Hi, you can as we all did, learn reading the docs: https://docs.frigate.video/guides/getting_started https://docs.frigate.video/configuration/ https://docs.frigate.video/configuration/reference PD: as first step, you should reinstall the app from scratch from the App store of unraid, the new version requires a new template. Edited August 16 by yayitazale Quote Link to comment
yayitazale Posted August 16 Author Share Posted August 16 41 minutes ago, bmrowe said: I'm running Frigate+ on unraid. When I scroll the frigate (/plus) tab it will glitch and reset the focus to the top of the screen. Meaning, I scroll through 5-10 rows of images and it will auto scroll back up to the top of the screen. This bug is preventing me from categorizing and confirming images since I can't scroll far enough to see them. In chrome debugger, I don't see any errors in the console. it does seem to happen after these two calls: /api/events?limit=100&in_progress=0&is_submitted=0&has_snapshot=1 /api/events?limit=100&in_progress=0&is_submitted=0&has_snapshot=1&before=1723800275.862599 Not related with the template and not related with running it in unraid. Please report bugs here: https://github.com/blakeblackshear/frigate/issues Quote Link to comment
bushbasha Posted August 16 Share Posted August 16 6 hours ago, yayitazale said: Hi, you can as we all did, learn reading the docs: https://docs.frigate.video/guides/getting_started https://docs.frigate.video/configuration/ https://docs.frigate.video/configuration/reference PD: as first step, you should reinstall the app from scratch from the App store of unraid, the new version requires a new template. Thanks, I've deleted and reinstalled the app. I've read the documents multiple time, unfortunately it just confuses me as i can't see what's wrong with my config. I've taken out rtmp, I don't have an authentication config yet but I'm attempting to use 5000 port to have it up and running. How do you read the logs, everytime I try to read the logs through the container page (docker tab, clicking on frigate and going logs) the page lasts for a couple secs then closes out, I assume it's closing due to the container constantly restarting. How can I have the log page not close so I can actually see what's going on? Quote Link to comment
John Graham Posted August 17 Share Posted August 17 7 hours ago, bushbasha said: Thanks, I've deleted and reinstalled the app. I've read the documents multiple time, unfortunately it just confuses me as i can't see what's wrong with my config. I've taken out rtmp, I don't have an authentication config yet but I'm attempting to use 5000 port to have it up and running. How do you read the logs, everytime I try to read the logs through the container page (docker tab, clicking on frigate and going logs) the page lasts for a couple secs then closes out, I assume it's closing due to the container constantly restarting. How can I have the log page not close so I can actually see what's going on? I had some problems also restarting .. all I can tell you was what I did, Start adding MQTT first the see if it saves ok. then TUP or GPU and see if it saves and restarts ok .. work your way though step by step. Only work on 1 camera at a time .. something i did was as i was editing the config file was to copy only what i just added. then hit save/restart. If it gave me a (RED screen of death) just click the camera icon and then go back to the config it will have erased your new part of the config and you can try again. (paste your last try and try to fix it) give it time you will get it working .. the big thing is save your 1.3 config and restart from a NEW template! 1 Quote Link to comment
John Graham Posted August 17 Share Posted August 17 7 hours ago, bushbasha said: Thanks, I've deleted and reinstalled the app. I've read the documents multiple time, unfortunately it just confuses me as i can't see what's wrong with my config. I've taken out rtmp, I don't have an authentication config yet but I'm attempting to use 5000 port to have it up and running. How do you read the logs, everytime I try to read the logs through the container page (docker tab, clicking on frigate and going logs) the page lasts for a couple secs then closes out, I assume it's closing due to the container constantly restarting. How can I have the log page not close so I can actually see what's going on? i know others have said this (new version requires a new template) save your 1.3 config some place safe and the remove you old frigate and tell it to remove all files. i then whet to the folder that holds your DOCKER files and i just erased all ( erased the frigate folder ) then go to the App store and reinstall it. it will make all the files needed to run and you should be ready to go .. other have saved the databases and all there files/pic but i just wiped it all atr started right up and worked .. try it ( you mileage me very ) Quote Link to comment
John Graham Posted August 17 Share Posted August 17 14 hours ago, yayitazale said: https://docs.frigate.video/configuration/tls/ yep got the TLS thanks.. but still asking for user name and password .. i dont seem to need it as i am using the frigat_proxy and also the port 5000 works .. it just the link from the Docker screen asks for a password and user name .. no biggie just ansking I have a bad habit of (pushing all buttons) ?;-> John G. Quote Link to comment
bushbasha Posted August 17 Share Posted August 17 1 hour ago, John Graham said: I had some problems also restarting .. all I can tell you was what I did, Start adding MQTT first the see if it saves ok. then TUP or GPU and see if it saves and restarts ok .. work your way though step by step. Only work on 1 camera at a time .. something i did was as i was editing the config file was to copy only what i just added. then hit save/restart. If it gave me a (RED screen of death) just click the camera icon and then go back to the config it will have erased your new part of the config and you can try again. (paste your last try and try to fix it) give it time you will get it working .. the big thing is save your 1.3 config and restart from a NEW template! Thanks, this is what I ended up doing, just step by step basically. Not sure it's running optimally but its running. Is it worth setting up the authentication? I'm using 5000 port anyway, so I don't understand what the need for the other side is for? Quote Link to comment
Bruceflix Posted August 17 Share Posted August 17 10 minutes ago, bushbasha said: so I don't understand what the need for the other side is for? If you want to expose it to the internet for remote access Quote Link to comment
yayitazale Posted August 18 Author Share Posted August 18 On 8/17/2024 at 8:46 AM, John Graham said: yep got the TLS thanks.. but still asking for user name and password .. i dont seem to need it as i am using the frigat_proxy and also the port 5000 works .. it just the link from the Docker screen asks for a password and user name .. no biggie just ansking I have a bad habit of (pushing all buttons) ?;-> John G. https://docs.frigate.video/configuration/authentication The usage of the port 5000 from now on only intended for API. If you are using proxy there you have also the info to configure frigate accordingly. Quote Link to comment
yayitazale Posted August 18 Author Share Posted August 18 On 8/17/2024 at 10:00 AM, bushbasha said: Thanks, this is what I ended up doing, just step by step basically. Not sure it's running optimally but its running. Is it worth setting up the authentication? I'm using 5000 port anyway, so I don't understand what the need for the other side is for? On 8/17/2024 at 10:10 AM, Bruceflix said: If you want to expose it to the internet for remote access If you are using Frigate as CCTV system, you would like to have it secured even if you are not exposing to internet. Port 5000 in the future will only have access for API and not for the UI. This is one of the mandatory and breaking changes of this upgrade. https://docs.frigate.video/configuration/authentication Quote Link to comment
Alvaroc75 Posted August 19 Share Posted August 19 (edited) Hi, I'm new to unraid and frigate, I've been configuring frigate correctly but I have a problem and when I want to see the recordings or alerts, they keep loading eternally and I can't see them. Is it something of my configuration or on the contrary is something of the current version? Before unraid I tried frigate on linux an older version and I didn't have any problem. Best regards and thanks Edited August 19 by Alvaroc75 Quote Link to comment
John Graham Posted August 20 Share Posted August 20 17 hours ago, Alvaroc75 said: Hi, I'm new to unraid and frigate, I've been configuring frigate correctly but I have a problem and when I want to see the recordings or alerts, they keep loading eternally and I can't see them. Is it something of my configuration or on the contrary is something of the current version? Before unraid I tried frigate on linux an older version and I didn't have any problem. Best regards and thanks I am not sure .. take a look at the file that are saved to the hard drive .. if they are bad then that could be why your not seeing them in Frigate Quote Link to comment
John Graham Posted August 20 Share Posted August 20 Dont Get Me Wrong BIG THANKS for the Frigate people this is one of the best NVR's I have used!!! cant wait to see what comes next😇 Now I have a question ... I am trying to get a onvif camera running and I get this error: I see at the end of the error message I get " object is not subscriptable " The only thing I wish someone would add is a numbering system that would start from the start of the config file we are editing and give us a line number the error is on/starts on here is my error. Traceback (most recent call last): File "/opt/frigate/frigate/api/app.py", line 245, in config_save FrigateConfig.parse_raw(new_config) File "/opt/frigate/frigate/config.py", line 1665, in parse_raw return cls.model_validate(config) File "/usr/local/lib/python3.9/dist-packages/pydantic/main.py", line 551, in model_validate return cls.__pydantic_validator__.validate_python( File "/opt/frigate/frigate/config.py", line 1048, in __init__ if len(config["ffmpeg"]["inputs"]) == 1: TypeError: 'NoneType' object is not subscriptable Quote Link to comment
John Graham Posted August 20 Share Posted August 20 i have another question 😁.. Where is the CLICK to get in to the zones/debug it was in the debug but i cant find them now. thanks just me 🥴 Quote Link to comment
John Graham Posted August 20 Share Posted August 20 8 minutes ago, John Graham said: i have another question 😁.. Where is the CLICK to get in to the zones/debug it was in the debug but i cant find them now. thanks just me 🥴 Never mind ... Some times I just don't remember what i don't know 🤨 Quote Link to comment
yayitazale Posted August 21 Author Share Posted August 21 On 8/19/2024 at 2:37 PM, Alvaroc75 said: Hi, I'm new to unraid and frigate, I've been configuring frigate correctly but I have a problem and when I want to see the recordings or alerts, they keep loading eternally and I can't see them. Is it something of my configuration or on the contrary is something of the current version? Before unraid I tried frigate on linux an older version and I didn't have any problem. Best regards and thanks It is impossible to know with such little info. 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.