[Dovecot] auth error using director
Hello,
I am trying to configure director as described at http://wiki2.dovecot.org/Director. I have previously tried the proxy and it worked.
The problem I have is that whenever I try to connect I get the error:Jul 1 11:41:41 myotis40 dovecot: pop3-login: Error: auth: connect(director) failed: No such file or directory
This is my doveconf -n:# 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-4-amd64 x86_64 Ubuntu 10.04.2 LTS auth_cache_size = 1 k auth_debug = yes auth_verbose = yes default_process_limit = 256 director_mail_servers = 155.54.211.161 155.54.211.169 director_servers = 155.54.211.170 disable_plaintext_auth = no dotlock_use_excl = no hostname = myotis30 log_timestamp = %Y-%m-%d %H:%M:%S mail_debug = yes mail_fsync = always mail_location = maildir:~/Maildir:INDEX=/var/indexes/%n mail_nfs_storage = yes mail_privileged_group = mail maildir_stat_dirs = yes mdbox_rotate_size = 20 M namespace { inbox = yes location = prefix = separator = / } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster@um.es protocols = " pop3" service auth { unix_listener auth-userdb { mode = 0666 } } service imap-login { executable = imap-login director } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix user = postfix } } service pop3-login { executable = pop3-login director } ssl = no ssl_cert =
-- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 868887590 Fax: 868888337
Sorry. I have solved the problem. I haven't uncommented the mode directives for the director service, so, I guess, I had a permissions problem.
Just a question about director... The main purpose of it it's to ensure that all connections from a user are directed to the same backend server, so you could rely on correct indexes and minimize index regenerations.
But, I could see there is director_user_expire option, with a default value of 15 minutes. By other way, If I run doveadm director status <user> I could see that there is a hashed server.
Does it means that there is no warrantee that if I connect today to server node1 the connection for tomorrow will be directed to the same server (because this timeout would expire)?
Or does it means that whenever as possible I will be directed to this hashed server and I will be directed to other server just when my hashed server is down (or I have another active session because of a previous downtime)?
-- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 868887590 Fax: 868888337
participants (1)
-
Angel L. Mateo