[Support]: Possible bug causing metrics to stop running #15589
Unanswered
aav7fl
asked this question in
General Support
Replies: 1 comment
-
yeah looks like we need to catch that |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem you are having
I think I've run into a bug with Frigate when it is unable to write data to my disk (temporarily). When this happens, my metrics page (and through the API) no long update. e.g. the metrics for my system and cameras seen here
/system#general
.I'm running Frigate through Docker on my NAS. Frigate doesn't know this, but the folder it's saving to is an SMB mount from my NAS. When I reboot my NAS, Frigate is temporarily unable to write to the disk. When this happens, the metrics in Frigate no longer update. Everything else on Frigate seems to work like snapshots and recordings. I've only noticed that the metrics can't recover.
You can see in my logs that it's failing to write to
/media/frigate/recordings
, which is a volume path shared through Docker, which is an SMB folder mounted on my host machine.The attached logs occurred at the exact moment that my metrics stopped updating in Frigate. If I restart Frigate, the metrics start working again.
Note that the
last_updated
field in my/api/stats
was from a few days ago (the exact moment my logs display an exception). Even though I captured it today.Version
0.15.0-6b12a45
What browser(s) are you using?
No response
Frigate config file
Not related
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
Install method
HassOS Addon
docker-compose file or Docker CLI command
Object Detector
Coral
Network connection
Wired
Camera make and model
Unrelated
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
I don't think this is related, but Coral is attached to my machine over USB 2.0 and not USB 3.0.
Some time ago, there was a change in the Kernel (or OS) that made the USB 3.0 connection to my Coral TPU lock up my entire machine when being used by Frigate. It's been happening for years and I've given up trying to solve it.
Beta Was this translation helpful? Give feedback.
All reactions