search for: login_max_connect

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_count=4 login_max_processes_count=8 l...

...141.42.165.160, lip=141.42.4.250, TLS May 16 12:18:23 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=193.175.70.61, lip=141.42.4.250 Should I worry about these messages or are they of informational character only? Does it mean that the imap-login encountered more than "login_max_connections" and thus a new process had to be spawned? Is there a parameter I should be changing (config below) # /usr/local/sbin/dovecot --version 1.0.0 ---- snip --- # /usr/local/etc/dovecot.conf protocols: imap imaps pop3s ssl_cert_file: /etc/ssl/certs/postamt.pem ssl_key_file: /etc/ssl/private/...

...se. We initially spawn off 10 imap-login processes and have each handling 256 connections. Full "dovecot -n" at the end of the message, but the relevant settings here are: login_process_size = 64 login_process_per_connection = no login_processes_count = 10 login_max_processes_count = 128 login_max_connections = 256 We have grown to suspect it is to do with one of the imap-login processes having a large number of files open. Killing the process seems to get rid of the problem. For example currently we have 11 imap-login processes running, one of which has 518 open files -- process 12436 in the lis...

...ile_set_size() failed with index cache file /var/spool/imap/seriv/.imap/dovecot.index.cache: Invalid argument --- One more problem is with fd limit: I have a small dovecot installation, so don't want to increase fd limit. I tried to decreasee max_mail_processes, login_max_processes_count and login_max_connections, but still I have --- # /opt/dovecot/sbin/dovecot -n # 1.1.beta3: /opt/dovecot/etc/dovecot.conf 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 and max_mail_processes settings log_path: /tmp/dove...

...ocmail and mbox and am making my usual careful crawl (at turtle speed) through figuring out DC config. Some questions: a) I have something like 3-4 root imapd sessions so I presume that the default *login_processes_count* = 3 will be OK. I'm less clear about login_max_processes_count and login_max_connections = 256. A common enough heavy load has something like 275 unique users accessing imap and 600 imapd processes. Suggestions? I'm beginning with no SSL, KISS. b) If I set login_process_per_connection =no, would the number of users accessing imap be the same as the number of imapd sessions...

It appears that when running Dovecot as a proxy-only box with "login_process_per_connection = no", it ignores the value of login_max_logging_users. And in Linux, since each socket requires a file descriptor, if you don't increase the maximum number of open files that each process is allowed to have open, imap-login will reach the 1024 open file limit and start logging the following

...ap & pop3 service. When icinga reports that the service is down. We try to telnet to the server on port 110 but it refuses the connection. I've checked the netstat during this time and it's listens on port 110. My first thought we were hitting the max connections and similar. Changed login_max_connections from 128 to 256. Didnt solve the problem. Started the debug on the dovecot server but could not see anything in the logs. Also the error log or the syslog dosnt report anything that I can see. Best thing would of course be to start and upgrade the software and os(Debian 5) but I'm not com...

...imized out>) at ioloop-epoll.c:208 > #12 0x0000000000413b9d in io_loop_run (ioloop=0x6552b0) at ioloop.c:335 > #13 0x0000000000408e81 in main (argc=2, argv=0x7fff57100c58, envp=0x7fff57100c70) at main.c:494 Up until this afternoon we had "login_process_per_connection = yes", and login_max_connections at the default (256). This evening I tried with "login_process_per_connection = no" with no problems, except more CPU load and needing to increase login_max_processes_count (and strictly speaking the max fds set with ulimit -n would need to be increased, though I didn't do that a...

...le 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 available possible logins at a given time. That's 32K with our configuration. That s...

...ated using MySQL my dovecot.conf looks like base_dir = /var/run/dovecot/ protocols = imap pop3 listen = *, [::] log_path =/var/log/dovecot.log info_log_path = /var/log/dovecot-info.log ssl_disable = yes login_process_per_connection = no login_processes_count = 10 login_max_processes_count = 128 login_max_connections = 256 login_greeting = Dovecot ready. mail_location = maildir:~/ mail_debug = yes mmap_disable = yes dotlock_use_excl = yes mail_nfs_index = yes lock_method = dotlock mail_drop_priv_before_exec = yes first_valid_uid = 195 max_mail_processes = 512 mail_process_size = 256 mailbox_idle_check_inter...

...death (ie "Login process died too early - shutting down" or "too many open files" type crash). I've had my third crash today. My setup: Solaris 10, imap and imaps, 3K users coming in via horde webmail. My current connection settings are: login_max_processes_count = 2048 login_max_connections = 4096 Q: Does raising these limits actually make my problem worse or better? Are there any other variables that I should change to prevent the "too many open files"? Suggestions? Jeff Earickson Colby College

