[Support]: Unable to keep up with recording segments in cache after removing camera #16621
Unanswered
edalquist
asked this question in
General Support
Replies: 3 comments 3 replies
-
Usually the cause of an |
Beta Was this translation helpful? Give feedback.
0 replies
-
Here is the log from a restart with the trail camera disabled. This is with
|
Beta Was this translation helpful? Give feedback.
1 reply
-
So I am just commenting out the entire trail camera block, I didn't actually realize I could use |
Beta Was this translation helpful? Give feedback.
2 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 upgraded to 0.15 today, everything seemed to be working well, I tried out on of my Nest cameras to see if it would work any better (it didn't) but ever since I disabled the camera it seems to have broken the recording maintainer.
The following logs are repeated over and over:
I re-enabled the
trail
camera in my config and that seems to have fixed things for new recordings, though all the recordings for the time of the errors seem lost even though they appear to existing on the file system.Note that I'd rather not have this camera enabled since it is constantly throwing errors due to the unreliable Nest camera stream.
Running in Docker on LXC with storage on a host level NFS mount.
Version
0.15
What browser(s) are you using?
No response
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
Install method
Proxmox via Docker
docker-compose file or Docker CLI command
Object Detector
Coral
Network connection
Wired
Camera make and model
hikvision
Screenshots of the Frigate UI's System metrics pages
No response
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions