[Support]: Frigate didn't recover after a sudden ffmpeg failure #15950
Unanswered
davidebeatrici
asked this question in
General Support
Replies: 3 comments 5 replies
-
|
The recording stopped at exactly 04:45:35, with the last 20 seconds in fast-forward... Frigate is still not recording at the moment, despite the live stream working just fine along with the blinking red dot. There is still space available on the disk, as can be seen in the screenshot I uploaded. One thing I noticed is the CPU usage being no longer shown in the bottom bar:
Appeared again without me doing anything:
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I confirmed by looking at the filesystem that the stream is indeed not being recorded:
I restarted Frigate one more time and it appears to be recording just fine now:
Could the recording failure be caused by corrupt segments not being cleaned up properly? I have this suspicion because when I restarted the add-on I noticed this in the log: Along with this: |
Beta Was this translation helpful? Give feedback.
-
|
Failed again at 06:24:38: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Your camera is sending bad data. Recovery is a "best effort". What you are seeing can be mitigated by improving the quality of the data your camera is sending. |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
I understand, but I believe Frigate should be more robust in that regard. At least, I would expect it to perform a reconnection when no frames are received. |
Beta Was this translation helpful? Give feedback.
-
|
Of course. Frigate already does all that it can to restart/reconnect, and it has had this functionality for a long time. Your logs show this is already happening as well. A few recommendations to help your system run better:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the recommendations. I'm actually waiting for a USB Coral to arrive, but the camera network connection should be stable as its wired (RJ45 POE). Ironically at another location I have a camera with the same chipset (Ingenic T31X) that is connected through Wi-Fi and so far it didn't exhibit any signs of failure. It's running OpenIPC though, maybe there is a bug in Thingino's streamer. Exact same Frigate config, albeit running on a more powerful host. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like Thingino may be the culprit then. Good luck, let us know if there are any other ways we can help. |
Beta Was this translation helpful? Give feedback.
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 just noticed Frigate suddenly stopped recording today, apparently due to an ffmpeg failure.
The live stream only became visible again after restarting the add-on.
Version
0.14.1-f4f3cfa
What browser(s) are you using?
No response
Frigate config file
FFprobe output from your camera
Object Detector
CPU (no coral)
Network connection
Wired
Camera make and model
Vanhua Z55 running Thingino
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
It seems that other times Frigate recovers just fine:
Beta Was this translation helpful? Give feedback.
All reactions