Subject
One day after upgrading to 10.4.0 I realized the process check-for-changes.sh consumes a lot of memory and cpu resources.
I did not see this behaviour with 10.3.0.
Description
The next day after the upgrade the container used 2.5G of memory (this usually was less than 800M) and the four cpu cores have been very busy. After restarting docker-mailserver everything was as usual again.
Some hours later I realized that memory and cpu usage was growing again. It seems to be caused by the process bin/bash /usr/local/bin/check-for-changes.sh.
After starting docker-mailserver, the memory consumption of this process is around 6M, but growing 800k per minute (ca. 50M per hour). The higher the memory usage goes, the higher the cpu load.
This makes it necessary for me to restart docker-mailserver periodically (let's say: every day) as I have 4G of RAM available.
Question
It would be nice to hear if there are other people experiencing the same issue, or if it is just me ;-) Help is very appreciated!
I am not an expert in docker (yet), but I am very willing to learn as much as possible and to provide more information as needed and requested.
Thank you very much in advance!
(I did not label this issue as "bug" as I am not sure if this is a general issue or just happening in my configuration.)
Environment
Debian Bullseye, latest patches
Let'sEncrypt-certificates are generated from nginx-reverse-proxy with acme-companion.
version: "3.7"
services:
mailserver:
image: "docker.io/mailserver/docker-mailserver:10.4.0"
container_name: "mailserver"
hostname: "mail"
domainname: "[removed].de"
env_file: "/home/user/docker_compose/mailserver/mailserver.env"
ports:
- "25:25" # SMTP (explicit TLS => STARTTLS)
- "143:143" # IMAP4 (explicit TLS => STARTTLS)
- "465:465" # ESMTP (implicit TLS)
- "587:587" # ESMTP (explicit TLS => STARTTLS)
- "993:993" # IMAP4 (implicit TLS)
- "4190:4190" # ManageSieve
volumes:
- "data:/var/mail/"
- "state:/var/mail-state/"
- "logs:/var/log/mail/"
- "config:/tmp/docker-mailserver/"
- "/etc/localtime:/etc/localtime:ro"
- "/home/user/docker_compose/reverse-proxy/certs:/etc/letsencrypt/live/"
restart: "always"
cap_add:
- "NET_ADMIN"
- "SYS_PTRACE"
dns:
- "9.9.9.9"
- "8.8.8.8"
- "1.1.1.1"
volumes:
data:
state:
logs:
config:
And some (maybe useful and related) informations from .env. Please ask if there is more information needed!
ENABLE_CLAMAV=0
ENABLE_AMAVIS=1
SSL_TYPE=letsencrypt
ENABLE_QUOTAS=1
Subject
One day after upgrading to
10.4.0I realized the processcheck-for-changes.shconsumes a lot of memory and cpu resources.I did not see this behaviour with
10.3.0.Description
The next day after the upgrade the container used 2.5G of memory (this usually was less than 800M) and the four cpu cores have been very busy. After restarting
docker-mailservereverything was as usual again.Some hours later I realized that memory and cpu usage was growing again. It seems to be caused by the process
bin/bash /usr/local/bin/check-for-changes.sh.After starting
docker-mailserver, the memory consumption of this process is around 6M, but growing 800k per minute (ca. 50M per hour). The higher the memory usage goes, the higher the cpu load.This makes it necessary for me to restart
docker-mailserverperiodically (let's say: every day) as I have 4G of RAM available.Question
It would be nice to hear if there are other people experiencing the same issue, or if it is just me ;-) Help is very appreciated!
I am not an expert in docker (yet), but I am very willing to learn as much as possible and to provide more information as needed and requested.
Thank you very much in advance!
(I did not label this issue as "bug" as I am not sure if this is a general issue or just happening in my configuration.)
Environment
Debian Bullseye, latest patches
Let'sEncrypt-certificates are generated from nginx-reverse-proxy with acme-companion.
And some (maybe useful and related) informations from .env. Please ask if there is more information needed!