master: Warning: service(imap): process_limit (1024) reached

sahostking

Verified User
Joined
Jan 29, 2021
Messages
114
Location
South Africa
Aug 8 12:21:32 storm dovecot[1583892]: master: Warning: service(imap): process_limit (1024) reached, client connections are being dropped
Aug 8 12:21:33 storm dovecot[1583892]: master: Warning: service(imap): process_limit (1024) reached, client connections are being dropped
Aug 8 12:21:34 storm dovecot[1583892]: master: Warning: service(imap): process_limit (1024) reached, client connections are being dropped
Aug 8 12:21:35 storm dovecot[1583892]: master: Warning: service(imap): process_limit (1024) reached, client connections are being dropped
Aug 8 12:21:36 storm dovecot[1583892]: master: Warning: service(imap): process_limit (1024) reached, client connections are being dropped
Aug 8 12:21:37 storm dovecot[1583892]: master: Warning: service(imap): process_limit (1024) reached, client connections are being dropped
Aug 8 12:21:39 storm dovecot[1583892]: master: Warning: service(imap): process_limit (1024) reached, client connections are being dropped
Aug 8 12:21:40 storm dovecot[1583892]: master: Warning: service(imap): process_limit (1024) reached, client connections are being dropped
Aug 8 12:21:41 storm dovecot[1583892]: master: Warning: service(imap): process_limit (1024) reached, client connections are being dropped

I created : /usr/local/directadmin/custombuild/custom/dovecot/conf.d/99-serviceimap.conf

and placed in

service imap {
process_limit = 2000
}

and

cat /usr/local/directadmin/custombuild/custom/dovecot/conf/limits.conf

default_process_limit=4096
default_client_limit=12288
default_vsz_limit=8GB


But still not working
 
Will this still work for dovecot 2.4?

Main Dovecot configuration moved to separate files as of Directadmin Version 1.678. The script does not look compatible with the new scheme of Dovecot configs. And it might break the setup of the Dovecot 2.4.x.
 
Back
Top