search for: auth_worker_max_request_count

Hi, I am running dovecot with postfix and OTRS2 on a fresh Ubuntu 8.10 Server system. OTRS2 is configured to poll new email to otrs-incoming at localhost via POP3 every 5 minutes. It works, but after approximately 20 hours it suddenly stops working and only a restart of dovecot helps. The outage starts at different times during night (00:15 on Thursday, 1:15 on Friday, 3:20 on

Hello List, I have a question about dovecot-1.1.0-beta3 but first I'll ramble a little bit: Recently I upgraded a 0.99 installation of dovecot to 1.0.5. All went relatively smoothly until the dovecot-auth process began returning "out of memory" after a day. There is a rather large user base here. The current setup is using passdb pam with blocking=yes, with pam_ldap.so handling

...ncluded. I'll fix it after v1.1. * Removed THREAD=X-REFERENCES2 also because it wasn't as easy to implement with the old threading code. I might put this back though if there's enough interest. * PAM always works in blocking=yes mode now. If you have problems with memory leaks, change auth_worker_max_request_count setting. + Filesystem quota backend supports inode limits, group quota and RPC quota for NFS. + SEARCH and SORT finally compare all characters case-insensitively. We use i;unicode-casemap algorithm. + Config files support splitting values to multiple lines with \ + Winbind NTLM and GSS-SPNEGO...

Just setup a new server on the weekend with Ubuntu 8.10 beta, and Dovecot 1.1.4. Every now and then, the IMAP server dies, and won't let users authenticate. It happens about once or twice a day. In /var/log/mail.log, you can see dovecot complaining about critial errors: Oct 21 14:46:16 tachikoma dovecot: imap-login: Login: user=<jason>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS

Hi all! I`m using dovecot for a while with no problems. Some days ago it started to delay the authentication until the timeout. syslog... Oct 3 09:00:10 coan dovecot: auth(default): pam(rodrigo.botan,121.120.119.179): pipe() failed: Too many open files Oct 3 09:00:11 coan dovecot: auth(default): pam(katia,121.120.200.97): pipe() failed: Too many open files Oct 3 09:00:11 coan dovecot:

>From /var/log/auth.log (Dovecot 1.1.4 on Ubuntu 8.10): Feb 10 08:29:06 home dovecot-auth: PAM unable to dlopen(/lib/security/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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Running Dovecot 1.1.3 and after dovecot has been running for awhile it will just stop authenticating. Only fix is to stop and restart dovecot. Here is the errors in the logs: ct 4 09:34:32 goku dovecot: [ID 107833 mail.info] auth-worker(default): pam(KVogel22,74.125.78.25): lookup service=dovecot Oct 4 09:34:32 goku dovecot: [ID 107833

Hi, I'm using dovecot 1.1.3 on FreeBSD 6.3, x86, files are on NFS, except control and index files, which are local, on UFS2. It's moderately loaded, there are usually not more than 30 clients simultaneously. dovecot runs fine for 3-10 days, then people can't connect any more, and dovecot says: Nov 18 13:20:44 dizzy dovecot-auth: pam_ldap: ldap_simple_bind Can't contact LDAP

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Been running dovecot 1.1.2 for about a month now. I Have strange issue that I have not been able to trouble shoot. What I'm seeing is that dovecot runs along just fine for about 4 days, and then it will just stop authenticating everyone (IMAP and POP). No errors in the logs other than all authentication attempts comes out as password mismatch.

.... UW-IMAP compatibility namespaces didn't work). - dict quota: Don't crash when recalculating quota (when quota warnings enabled). - Fixes to handling "out of disk space/quota" failures. - Blocking passdbs/userdbs (e.g. PAM, MySQL) could have failed lookups sometimes when auth_worker_max_request_count was non-zero. - Fixed compiling with OpenBSD Largest changes since v1.2.alpha2: + Added userdb checkpassword (by Sascha Wilde) + Autocreate plugin: http://wiki.dovecot.org/Plugins/Autocreate + Listescape plugin: http://wiki.dovecot.org/Plugins/Listescape - All the same fixes as for v1.1.5 I...

.... UW-IMAP compatibility namespaces didn't work). - dict quota: Don't crash when recalculating quota (when quota warnings enabled). - Fixes to handling "out of disk space/quota" failures. - Blocking passdbs/userdbs (e.g. PAM, MySQL) could have failed lookups sometimes when auth_worker_max_request_count was non-zero. - Fixed compiling with OpenBSD Largest changes since v1.2.alpha2: + Added userdb checkpassword (by Sascha Wilde) + Autocreate plugin: http://wiki.dovecot.org/Plugins/Autocreate + Listescape plugin: http://wiki.dovecot.org/Plugins/Listescape - All the same fixes as for v1.1.5 I...

Hi! I'm running 1.1rc4 on a system and this happens occasionally: --8<-- mail.info; dovecot: auth(default): client in: AUTH 1 PLAIN service=imap lip=NN.NN.NN.NN rip=NNN.NN.NNN.NN lport=143 mail.info; dovecot: auth-worker(default): pam(XXXXXXXXXXXX,NNN.NN.NNN.NN): lookup service=imap kern.alert; kernel: grsec: From NN.NN.NN.NN: denied resource overstep by requesting

Good afternoon, I am considering to upgrade from Dovecot 1.1.18 to 1.2.x and was reading your Wiki regarding any changes and found: "If you were using e.g. mail_location = maildir:/var/mail/%h, just change it to mail_location = maildir:%h and add /var/mail/ prefix to home dirs." I am currently using: "mail_location = maildir:~/Maildir" in combination with vpopmail. Does

Hello Trying to setup dovecot installation with sieve plugin, can't configure how to make redirect working. My setup 1 Exim + dovecot lda begin transports dovecot_virtual_delivery: driver = pipe command = /usr/local/dovecot/libexec/dovecot/deliver -d $local_part message_prefix = message_suffix = delivery_date_add envelope_to_add return_path_add log_output user = exim 2

..._greeting = Involved login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c login_log_format = %$: %s default_mail_env = maildir:/home/vmail/domains/%d/%u first_valid_uid = 103 pop3_uidl_format = %08Xu%08Xv auth_cache_size = 10485760 auth_cache_ttl = 3600 auth_worker_max_count = 10 #auth_worker_max_request_count = 50 auth default { mechanisms = PLAIN LOGIN passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } socket listen { master { path = /var/run/dovecot/auth-master...

I would guess this is unlikely to be dovecot's fault, but I'm wondering if anyone has any ideas of what might have happened based on the evidence. My best guess is some kind of resource limit was reached but I don't see any evidence in the logs, and the condition is now gone. Suddenly this morning, one (and only one) of my dovecot servers decided to start failing all logins since

...esses. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 # Number of auth requests to handle before destroying the process. This may # be useful if PAM plugins leak memory. #auth_worker_max_request_count = 0 # Host name to use in GSSAPI principal names. The default is to use the # name returned by gethostname(). #auth_gssapi_hostname = # Kerberos keytab to use for the GSSAPI mechanism. Will use the system # default (usually /etc/krb5.keytab) if not specified. #auth_krb5_keytab = # Do NTLM auth...