Closed quantummobile closed 9 months ago
While this is happening it will be good to know the contents of /tmp/cache
Also there's no reason not to use a coral, it would only help
While this is happening it will be good to know the contents of /tmp/cache
How would I get these?
Also there's no reason not to use a coral, it would only help
I am using coral on another machine, works like a charm, though the same issue with recording segments is there too.
You can get a shell in the container with docker exec -it frigate /bin/bash
then run ls /tmp/cache
it would also be helpful to know at what time the event occurred that had missing recording segments
by the way, it looks like you kept the old motion detection values despite the release notes explaining motion detection has changed and these old values are no good. It is possible that your missing recording segments for the person walking have nothing to do with this error and are simply due to motion having not been detected. I would definitely suggest removing this config and tuning motion detection according to the docs https://deploy-preview-6262--frigate-docs.netlify.app/configuration/motion_detection
You can get a shell in the container with
docker exec -it frigate /bin/bash
then runls /tmp/cache
ls /tmp/cache mainhallway-e1pro@20231118170246+0200.mp4 mainhallway-e1pro@20231118170314+0200.mp4 salon-e1pro@20231118170245+0200.mp4 salon-e1pro@20231118170313+0200.mp4 mainhallway-e1pro@20231118170255+0200.mp4 mainhallway-e1pro@20231118170325+0200.mp4 salon-e1pro@20231118170253+0200.mp4 salon-e1pro@20231118170323+0200.mp4 mainhallway-e1pro@20231118170305+0200.mp4 mainhallway-e1pro@20231118170335+0200.mp4 salon-e1pro@20231118170303+0200.mp4 salon-e1pro@20231118170333+0200.mp4
by the way, it looks like you kept the old motion detection values despite the release notes explaining motion detection has changed and these old values are no good. It is possible that your missing recording segments for the person walking have nothing to do with this error and are simply due to motion having not been detected. I would definitely suggest removing this config and tuning motion detection according to the docs https://deploy-preview-6262--frigate-docs.netlify.app/configuration/motion_detection
Somehow I missed that - thanks for pointing out.
Okay I understand what is going on here. Your pre_capture is 120 seconds which is too long for the assumptions made by the recordings maintainer. basically meaning that your segments are being kept for too long because the assumption was made that the segments would be moved immediately. We will need to figure out how to address this in a PR
Okay I understand what is going on here. Your pre_capture is 120 seconds which is too long for the assumptions made by the recordings maintainer. basically meaning that your segments are being kept for too long because the assumption was made that the segments would be moved immediately. We will need to figure out how to address this in a PR
Okay, so at the moment there's nothing I can do on my side to fix that, right? :)
Until the PR is ready, you could drop your pre_capture time to something below 60s to mitigate the issue.
Until the PR is ready, you could drop your pre_capture time to something below 60s to mitigate the issue.
Alright, I have pre_capture time set to 30s. Will see how it goes.
Okay, I can confirm that after pre_capture time was set to 30, warnings stopped.
Thank you so much for this info. Had this issue for quite a while and took me a long time to find fix here. THX!
Describe the problem you are having
I have log flooded with this warning: frigate.record.maintainer WARNING : Unable to keep up with recording segments in cache for mainhallway-e1pro. Keeping the 5 most recent segments out of 6 and discarding the rest... Apart from that, events are actually missing parts of recording. Like person walks and all of a sudden disappears. Write times are in range of 0.1 - 0.05 s.
I had this issue in Frigate 12.1, then read in some post here that it is addressed in Beta version, so I migrated to Beta - still have this issue.
I very much look forward to getting help.
Other than this issue Frigate is fantastic. Thank you very much for your efforts!
Version
0.13.0-AA93D4F
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Proxmox
Install method
Docker Compose
Coral version
CPU (no coral)
Network connection
Wired
Camera make and model
Reolink e1Pro
Any other information that may be helpful
I am facing the same issue with and without coral. CPU load is inm range 1-5%. 16 GB of RAM, the system only runs Frigate.