[Detector Support]: detector.coral did not restart #19270
Replies: 3 comments 4 replies
-
|
You’re seeing “Detection appears to be stuck. Restarting detection process...” followed by a failure to restart the detector, which leaves Frigate unable to process recordings. This kind of stuck detector event with a Coral USB is known and can be related to power delivery, USB port instability, cable issues, or hardware passthrough quirks—especially when running under Proxmox, VMs, or Docker(1)(2). Here are actionable steps based on the documentation and community findings:
If you continue to see the detector fail to restart and Frigate is left in a failed state, the most robust fix reported is to fully reboot the host or VM to reinitialize the Coral, and to verify that your USB power and passthrough configuration are optimal(1)(2). For more troubleshooting steps and background, see:
📚 Sources:
Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
this shows the detector process is not running: After a restart i can see frigate.detector.coral is running as expected: |
Beta Was this translation helpful? Give feedback.
-
|
right, that is the process that is killed when the coral loses connection, and a new one is created. It seems the coral re-connection is not working |
Beta Was this translation helpful? Give feedback.
-
|
the new process is created most of the time. its unfortunate there doesn't appear to be an error log when the watch dog gives up creating new processes. i am continuing to investigate the root cause of why the coral gets stuck in the first place. but will take some time. so far i have eliminated the coral itself and the supplied usb lead by testing using frigate on other hardware - hp elitedesk with ubuntu -> docker -> frigate appears to be stable. next things to validate are:
|
Beta Was this translation helpful? Give feedback.
-
|
to be clear if the watchdog sees the process not get started back up with a successful inference then it will shut frigate down entirely, so something is stuck here |
Beta Was this translation helpful? Give feedback.
-
|
Right ok, well it doesn't shutdown frigate and it can get stuck in that state for hours until I notice. Is it worthwhile switching to the v16 release candidate that has just been announced? |
Beta Was this translation helpful? Give feedback.
-
in this case specifically, yes, in general though we know it works as this functionality has been the same for many years
I am not aware of any changes that may help this issue specifically |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
I regularly appear to get a detector stuck error that i am trying to diagnose (any advice appreciated here), but the reason for logging this ticket was because detector.coral failed to restart causing frigate to indefinitely fail.
i.e. at 12:21:01 the detector process restarts.
but at 12:25:31 the detector doesn't try to restart.
at which point frigate.record.maintainer logs unprocessed recording segments forever more.
Version
0.15.2-3bda638
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Install method
Proxmox via Docker
Object Detector
Coral
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
Proxmox -> Debian Bookworm VM -> Docker -> Frigate
Hardware passthru of intel gpu & google coral usb
Beta Was this translation helpful? Give feedback.
All reactions