No E-Mail Notifications will be send on up or down of check but testing the email integration works about container-healthchecks HOT 8 CLOSED

Does your machine still enough space? No space left on device

Post the df -h of your host.

from container-healthchecks.

Yes, there is still 22G left on this device.

[root@x2845532 ~]# df -h
Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
devtmpfs         16G       0   16G    0% /dev
tmpfs            16G       0   16G    0% /dev/shm
tmpfs            16G    1,6G   15G   10% /run
tmpfs            16G       0   16G    0% /sys/fs/cgroup
/dev/md1        436G    393G   22G   95% /
/dev/md0        969M    225M  678M   25% /boot
tmpfs           3,2G       0  3,2G    0% /run/user/0
overlay         436G    393G   22G   95% /var/lib/docker/overlay/0baf47a78cc8fb65c06c5dfcc7d08eed1243c2d074ffd41e04ded89d01e93406/merged

from container-healthchecks.

@CodeSmolder Exec into the container and run df there, the supervisor program runs healthchecks and such so it probably is related to the low percent of storage available, e.g., different volume / mounts are used for / inside the container.

Make sure quotas and such don't affect the volume(s) and container(s) you have running.

from container-healthchecks.

@CodeSmolder Also have you already tried to recreate the container itself? Maybe the container's root fs is full. How long is / was the container running?

from container-healthchecks.

@CodeSmolder Exec into the container and run df there, the supervisor program runs healthchecks and such so it probably is related to the low percent of storage available, e.g., different volume / mounts are used for / inside the container.

Make sure quotas and such don't affect the volume(s) and container(s) you have running.

root@d5a46a8ff620:/# df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay         436G  393G   21G  96% /
tmpfs            64M     0   64M   0% /dev
tmpfs            16G     0   16G   0% /sys/fs/cgroup
/dev/md1        436G  393G   21G  96% /data
shm              64M     0   64M   0% /dev/shm
tmpfs            16G     0   16G   0% /proc/acpi
tmpfs            16G     0   16G   0% /proc/scsi
tmpfs            16G     0   16G   0% /sys/firmware

I have not quotas set, so there should be not affect on volume(s) and container(s)

from container-healthchecks.

@CodeSmolder Also have you already tried to recreate the container itself? Maybe the container's root fs is full. How long is / was the container running?

I recreated the container and then it worked again with no problem.

The container was running about a week before when the error occurred.

from container-healthchecks.

@CodeSmolder I have pushed a commit to lower the log sizes that supervisord will keep, that may solve the issue for good.

The image tag v1.17.0-20201019-143145-678 should become available in the next 15-30 minutes.

from container-healthchecks.

@galexrt: thank you :)

from container-healthchecks.