dovecot Down after upgrade..

C

CBHOSTING

Verified User
Joined
Mar 18, 2010
Messages
17
Hi,

i need Help with my devcot , the service is down.

after the update to 1.37.

Restarting dovecot.
Shutting down dovecot: [FEHLGESCHLAGEN]
Starting dovecot: Error: socket() failed: Address family not supported by protocol
Error: service(pop3-login): listen(::, 110) failed: Address family not supported by protocol
Error: socket() failed: Address family not supported by protocol
Error: service(pop3-login): listen(::, 995) failed: Address family not supported by protocol
Error: socket() failed: Address family not supported by protocol
Error: service(imap-login): listen(::, 143) failed: Address family not supported by protocol
Error: socket() failed: Address family not supported by protocol
Error: service(imap-login): listen(::, 993) failed: Address family not supported by protocol
Fatal: Failed to start listeners
[FEHLGESCHLAGEN]


any idee....


Thanks
 
Is something else listening to the ports? If you dont use ipv6 disable it in /etc/dovecot.conf
 
Hello thanks for answer,

in the config file is nothing from IP6

Code: 
## Dovecot 2.0 configuration file

auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@&
auth_verbose = yes
disable_plaintext_auth = no
login_greeting = Dovecot DA ready.
mail_access_groups = mail
default_login_user = dovecot
mail_location = maildir:~/Maildir
passdb {
  driver = shadow
}
passdb {
  args = username_format=%n /etc/virtual/%d/passwd
  driver = passwd-file
}
protocols = imap pop3
service auth {
  user = root
}
service imap-login {
  process_min_avail = 16
  user = dovecot
}
service pop3-login {
  process_min_avail = 16
  user = dovecot
}
ssl_cert = </etc/httpd/conf/ssl.crt/server.crt
ssl_cipher_list = ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP
ssl_key = </etc/httpd/conf/ssl.key/server.key
userdb {
  driver = passwd
}
userdb {
  args = username_format=%n /etc/virtual/%d/passwd
  driver = passwd-file
}
verbose_proctitle = yes
protocol pop3 {
  pop3_uidl_format = %08Xu%08Xv
}

Sorry for my English...

Thanks
 
My guess is that ipv6 has been disabled on your server somehow and dovecot is confused it cannot bind to an ipv6 ip.

Try:

cd /usr/local/directadmin/custombuild
./build update
./build clean
./build dovecot d

If that doesnt fix it then try overwritting your /etc/dovecot.conf with:

http://files.directadmin.com/services/custombuild/1.2/custombuild/configure/dovecot/dovecot.conf

If that doesnt fix it then you might need to compile dovecot with --disable-ipv6 option on the ./configure line.
 
no i get these error

Starting dovecot: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > d
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:3: protocols=imaps is no longer nec
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:3: protocols=pop3s is no longer nec
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:7: ssl_cert_file has been replaced
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:8: ssl_key_file has been replaced b
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:19: login_user has been replaced by
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:20: login_processes_count has been _min_avail }
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 34: Unknown setting: mai
[FEHLGESCHLAGEN]
Click to expand...

is there any possiblity to reinstall dovecot clear ?
 
Are you still using a dovecot 1.x version of the conf file? Those messages are telling you that there are some deprecated settings in there. Trying doing something like this:
Code: 
doveconf -n -c dovecot-1.conf > dovecot-2.conf
Where the dovecot-1.conf is a copy of your current configuration.

Then review the dovecot-2.conf and if it looks right, then replace your current /etc/dovecot.conf with the converted one.
 
I have not upgraded from 1.2.16 to 2.0.9 yet, because of the problems reported. Can anybody post the commands on how to downgrade from Dovecot 2.0.9 to 1.2.16 using custombuild? I don't think I dare upgrade if I don't have the commands to downgrade ready, in case the upgrade go wrong and I need to downgrade.
 
Would be nice if that "listen" line could be added by default. So others upgrading or at a later time, won't get this problem.
Is that possible?
 
Who are you asking? Why dont you put in a feature request if you want it changed.
 
Support reads here too and it is not -that- important for me. And imho it's not a feature request but rather a bug- or problemfix.

By the way, to whom it concerns:
listen= 110,143,995,993
Click to expand...
This is -not- working on Centos 5.5 32bit.
Dovecot will run without error notices, but you can't send and receive mail.
For expample telnetting to port 110 will give you an error.

After changing this to listen=* like stated by CBhosting, all is working well again.
 
Hello,

I've changed the default dovecot.conf for 2.0 to have these lines at the very top:
Code: 
#IPv4
listen = *

#IPv4 and IPv6:
#listen = *, ::
Our goal was to support IPv6 natively, and for all other services, they seem to be working ok, but for dovecot 2.0, it appears if the box doesn't support it then the internal defaults (*, ::) won't work.

In any case, for now, I've set just the IPv4 as the default until another method of determining the box's IPv6ness can be sorted out.

John
 
DirectAdmin Support said:
Hello,

I've changed the default dovecot.conf for 2.0 to have these lines at the very top:
Code: 
#IPv4
listen = *

#IPv4 and IPv6:
#listen = *, ::
Our goal was to support IPv6 natively, and for all other services, they seem to be working ok, but for dovecot 2.0, it appears if the box doesn't support it then the internal defaults (*, ::) won't work.

In any case, for now, I've set just the IPv4 as the default until another method of determining the box's IPv6ness can be sorted out.
Click to expand...

I just upgraded before you did those changes. I have not discovered any problems with email yet. I am running CentOS 5.5 64bit.

Should I recompile Dovecot in custombuild, or does I not have to do anything?
 
@DA support: thank you!

@Ditto: Just test if you can make a connection to your server by telnetting to port 110, if yes, things should be fine.
If not you should add the line in the config.
 
You must log in or register to reply here.
Back
Top