Camera service consumes too many system inode resources (docker/gladys crash) #749
Labels
Milestone
Comments
Pierre-Gilles
added a commit
that referenced
this issue
May 4, 2020
NickDub-old
pushed a commit
to NickDub/Gladys
that referenced
this issue
Aug 7, 2020
…value parsing (GladysAssistant#769) * Remove scene queue concurrency * Fix GladysAssistant#749 : Camera should not create tons of folders + improve image compression * Fix camera tests * Fix scene UI, automatically add actions blocks * Add tests to cameraService.start * Fix GladysAssistant#767: MQTT service should parseFloat received device value * Fix MQTT tests
R6n0
pushed a commit
to R6n0/Gladys
that referenced
this issue
Dec 2, 2020
…value parsing (GladysAssistant#769) * Remove scene queue concurrency * Fix GladysAssistant#749 : Camera should not create tons of folders + improve image compression * Fix camera tests * Fix scene UI, automatically add actions blocks * Add tests to cameraService.start * Fix GladysAssistant#767: MQTT service should parseFloat received device value * Fix MQTT tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First, are you sure that you found a Gladys bug? yes
Description
Directory /var/lib/docker/overlay2/xxxx/diff/tmp/gladysassistant is full au camera-* directories.
On my Gladys instance, i have 2 cameras with 2 seconds refresh delay for one of them and 60 seconds for the other.
When 100% inodes used : Docker doesn't start anymore with "no space left on device storage-driver=overlay2" error message.
Expected behavior
Regular purging history ?
Your Gladys installation (please complete the following information):
The text was updated successfully, but these errors were encountered: