#Latest frigate nightlies keep running out of /dev/shm space..
23 messages · Page 1 of 1 (latest)
we need to see logs, config, and preferably lsof and du -h outputs of /dev/shm otherwise there is nothing we can help with
Hi nick, thanks and yes, apologies I should have got more info rather than just panicking and restarting the docker instance, but will next time depending on the time of day, prefer not to do it at night like now.
The only logs I can get are from the Portainer log view:
s6-log: warning: unable to write to /dev/shm/logs/nginx/current: No space left on device
s6-log: warning: unable to write to /dev/shm/logs/frigate/current: No space left on device
s6-log: warning: unable to write to /dev/shm/logs/nginx/current: No space left on device
s6-log: warning: unable to write to /dev/shm/logs/frigate/current: No space left on device
s6-log: warning: unable to write to /dev/shm/logs/nginx/current: No space left on device
s6-log: warning: unable to write to /dev/shm/logs/frigate/current: No space left on device
s6-log: warning: unable to write to /dev/shm/logs/nginx/current: No space left on device
I can connect, looking now
Output from du -h /dev/shm:
lsof apparently doesn't exist in the image?
lsof of the server running docker is HUGE
It's only running docker with the portainer image and frigate image
I didn't go and grab frigate logs before restarting, apologies
Just need to install it
This is before restarting?
Oh, how do I do that? I'm not that familiar with what funcationality I have within a docker shell. Thanks
Before restarting, hope that's helpful
Ah cool
Sorry, forgot to tag yoy
This is from df, just before I did the lsof that I've uploaded:
shm 1048576 925408 123168 89% /dev/shm
And this is just before writing this message:
shm 1048576 931516 117060 89% /dev/shm
and it crashed with shm error correct?
we found another issue and fixed it, so that will hopefully imporove what you are seeing as well