-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[Config Support]: /tmp/cache fills up intermittently #11402
Replies: 1 comment · 8 replies
-
this is usually an issue when requesting a large clip for notifications or other purposes via the API. The only way to know for sure though is to check the contents of /tmp/cache once this has occurred and see what is taking up space |
Beta Was this translation helpful? Give feedback.
All reactions
-
@NickM-27 have you had a moment to look at the above stats maybe? |
Beta Was this translation helpful? Give feedback.
All reactions
-
I don't see anything that would indicate a problem for the recordings. I would suggest enabling debug logs for |
Beta Was this translation helpful? Give feedback.
All reactions
-
@NickM-27
|
Beta Was this translation helpful? Give feedback.
All reactions
-
The problem is you have |
Beta Was this translation helpful? Give feedback.
All reactions
-
Yes but I added that after the problem started occurring, just to see if it changes anything. It actually helped a bit but let me set it back to |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
Hi,
My /tmp/cache fills up for no obvious reason. My Frigate instance sometimes works for a week without issues, but more frequently it works for a few hours, or even only for 10 minutes before the cache fills up. When Frigate is working as expected, my cache uses ~50MB. When it spikes to 4GB, it does that within minutes and causes streams to crash. Logs don't give me any hints.
I'm running a Proxmox VM with Debian, Docker and Portainer.
Any ideas on how to troubleshoot it?
Thanks,
Maciek
Version
0.13.2-6476F8A
Frigate config file
Relevant log output
Frigate stats
Operating system
Proxmox
Install method
Docker Compose
Coral version
USB
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions