[Detector Support]: Detection appears to be stuck. Restarting detection process #13167
Replies: 4 comments 1 reply
-
there have been some reports of this when running a VM in proxmox, I believe some users solved it by using an LXC instead |
Beta Was this translation helpful? Give feedback.
-
Hello, I confirmed the suspicion about proxmox, I moved frigate from an intel nuc to a proxmox VM and surprised, I had this error. Is there any solution apart from not running on proxmox VM ? In fact I have a k3s cluster with master running on the VM proxmox, it'll be very sad to have to run frigate independently outside of my k3s on the proxmox host it-self. Apart from the fact that detection is down every 2 hours or so for 1 minute, what's the consequence of this bug ? |
Beta Was this translation helpful? Give feedback.
-
@NickM-27 -- I am getting these same errors too, but I'm not running Frigate 0.14.1 in Proxmox. I am running it in a docker container in Ubuntu 24.04 LTS. I also have an M.2 coral tpu and a USB coral tpu connected and it is the usb that is having the trouble. Here's the relevant portion of my log file:
What do you think is causing the issue? |
Beta Was this translation helpful? Give feedback.
-
There are all sorts of USB C data cables out there. Some are not capable of supplying enough power. Some are not capable of the required speed. Some are poorly engineered and will act flaky. A few years ago I needed an expensive repair to a laptop because of the data cable burning out the port. When I first plugged in my Google Coral USB with the supplied USB cable I started seeing occasional "Detection appears to be stuck" log messages within the first hour and they continued every hour or two. I suspected the cable. Based on a suggestion from the NYT Wirecutter reviews I ordered "Cable Matters [USB-IF Certified] 10 Gbps Gen 2 USB C to USB C Cable 3.3 ft / 1m with 4K@60Hz Video and 100W Power Delivery in Black". If you try another cable, and it's not that one, I would at least verify that it is USB-IF certified. I installed it yesterday and so far there have been no more "Detection appears to be stuck" messages, but it's only been about 20 hours so far. I'll come back and reply or edit if I see any more of those errors. One thing to note if you try this particular cable, it is USB-C to USB-C so you need a free USB-C port on your PC to utilize it. The device mapping in my docker compose yaml file didn't need to change. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
Log Info: "Detection appears to be stuck. Restarting detection process"
USB 3 speeds appear to be working. Cables and ports have been swapped around. No change.
HassOS add-on, on proxmox 8.2.4.
Version
0.14.0-da913d8
Frigate config file
docker-compose file or Docker CLI command
none used
Relevant log output
Operating system
Proxmox
Install method
HassOS Addon
Object Detector
Coral
Any other information that may be helpful
Beta Was this translation helpful? Give feedback.
All reactions