[Dovecot] Deliver: command time exceed limit

[Dominique Feyer]

Here is my configuration (auth parts):

auth_cache_size = 0
auth_cache_ttl = 3600
auth default {
  mechanisms = plain login
  passdb sql {
    args = /etc/dovecot/dovecot-pgsql.conf
  }
  userdb sql {
    args = /etc/dovecot/dovecot-pgsql.conf
  }
  socket listen {
    master {
      path = /var/run/dovecot/auth-master
      mode = 0660
      user = vmail
      group = mail
    }
  }
  user = dovecot
  count = 1
  #ssl_require_client_cert = no
  #ssl_username_from_cert = no
}

The socket is use by deliver ? Right ? So I can't set count to more than
1, if I do that dovecto don't start, the process try to create the
socket, but after the first process start, the socket exist.

I try to add an other section without socket to have more dovecot-auth
process:

auth normal {
  mechanisms = plain login
  passdb sql {
    args = /etc/dovecot/dovecot-pgsql.conf
  }
  userdb sql {
    args = /etc/dovecot/dovecot-pgsql.conf
  }
  user = dovecot
  count = 48
  #ssl_require_client_cert = no
  #ssl_username_from_cert = no
}

Our backend i a pgsql server with a average load of 0.10-0.15

/etc/dovecot/dovecot-pgsql.conf

driver = pgsql
connect = host=10.#.#.# dbname=mail user=mailreader password=secret
default_pass_scheme = CRYPT
password_query = SELECT password FROM users WHERE userid = '%u'
user_query = SELECT '/var/mail/'||home AS home, uid, gid FROM users
WHERE userid = '%u'

The CPU usage by dovecot-auth is quiet normal. The server has load
always under 0.8.

Thanks a lots for your help, 


Le mercredi 08 novembre 2006 à 14:51 +0200, Timo Sirainen a écrit :
> On Wed, 2006-11-08 at 13:44 +0100, Dominique Feyer wrote:
> > After upgrade to the RC12 no more time limit exceed in postfix log, but
> > in the deliver log, I have:
> > 
> > Error: User request from dovecot-auth timed out
> > 
> > How can I improve the performance of the dovecot-auth ?
> > 
> > Can I use the dovecot-auth cache ? It's disable in our configuration ?
> 
> If the deliver is giving such timeouts, then I'd guess that you'll get
> similar problems for pop/imap logins as well.
> 
> What passdb and userdb are you using? auth-cache might help, but I'm
> guessing the problem is that you're using some blocking passdb/userdb
> which causes the whole process to hang while waiting for a reply from
> somewhere.
> 
> How many dovecot-auth processes do you have? The default is one (auth
> section, count=1). Growing that might help. How large is the CPU usage
> by the dovecot-auth?