search for: shutdown_clients

I try to restart dovecot 2.2.24 (for changing limits) without killing all IMAP and POP3 sessions. dovecot(1) tells me: When shutdown_clients is set to no, existing sessions will continue to use the old settings, after a dovecot reload. Also all sessions will keep alive after a dovecot stop. By default all active sessions will be shut down. According to my "dovecot -n" (see below), I have set "shu...

...re stalled, and needs a kill -9 to die. This is a problem because those stalled connections are still connected to backends, so when new connections are made from the same account, they do not end up on the same backend and thus index corruption happens (same account, two different backends). shutdown_clients is enabled but it appears Dovecot restarts regardless of verifying all processes/clients are shut down. Just had this happen upon yum update from dovecot-2.3.11.3-3 to dovecot-2.3.11.3-4 -- Tom

...build the new version into /usr/local/dovecot-X.Y.Z and test. To actually switch over the live service to the new X.Y.Z version do I need to: a) Totally shut down the old A.B.C version of Dovecot, thereby breaking all open connections for users? or b) Assuming I am using "shutdown_clients = no" can I just kill the master "dovecot" process and then start up the new version? Ideally I want existing connections to remain running, but new connections to start up using the new X.Y.Z version of Dovecot. The comment for "shutdown_clients" implies this,...

Am 30.08.19 um 10:00 schrieb Christian Balzer via dovecot: > When upgrading on Debian Stretch with the security fix packages all > dovecot processes get killed and then restarted despite having > "shutdown_clients = no" set. This is systemd doing its "magic" (kill all control group processes), see https://dovecot.org/pipermail/dovecot/2016-June/104546.html for a potential fix.

...proxy session on the proxy servers and 25k imap processes on the mailbox servers sound? Even on a server with just 6k users and 7k imap processes that causes a massive load spike and a far longer service interruption (about 50 seconds) than I'm happy with. Penultimately if people do set "shutdown_clients = no" they hopefully know what they are doing and do expect that to work. Regards, Christian On Fri, 30 Aug 2019 17:44:23 +0200 Daniel Lange via dovecot wrote: > Am 30.08.19 um 17:38 schrieb Daniel Lange via dovecot: > > Am 30.08.19 um 10:00 schrieb Christian Balzer via dovecot:...

...; I rotate logs every night on my Director, running "doveadm log reopen" > > It happens on "/etc/init.d/dovecot restart", not "doveadm log reopen" > - sorry > > So it happens when you run killproc on dovecot > > --- > Tom Do you happen to have shutdown_clients=no ? Aki

...ery client is forced to relogin in the same time and that causes a huge system load spike (2-3000 5 min load). I was thinking that it would be great, if dovecot wouldn't kick all the users in the same time during reload, but somehow gradually, during specified interval. I'm aware of the shutdown_clients directive that could help, but I don't like it - I do want the clients get disconnected on dovecot shutdown and also I want them to relogin in reasonably short time after reload. Is something like that possible with dovecot or does it make sense to implement that in the future versions? T...

...iguration. When that > happen, every client is forced to relogin in the same time and that > causes a huge system load spike (2-3000 5 min load). > Unless you're making a change that affects the dovecot master process, restarting everything isn't needed and you should set "shutdown_clients = no". You could still kick users with "dovecot kick" at a leisurely pace, but security problems with the mail processes are rare. > I was thinking that it would be great, if dovecot wouldn't kick all the > users in the same time during reload, but somehow gradually, dur...

Hi! Is it necessary for Dovecot2 to send it a SIGHUP when I rotate its log files? I'm asking because then I must turn off the 'shutdown_clients' option, because then every user gets disconnected while rotating the logs. Daniel -- L?VAI D?niel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F

