[Support]: Camera errors then "stops" recording - near empty video files #11053
Replies: 2 comments 3 replies
-
Although I am interested in fixing the problem. I am also hoping/wondering/thinking, is there a way we can make the process restart or the container restart if there is such a serious error (camera stops recording). Because I only became aware when I tried to get footage of an incident and found out that it actually stopped recording hours prior... |
Beta Was this translation helpful? Give feedback.
-
I’ve been having the same sort of issue, where Frigate encounters an error with a camera and then only records audio after that, going from files of an MB each to about 40 KB. I think it started a month ago when I enabled recording audio, but that may have been a coincidence. In my case, the number of cameras failing to record segments keeps increasing. I have to ‘refresh’ Frigate’s connection to the failing cameras to get them to start again, for which I have to either restart Frigate, restart the camera, or disable and re-enable the network connection between them. My logs fill up with the same error as @DrSpaldo sees meanwhile:
This is Frigate v0.13.2-6476f8a and go2rtc 1.8.4 on TrueNAS 23.10.2, in case that helps. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
From time to time, Frigate will throw a bunch of errors and then one camera (not always the same) will record almost empty video files and think that it is recording but it actually isn't.
Version
0.13.2-6476F8A
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Proxmox
Install method
Docker Compose
Coral version
PCIe
Network connection
Wired
Camera make and model
Reolink RLC-511
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions