On 11/13/2013 4:34 PM, Benny Pedersen wrote:
Marc Perkel skrev den 2013-11-14 01:13:
I does act like a DNS problem but why is DNS involved? It doesn't have a delay in connecting. It's the login that's slow.
you use a auth that depends on fast dns ?
lost now how your dovecot -n was
are we sure its dns at all ?, i see the INDEX on another path then MAILDIR was, is it 2 diff harddisk drives ?
is it running on shared resources ?
My AUTH depends only on MYSQL. There's no DNS involved. At least not that I can see there should be. So why would localhost take 10-15 seconds to do the login part and coming into the servers IP address is instant. And in both cases the connection itself is instant. It's when I type in the LOGIN command that the delay occurs.
# 2.2.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab083.2 x86_64 CentOS release 6.4 (Final) ext4 auth_master_user_separator = * auth_mechanisms = login plain disable_plaintext_auth = no first_valid_uid = 12 info_log_path = /var/log/dovecot.log log_path = /var/log/dovecot.log login_greeting = Computer Tyme Dovecot ready. mail_fsync = never mail_gid = mail mail_location = maildir:/vhome/%d/home/%n:INDEX=/email/imap-cache/%d-%n mail_uid = mail passdb { args = /etc/dovecot/sql.conf driver = sql } passdb { args = /etc/dovecot/master-combined-sql.conf driver = sql master = yes pass = yes } protocols = imap pop3 service anvil { client_limit = 20000 } service auth { client_limit = 20000 unix_listener auth-client { mode = 0666 } unix_listener auth-master { mode = 0666 } } service imap-login { process_limit = 4000 process_min_avail = 30 service_count = 0 } service imap { process_limit = 4000 } service pop3-login { process_limit = 2000 process_min_avail = 20 service_count = 0 } service pop3 { process_limit = 2000 } ssl_ca =