Lmtp Memory Limit
Hi,
i am using dovecot 2.2.33.2 on CentOS 7.4.
Since i upgraded from CentOS 7.2. to CentOS 7.4. (without upgrading dovecot), my dovecot sieve-pipe scripts crash with Out of memory: Out of memory (allocated 262144) (tried to allocate 8793 bytes)
There are some memory limits in dovecot or sieve? Can i change this value?
Kernel limitks: [root@xxx software]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 26505 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 26505 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
Dovecot is running as user mail: su mail bash-4.2$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 26505 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 4096 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
Can someone help me?
Thanks for help!
Best regards Thomas Manninger
On 14.01.2018 09:11, Thomas Manninger wrote:
Hi,
i am using dovecot 2.2.33.2 on CentOS 7.4.
Since i upgraded from CentOS 7.2. to CentOS 7.4. (without upgrading dovecot), my dovecot sieve-pipe scripts crash with Out of memory: Out of memory (allocated 262144) (tried to allocate 8793 bytes)
There are some memory limits in dovecot or sieve? Can i change this value?
Kernel limitks: [root@xxx software]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 26505 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 26505 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
Dovecot is running as user mail: su mail bash-4.2$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 26505 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 4096 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
Can someone help me?
Thanks for help!
Best regards Thomas Manninger
Check 'doveconf service/lmtp' for dovecot imposed limits. If vsz_limit is 18446744073709551615, it means default_vsz_limit is used. Check out 'doveconf default_vsz_limit'. You can then decide if you want to set some limit for lmtp only or increase the default limit. Aki
Hi.
268435456 / 1024 / 1024 = 256M not 256K. These are Bytes not Bits.
Aki
On 15.01.2018 12:02, Thomas Manninger wrote:
Hi, thanks for your response! Now, i already solved the problem, but it's possible a bug? If i use the default values: default_vsz_limit = 256M service lmtp { vsz_limit = $default_vsz_limit } After restart, i check the limits of the lmtp process: Max data size 268435456 268435456 bytes The limit is 256KB instead of 256MB? If i change the value to 512MB, the process limit is 512KB. When i set "20000M" as limit, the process limit is really 20000MB. I am using CentOS 7.4. and dovecot 2.2.33.2 (d6601f4ec). Who is parseing the values from the unit (MB) to Bytes? Dovecot or a linux libary function??
Best regards, Thomas Manninger *Gesendet:* Montag, 15. Januar 2018 um 08:16 Uhr *Von:* "Aki Tuomi" aki.tuomi@dovecot.fi *An:* "Thomas Manninger" DBGTMaster@gmx.at, Dovecot@dovecot.org *Betreff:* Re: Lmtp Memory Limit
On 14.01.2018 09:11, Thomas Manninger wrote:
Hi,
i am using dovecot 2.2.33.2 on CentOS 7.4.
Since i upgraded from CentOS 7.2. to CentOS 7.4. (without upgrading dovecot), my dovecot sieve-pipe scripts crash with Out of memory: Out of memory (allocated 262144) (tried to allocate 8793 bytes)
There are some memory limits in dovecot or sieve? Can i change this value?
Kernel limitks: [root@xxx software]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 26505 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 26505 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
Dovecot is running as user mail: su mail bash-4.2$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 26505 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 4096 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
Can someone help me?
Thanks for help!
Best regards Thomas Manninger
Check 'doveconf service/lmtp' for dovecot imposed limits. If vsz_limit is 18446744073709551615, it means default_vsz_limit is used. Check out 'doveconf default_vsz_limit'. You can then decide if you want to set some limit for lmtp only or increase the default limit. Aki
participants (2)
-
Aki Tuomi
-
Thomas Manninger