[Detector Support]: Detection appears to be stuck. Restarting detection process #13167
Replies: 3 comments
-
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.
-
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