dovecot - Jun 2013 - LDA Connection Refused with auth-userdb

Hi there,

I've encountered an issue with the LDA in which I get a "Connection
refused" error.

There is a serverfault question (
http://serverfault.com/questions/517262/dovecot-with-postfix-configuration-has-connection-refused-when-accessing-auth)
if you would like to read that version, otherwise, the details are as
follows:

Dovecot 2.0.19
Postfix 2.9.6
Ubuntu 12.04

The actual error message I receive is
---------------------------------------------------------------

postfix/pickup[16842]: 019023A06AB: uid=1000 from=<vagrant>
postfix/cleanup[19542]: 019023A06AB: message-id<20130620140358.019023A06AB at
mail-server-berkshelf>
postfix/qmgr[16843]: 019023A06AB:
from=<vagrant at mail-server-berkshelf.localdomain>, size=382, nrcpt=1
(queue
active)
dovecot: lda: Debug: Loading modules from directory:
/usr/lib/dovecot/modules
dovecot: lda: Debug: Module loaded:
/usr/lib/dovecot/modules/lib90_sieve_plugin.so
---> dovecot: lda: Error: userdb lookup:
connect(/var/run/dovecot/auth-userdb) failed: Connection refused
dovecot: lda: Fatal: Internal error occurred. Refer to server log for more
information.
postfix/pipe[19545]: 019023A06AB: to=<test at chefdovecot.com>,
relay=dovecot,
delay=1.2, delays=0.04/0.01/0/1.1, dsn=4.3.0, status=deferred (temporary
failure)


dovecot -n snippet:
--------------------------------------------------------------

# 2.0.19: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-23-generic x86_64 Ubuntu 12.04 LTS ext4
auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login
auth_socket_path = /var/run/dovecot/auth-userdb
auth_verbose = yes
auth_verbose_passwords = plain
mail_debug = yes
mail_location = maildir:/var/vmail/%d/%n/Maildir
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags
copy include variables body enotify environment mailbox date ihave
passdb {
  args = /etc/dovecot/dovecot-sql.conf.ext
  driver = sql
}
plugin {
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
}
postmaster_address = info@*****.com
protocols = imap pop3 sieve imap pop3
service auth-worker {
  user = vmail
}
service auth {
  unix_listener /var/spool/postfix/private/auth {
    group = postfix
    mode = 0660
    user = postfix
  }
  unix_listener auth-userdb {
    group = vmail
    mode = 0644
    user = vmail
  }
  user = dovecot
}
service managesieve-login {
  inet_listener sieve {
    port = 4190
  }
}
ssl = no
ssl_cert = </etc/ssl/certs/star_***_com.crt
ssl_key = </etc/ssl/private/star_***_com.key
userdb {
  args = uid=5000 gid=5000 home=/var/vmail/%d/%n allow_all_users=yes
  driver = static
}
verbose_ssl = yes
protocol lda {
  info_log_path = /var/log/dovecot-lda.log
  log_path = /var/log/dovecot-lda-errors.log
  mail_plugins = sieve
}
protocol imap {
  mail_max_userip_connections = 20
}




Extra from auth-sql
-----------------------------------------
userdb {
  driver = static
  args = uid=vmail gid=vmail home=/var/vmail/%d/%n allow_all_users=yes
}


File permissions on auth-userdb
-----------------------------------------
srw-r--r-- 1 vmail vmail 0 Jun 20 13:04 /var/run/dovecot/auth-userdb


I have tried changing the permissions and owner of auth-userdb to 777 and
dovecot:dovecot, but there wasn't a change.

Any leads or ideas are appreciated. I'm happy to research on my own, but
atm I'm not sure where to continue looking.

Adam

On Fri, Jun 21, 2013 at 12:54 PM, Adam Ramirez <smadam9 at gmail.com>
wrote:
> ---> dovecot: lda: Error: userdb lookup:
> connect(/var/run/dovecot/auth-userdb) failed: Connection refused
>
[...]

>   unix_listener auth-userdb {
>     group = vmail
>     mode = 0644
>     user = vmail
>   }
>
> File permissions on auth-userdb
> -----------------------------------------
> srw-r--r-- 1 vmail vmail 0 Jun 20 13:04 /var/run/dovecot/auth-userdb
>
[...]
  # The default 0666 mode allows anyone to connect to the socket, but the
  # userdb lookups will succeed only if the userdb returns an "uid"
field
that
  # matches the caller process's UID. Also if caller's uid or gid
matches
the
  # socket's uid or gid the lookup succeeds. Anything else causes a failure.


> I have tried changing the permissions and owner of auth-userdb to 777 and
> dovecot:dovecot, but there wasn't a change.
>
 This sounds strange; did you restart dovecot and Postfix?

Cheers,
Luca