search for: login_max_processes_count

Hello, Our server reach today the login_max_processes_count. Dovecot works well and don't accept any new connection. But it doesn't log anything about this problem : we are blind why the connection is refused for the clients. Could you add a log when the connection limit is reached or (maybe better) a log with the occupation for the beginning of...

I think today just due to increased use, my mail servers hit login_max_processes_count. It wasn't obvious what was happening, logins just weren't acting like they should and sometimes would get disconnected before given a prompt from the server. Something made me think to check if I had too many of certain dovecot processes and I found I had 128 imap-login processes on...

...art logging > # in at the same time more extra processes are created. To prevent fork-bombing > # we check only once in a second if new processes should be created - if all > # of them are used at the time, we double their amount until the limit set by > # this setting is reached. > #login_max_processes_count = 128 If the server is attacked by a password guessing routine, or just gets very busy, and login process count reaches 128, will the created processes ever get killed, or will dovecot continue to run 128 processes until it's restarted? Thanks, Ken -- Ken Anderson Pacific.Net

Today I found our dovecot 2.x gracefully logged: dovecot: master: Warning: service(imap-login): process_limit reached, client connections are being dropped I am confident that we had the very same problem on our previous dovecot 1.x box. Of course with dovecot 1.x, the same relative setting is login_max_processes_count. I believe that I turned up all dovecot logging & debugging to the max (also checked with the 1.x wiki), but nothing was ever logged relating to this. Does anyone know whether there is a way to get dovecot 1.x to log this type of error? Thanks, - Doug Mortensen Network Consultant Impala Netwo...

Hi, I'm working for tuning a busy cluster of dovecot servers. Heach server as 4 core, 8GB of RAM and provide POP3 and IMAP access to mailbox. OS is Debian 6.0 and dovecot version is 1.2.15. I am unsure how to set "login_max_processes_count" and "login_max_connections" for reach the best situation when login_process_per_connection is set to no. I don't know what value to set login_max_processes_count. For example is better the first or the second configuration? login_process_per_connection=no login_processes_co...

...ter upgrade, i got this warning msg: ----8< ---- # /etc/init.d/dovecot restart Stopping Dovecot Imap: [ OK ] Starting Dovecot Imap: Warning: fd limit 1024 is lower than what Dovecot can use under full load (more than 1280). Either grow the limit or change login_max_processes_count and max_mail_processes settings [ OK ] ----8< ---- but i changed either login_max_processes_count and max_mail_processes to 2048, it raised the same msg. How can i solove this issue? Thanks very much. My dovecot -n output: ----8&lt...

Hi, i don't know. Is normal login_max_processes_count > 1024?? Our environment is about 1700 users (imaps + thunderbird or imaps+horde). The server is RedHat Enterprise Linux 5.2 User logins different in a hour: # cat dovecot.info | grep 'Nov 11 10' | grep "login: Login" | cut -d'<' -f2 | cut -d'>' -f1 |...

...sisyphus-cybertalk-lists-altlinux-org/dovecot.index.cache: In valid argument dovecot: Oct 18 15:02:57 Warning: SIGHUP received - reloading configuration dovecot: Oct 18 15:02:58 Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 384). Either grow the limit or change login_max_processes_count a nd max_mail_processes settings dovecot: Oct 18 15:03:13 Warning: Killed with signal 15 deliver(seriv): Oct 18 15:04:07 Error: file_set_size() failed with index cache file /var/spool/imap/seriv/.imap/.community-lists-altlinux-org/dovecot.index.cache: Invalid arg ument deliver(seriv): Oct 18 15:04:...

...he configured parms. dovecot -n yields: # 1.1.14: /usr/local/etc/dovecot.conf # OS: AIX 1 005A928C4C00 listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1280 mail_max_userip_connections: 12 verbose_proctitle: yes first_valid_uid: 200 mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u mbox_write_locks: fcntl mbox_dirty_syncs: no auth default: passdb: driver: pam userdb: driver: passwd The o...

...curity/pam_ck_connector.so): libdbus-1.so.3: failed to map segment from shared object: Cannot allocate memory Feb 10 08:29:06 home dovecot-auth: PAM adding faulty module: /lib/security/pam_ck_connector.so English, please? :) Strangely, it seemed to disappear after increasing login_processes_count, login_max_processes_count and/or auth_worker_max_count. -- Vegard Svanberg <vegard at svanberg.no> [*Takapa at IRC (EFnet)]

