[Support]: Too many unprocessed recording segments in cache for CameraName #15683
-
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
Would be great to see the contents of /tmp/cache in the container while this is happening. |
Beta Was this translation helpful? Give feedback.
-
I also see this error on my setup (with 0.15-beta4), seems to be a new thing after upgrading from beta3, but not sure as I had briefly bumped back to stable to check some other instability issues. |
Beta Was this translation helpful? Give feedback.
-
Ok, frustratingly, the error hasn't occurred since I restarted the container back on 26th December. I will provide the entire log since the last container start-up below, but here are the relevant lines:
Is this anything to worry about? In any case, I will continue to monitor for the original issue and will post a comment if it happens again. Thanks. Here's the entire log for the last few days:
|
Beta Was this translation helpful? Give feedback.
-
I also ran into this exact same issue as described in the original post. My upgrade path has been 0.14.1 -> 0.15.0-beta2 -> 0.15.0-beta3 -> 0.15.0-beta4. However I just started getting this issue two days ago on 0.15.0-beta4. I tried many different fixes (downgrading to 0.15.0-beta3, reducing my camera quality, moving hardware) but nothing seemed to stick. I would start getting the same errors within a few minutes of the container starting. Finally I wiped out my entire media directory for frigate to start fresh (but keeping the config) and I have yet to see this issue happen again. |
Beta Was this translation helpful? Give feedback.
-
Ok, as per one of my earlier comments, I had set up Frigate so that the storage/recordings folder was on a network drive (SMB NAS folder, mounted on my Frigate computer). That way, Frigate would save recordings directly onto the NAS. Good idea in theory. In practice, of course, when the NAS turns itself off, Frigate - understandably - goes haywire. Making it so that Frigate is storing recordings on the actual computer (rather than the NAS) solved the problem. I was able to test this manually by shutting down the NAS and observing that the error occurred when Frigate was saving to the NAS, but Frigate runs fine when the NAS is shut down if Frigate is saving to the computer instead. Thanks for helping me with troubleshooting this. |
Beta Was this translation helpful? Give feedback.
Ok, as per one of my earlier comments, I had set up Frigate so that the storage/recordings folder was on a network drive (SMB NAS folder, mounted on my Frigate computer). That way, Frigate would save recordings directly onto the NAS.
Good idea in theory. In practice, of course, when the NAS turns itself off, Frigate - understandably - goes haywire.
Making it so that Frigate is storing recordings on the actual computer (rather than the NAS) solved the problem. I was able to test this manually by shutting down the NAS and observing that the error occurred when Frigate was saving to the NAS, but Frigate runs fine when the NAS is shut down if Frigate is saving to the computer instead.
Thanks …