[Support]: local disk (cache?) filling up fast, clips not written to database #15370
Replies: 2 comments 3 replies
-
|
/tmp/cache should be ram not file based and really it should just be managed by Frigate. It looks like the cache that is being mounted contains other files which is causing problems for Frigate |
Beta Was this translation helpful? Give feedback.
-
|
I Just checked the contents of /tmp/cache. I run the command du -h /tmp/cache/* So i guess somehow frigate cannot copy it to the large hdd, and is keeping everything in the cache untill it is completely filled... Any tips on how to troubleshoot this? |
Beta Was this translation helpful? Give feedback.
-
|
you have tmpfs set to 1gb in your docker compose, but in your UI it says it has ~85gb for /tmp/cache. That seems weird to me. |
Beta Was this translation helpful? Give feedback.
-
|
I Just checked the contents of /tmp/cache. I run the command du -h /tmp/cache/* So i guess somehow frigate cannot copy it to the large hdd, and is keeping everything in the cache untill it is completely filled... Any tips on how to troubleshoot this? |
Beta Was this translation helpful? Give feedback.
-
|
No, I have no experience with proxmox |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
Hi all,
I absolutely love frigate!!! but.... Since a few days, i have some issues with my frigate setup. I have 15 cams around the office, recorded with frigate, which runs on proxmox.
System has been running fine and without issues for more than a year now, but since a few days, frigate stopped working. After some digging, i found out that the proxmox container stopped working because of a 100% disk. At first, i increased the disk from 64 to 80gb, and started the container back up. After starting, frigate immideately deleted its cache (i think?) and the used space went from 64gb to 15gb. but after that, within a few hours, the disk was again completely full, now at 80gb.
Restarting it only repeats this patern.
than about the disk space;
frigate has a root ssd disk which is now 87gb. this is where frigate runs, and where the cache is located. Besides that, there is an mountpoint (accessible for frigate at /data) which is an 14.5tb hdd, for storing the recordings. This hdd is not an network share or something like that, but a sata disk connected to the same proxmox server.
These disks are correctly recognized by frigate:
This morning i had to restart frigate again, and right after the restart, there where a lot of errors in the logfile.
To be honest; i googled a lot, but i do not no where to look anymore. Hopefully someone here can help me with this?
Thanks in advance guys!
Version
0.13.2-6476f8a
What browser(s) are you using?
No response
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
[{"return_code":0,"stderr":"","stdout":{"programs":[],"streams":[{"avg_frame_rate":"10/1","codec_long_name":"H.264/AVC/MPEG-4AVC/MPEG-4part10","display_aspect_ratio":"16:9","height":2160,"width":3840},{"avg_frame_rate":"0/0","bit_rate":"64000","codec_long_name":"PCMmu-law/G.711mu-law"}]}},{"return_code":0,"stderr":"","stdout":{"programs":[],"streams":[{"avg_frame_rate":"6/1","codec_long_name":"H.264/AVC/MPEG-4AVC/MPEG-4part10","display_aspect_ratio":"16:9","height":720,"width":1280}]}}]Frigate stats
No response
Install method
Proxmox via Docker
docker-compose file or Docker CLI command
Object Detector
Coral
Network connection
Wired
Camera make and model
hikvision DS-2CD2087G2H-LI(U)
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