...Nov 27 15:10:45 mproxy1 dovecot: child 21677 (login) killed with signal 6 A lot means one every 2 or 3 seconds. Any suggestion ? ---------------- protocols = pop3 imap disable_plaintext_auth = no ssl_disable = yes login_process_size = 64 login_process_per_connection = no login_processes_count = 8 login_max_connections = 256 login_greeting = loktar auth_cache_size = 16384 auth_cache_ttl = 1800 auth_worker_max_count = 30 auth default { mechanisms = plain # Userdb settings are not used with proxy but there need to be something. userdb static { args = static uid=5000 gid=5000 home=/dev/null } passd...

...print "create $pths\'s threads\n"; $i++; $pths--; } my $ret = $t1->join(); =========================dovecot.conf====================== my dovecot.conf about auth is:log_path = /var/log/maillog login_processes_count = 128 #listen_start_process login_max_processes_count = 128 login_max_connections = 128 #login_max_connections = 256 max_mail_processes = 1024disable_plaintext_auth = nologin_process_per_connection=yes thanks amandy

...cot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login login_process_per_connection: no login_process_size: 512 login_processes_count: 20 login_max_processes_count: 3000 login_max_connections: 64 max_mail_processes: 2048 mail_max_userip_connections(default): 20 mail_max_userip_connections(imap): 20 mail_max_userip_connections(pop3): 10 mail_max_userip_connections(managesieve): 10 mail_access_groups: staffmailusers mail_privileged_group: dovecot mail_uid: mail mail_gid: 502 mail_loca...

...: Warning: Obsolete setting in ./dovecot.old.conf:45: login_max_processes_count has been replaced by service { process_limit } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 45: Unknown setting: process_limit doveconf: Warning: Obsolete setting in ./dovecot.old.conf:48: login_max_connections has been replaced by service { client_limit } doveconf: Fatal: Error in configuration file ./dovecot.old.conf line 48: Unknown setting: client_limit doveconf: Warning: Obsolete setting in ./dovecot.old.conf:75: mail_drop_priv_before_exec has been replaced by service { drop_priv_before_ex...

...th: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_process_per_connection: no login_processes_count: 2 login_max_processes_count: 50 login_max_connections: 500 mail_max_userip_connections(default): 20 mail_max_userip_connections(imap): 20 mail_max_userip_connections(pop3): 3 maildir_copy_preserve_filename: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/d...

...ogin_user: dovecot login_greeting: Dovecot ready. login_log_format_elements: user=<%u> method=%m rip=%r lip=%l %c login_log_format: %$: %s login_process_per_connection: yes login_chroot: yes login_trusted_networks: login_process_size: 64 login_processes_count: 3 login_max_processes_count: 128 login_max_connections: 256 valid_chroot_dirs: mail_chroot: max_mail_processes: 512 mail_max_userip_connections: 10 verbose_proctitle: no first_valid_uid: 500 last_valid_uid: 0 first_valid_gid: 1 last_valid_gid: 0 mail_access_groups: mail_privileged_group: mail mail_uid: mail_gid: mail_location: mail_cache_fields: ma...

...msgid=<01c8b6db$0222fe80$b7af2abe at info>: save failed to INBOX: Timeout while waiting for lock My dovecot.conf: $ cat /etc/dovecot.conf | grep -v \# | grep -v ^\n protocols = imap pop3 log_path = /var/log/dovecot.log ssl_disable = yes login_user = dovecot login_process_per_connection = no login_max_connections = 1024 login_greeting = Server is ready. >>dotlock_use_excl = yes - can it be the reason? fsync_disable = yes first_valid_uid = 39 last_valid_uid = 39 first_valid_gid = 39 last_valid_gid = 39 max_mail_processes = 1024 maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = yes...

...%S " login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c login_log_format = %$: %s mail_log_prefix = "%Us(%u): " disable_plaintext_auth = no login_process_per_connection=yes auth_default_realm = example.com login_processes_count = 8 login_max_processes_count = 128 login_max_connections = 256 verbose_proctitle = yes max_mail_processes = 512 mail_debug = yes auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * login_chroot = yes ssl = no protocol imap { imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbo...

.../run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_user: postfix login_greeting: Something witty here.. login_process_per_connection: no login_max_connections: 512 max_mail_processes: 2048 mail_max_userip_connections: 50 verbose_proctitle: yes first_valid_uid: 69 last_valid_uid: 500 first_valid_gid: 69 last_valid_gid: 500 mail_access_groups: postfix mail_privileged_group: postfix mail_location: mbox:/NFS1MAILDIR/mailSysV2/%d/%u:INDEX=/usr/local/mail/...