#Frigate /tmp/cache - No space left on device

19 messages · Page 1 of 1 (latest)

vocal copper
#

Have been getting this error off and on for a while. I have increased my cache size several times in accordance with the docs. I believe it’s large notification clips clogging things up but not sure how to fix. Now in this most recent incident, I’ve tried rebooting Frigate several times but this isn’t resolving things anymore.

s6-log: warning: unable to write to /dev/shm/logs/nginx/current: No space left on device

frank glade
#

Logs are not stored in /tmp/cache

#

That has to do with shm

#

Increase shm size or you’ll want to use 0.15 which fixes this issue

vocal copper
#

also getting some funky errors in the logs

#

increased shm size from 256 > 512mb

#

--restart=unless-stopped --shm-size=512mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=100000000

running this in my Extra Parameters (unraid container install)

vocal copper
#

moved to 0.15 and still getting s6-log: warning: unable to write to /dev/shm/logs/nginx/current: No space left on device

#

still says 2024-10-07 00:42:38.160900304 [2024-10-07 00:42:38] frigate.app INFO : Starting Frigate (0.14.1-039ab1c) in the logs

#

using ghcr.io/blakeblackshear/frigate:039ab1c

#

Also tried MB instead of mb and upping from 512 to 1024 and still getting the errors

frank glade
vocal copper
frank glade
vocal copper
#

Ok so after upgrading to 0.15, now getting a lot of different errors.

#

including another space error

2024-10-09 15:21:18.287230414 [2024-10-09 15:21:18] ffmpeg.Balcony.record ERROR : [aost#0:1/aac @ 0x55643c5a26c0] Error submitting a packet to the muxer: No space left on device