...g fine as far as I know so I was investigating maybe mistuned limits : Dovecot is configured (for ~3000 users) with . each login processed in its own process : #login_process_per_connection = yes #login_max_connections = 256 . counts as : #login_processes_count = 3 login_max_processes_count = 1024 auth default { [...] count = 5 } I've got several questions : 1) how can I count more than login_max_processes_count processes ? # ps aux | egrep -i '(pop3|imap)-login' | wc -l # 1031 2) could be my auth process count the bottleneck ? is there...

...ere's no solution at present; since I'm having a different error, though, I'm posting it here. Compilation succeeds. Starting dovecot from command line results in: Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 640). Either grow the limit or change login_max_processes_count and max_mail_processes settings Warning: Last died with error (see error log for more information): Auth process died too early - shutting down Trying to run just dovecot-auth outputs: dovecot-auth: Fatal: MECHANISMS environment is unset Now, if I try to set an environment variable called MECH...

...ldir. I don't want to stop dovecot, remove the homedir and start dovecot. Is there another way to accomplish this. Thanks, Martijn # 1.2.12: /etc/opt/redknot/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 4096). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: SunOS 5.11 sun4v log_path: /var/log/dovecot.log protocols: imap imaps managesieve ssl_cert_file: /etc/opt/redknot/ssl/secure.redknot.nl.cer ssl_key_file: /etc/opt/redknot/ssl/secure.redknot.nl.key disable_plaintext_auth: no login_dir: /opt/redknot/var/run/dov...

...: %Y-%m-%d %H:%M:%S protocols: pop3 imap imaps pop3s ssl_cipher_list: ALL:!LOW disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_max_processes_count: 256 first_valid_uid: 1090 last_valid_uid: 1090 first_valid_gid: 1090 last_valid_gid: 1090 mail_privileged_group: mail mail_location: maildir:~/Maildir mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plug...

...AIL 1 user=test1 May 21 11:14:17 Info: pop3-login: Disconnected (auth failed, 1 attempts): user=<test1>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot -n: Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 768). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: SunOS 5.10 sun4u info_log_path: /var/log/dovecot.log protocols: imap pop3 listen(default): 127.0.0.1:143 listen(imap): 127.0.0.1:143 listen(pop3): * ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default...

...processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? login_process_per_connection = no # Number of login processes to keep for listening new connections. #login_processes_count = 3 # Maximum number of login processes to create. #login_max_processes_count = 128 # Maximum number of connections allowed per each login process. #login_max_connections = 256 We are running in the high-performance mode, where each login process can handle a number of connections. As I understand it that means we have login_max_connections * login_max_processes_count...

I'm getting "Maximum number of mail processes exceeded" messages when 512 imap Processes are active. Dovecot reports: Warning: fd limit 1024 is lower than what Dovecot can use under full load (more than 1712). Either grow the limit or change login_max_processes_count and max_mail_processes settings But in my /var/service/dovecot/run script I use: #!/bin/sh mkdir /var/core chmod 1777 /var/core echo /var/core/%p > /proc/sys/kernel/core_pattern ulimit -n unlimited ulimit -c unlimited /usr/local/sbin/dovecot -F So how can I raise the filedescriptor limit abov...

...d without complaint, becoming completely unresponsive. I had to kill -9 it this morning in order to restart the service. Once possibility I considered was that the dovecot user process limit was reached, but this is set to 1024, and I didn't see any errors or warnings anywhere in the logs. login_max_processes_count = 256 max_mail_processes = 1024 With the above I would think it would have been able to handle it gracefully, but apparently it did not. ulimit -n 2048 is also set on dovecot startup for the fd limit. Any suggestions on what I could tweak to prevent this from happening in the future? dovecot...

...ssertion failed: (seq_range _exists(&ibox->recent_flags, uid)) I did apply the assertion fix that Timo sent out. # 1.1.2: /userM/mail-services/dovecot/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 3072). Either grow the limit or change login_max_processes_count and max_mail_processes settings base_dir: /userM/mail-services/dovecot/var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /userM/mail-services/dovecot/etc/ssl/dovecot.pem ssl_key_file: /userM/mail-services/dovecot/etc/ssl/privkey.pem ssl_parameters_regenerate: 0 ssl_cipher_list: MEDIU...

After a few hours of running, I get tons of the following errors in my logs: dovecot: Oct 08 07:41:50 Error: auth(default): ldap(user at domain,x.x.x.x): Request queue is full I removed the username and IP, obviously. Any idea how to stop this? I have about 5 Thousand users using horde that login ever 1-5 minutes to refresh their page. I assume it is a setting, but I am confused as to