...e some things. What I need is an IMAP-Server which restricts the user to the following: - no folder createable - no messages deleteable How to get what I want? My Version: Debian x86 Squeeze, Dovecot 1:1.2.15-7. Many thanks in advance! Goran --- protocols = imaps disable_plaintext_auth = yes shutdown_clients = yes log_timestamp = "%Y-%m-%d %H:%M:%S " ssl = yes ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl dotlock auth default { mechanisms = plain...

Hi, i have configured my dovecot-proxy with "shutdown_clients = no" and "service_count = 1" for a "default_process_limit = 5000" and "default_client_limit = 25000". I don't know if this is a prefered setup for so many users/concurrent sessions but so i can reload my dovecot without disconnecting all sessions. The main...

Sorry, I checked and it's already ok: # dovecot -a |grep shutdown shutdown_clients = yes >----Messaggio originale---- >Da: eduardo at freedominterface.org >Data: 13/11/2014 2.18 >A: <dovecot at dovecot.org> >Ogg: Re: pop3/imap hanging processes > >Take a look at ' shutdown_clients' parameter. > >http://wiki2.dovecot.org/RunningDovecot...

...dotlock mbox_write_locks = dotlock mmap_disable = yes passdb { driver = shadow } protocols = pop3 service pop3-login { client_limit = 10 inet_listener pop3 { address = 216.223.136.7 port = 110 } process_limit = 128 process_min_avail = 5 service_count = 0 vsz_limit = 512 M } shutdown_clients = no ssl = no userdb { args = blocking=yes driver = passwd } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_enable_last = yes pop3_lock_session = yes pop3_reuse_xuidl = yes pop3_save_uidl = yes }

...25373 0.0 0.0 12496 3196 ? S 09:41 0:00 dovecot/config root 25418 0.0 0.0 132168 852 pts/1 S+ 09:43 0:00 grep dovecot Now on production server where are tons of clients this looks more insane: # ps aux|grep dovecot/config | wc -l 56 Note that I'm running with shutdown_clients = no here (+ high performance auth/login variant). So looks like something is not right here. Obviously with shutdown_clients=yes this doesn't occur since clients are disconnected. doveadm reload can happen every 2 minutes (because dovecot requires reload when SSL certificates change; new dom...

...]> cat dovecot-acl owner lr user=typ lr But user typ can delete messages. But ACL seems working because if I remove letter 'l' from typ's setting he cannot see the folder. Here is my config: ----------8<------------ protocols = imap ssl_disable = yes disable_plaintext_auth = no shutdown_clients = yes log_path = /var/log/dovecot/sys.log info_log_path = /var/log/dovecot/info.log login_process_size = 64 verbose_proctitle = yes first_valid_gid = 0 mail_extra_groups = mail default_mail_env = mbox:/var/mail/%u:INDEX=/home/user/%u:INBOX=/var/mail/%u namespace private { separator = / prefix...

...ible authentication case that it really works. I'll soon create a CVS branch which is going to stabilize into the 1.0 release. I won't add new features there so it shouldn't really get broken anymore, at least because of new features.. So, two changes in this release: + Added shutdown_clients setting to control if existing imap/pop3 processes should be killed when master is. - Master login fixes, PLAIN authentication was still broken.. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size...

...ible authentication case that it really works. I'll soon create a CVS branch which is going to stabilize into the 1.0 release. I won't add new features there so it shouldn't really get broken anymore, at least because of new features.. So, two changes in this release: + Added shutdown_clients setting to control if existing imap/pop3 processes should be killed when master is. - Master login fixes, PLAIN authentication was still broken.. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size...

...usr/local/bin/dovecot-postlogin.sh } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } shutdown_clients = no ssl_cert = </etc/dovecot/private/fullchain.pem ssl_key = </etc/dovecot/private/privkey.pem syslog_facility = local6 userdb { args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = home=/var/vmail/%Ld/%Ln quota_rule=*:bytes=8589934592 driver = ldap } verbose_proctitle = ye...

...:storage=200M } service auth { client_limit = 32768 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { process_min_avail = 12 service_count = 0 } service pop3-login { service_count = 0 } shutdown_clients = no ssl_cert = </etc/pki/postfix/certs/nexus.pem ssl_key = </etc/pki/postfix/private/nexus_key.pem userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } protocol imap { mail_plugins = $mail_plugins imap_quota } Thanks, -Kurt Hockenbury

...ling TCP_NODELAY. HTTP and SMTP/LMTP connections weren't ? affected, but everything else was. This delay wasn't always visible - ? only in some situations with some message/packet sizes. - imapc: Fix various crash conditions - Dovecot builds were not always reproducible. - login-proxy: With shutdown_clients=no after config reload the ? existing connections could no longer be listed or kicked with doveadm. - "doveadm proxy kick" with -f parameter caused a crash in some ? situations. - Auth policy can cause segmentation fault crash during auth process ? shutdown if all auth requests have not b...