DirectAdmin User cannot login to dovecot after update to 2.4.1-4

C

CISWS

Verified User
Joined
Aug 4, 2016
Messages
12
Good day to all,

Yesterday I have updated my webservers to DirectAdmin 1.676 including dovecot 2.4.1-4. Now I have some (luckily just a very few) users that cannot login any more into the mail. Roundcube, imap and pop3 logins fail. This only happens to the main DirectAdmin e-mail accounts (so the accounts without @domain.com). The normal (virtual) e-mail accounts seem to work without any issues. I didn't also receive complaints from users other than the few using a DirectAdmin account.

I already tried to rebuild dovecot one more time but that didn't solve the problem. The OS is Alma Linux 8.10. Is this is known issue and is there a fix for this?

Best regards
Roland



PS: a short piece of the log for a login attempt to Roundcube:

Code: 
Apr 23 09:11:23 ws11 dovecot[160686]: auth-worker(************,::1)<161364><31gTz2wz6KEAAAAAAAAAAAAAAAAAAAAB>: request [9]: Error: unix_user: pam_authenticate() failed: Authentication failure (/etc/pam.d/dovecot missing?)
Apr 23 09:11:25 ws11 dovecot[160686]: imap-login: Login aborted: Connection closed (auth failed, 1 attempts in 2 secs) (auth_failed): user=<************>, method=PLAIN, rip=::1, lip=::1, secured, session=<31gTz2wz6KEAAAAA
 
If the mail address is like [email protected] and username1 is used to login, change the username1 of the account to a new one (for example username2) and add a new mailbox with that username1 so [email protected] still can used.

OR

You can manually modify /usr/virtual/domain.tld/passwd file to add the username to access as before.
 
Achterstraat said:
You can manually modify /usr/virtual/domain.tld/passwd file to add the username to access as before.
Click to expand...

That would be a work-around. But where are the data stored? It's not in /home/username1/imap/domain.tld/

Edit: found it in /home/username1/Maildir
 
I have added this line to /etc/virtual/domain.tld/passwd:

username1:$6$u_hidden_hash_bhw5.:1037:12::/home/username1/Maildir:/bin/false:userdb_quota_rule=*:bytes=0M userdb_quota_storage_size=0M

and I can login to Roundcube with [email protected] but Roundcube says "Mailbox is empty"
 
I have changed the configuration file and now I have my mailbox back up and running. I just had to change the login username to the full email address.

@zEitEr : I'll (try to) remember this method when I run into this again.

Thanks to all for your support.
 
We had the same issue with one of our customers which use DA user (= system user) to use Dovecot.
After the Dovecot upgrade we got the same issue.

Code: 
 Error: unix_user: pam_authenticate() failed: Authentication failure (/etc/pam.d/dovecot missing?)
I've created the /etc/pam.d/dovecot file and it works again.
Code: 
# cat /etc/pam.d/dovecot
auth    required        pam_unix.so
account required        pam_unix.so

I've checked the release notes again https://github.com/dovecot/core/releases/tag/2.4.1.
I see the following line:
Code: 
auth: Change unix_listener/auth-userdb/group = $SET:default_internal_group
This change needs dovecot_config_version=2.4.1.

Could it be that DirectAdmin must update the dovecot config for this new version?
 
I'd like to report an issue that started after upgrading to Dovecot 2.4 on a server running CloudLinux 9 and DirectAdmin 1.676.


Dovecot works fine for a short time after startup, but once the number of connections increases (over 1000 active IMAP sessions during peak hours), the dovecot/auth process starts accumulating wait, and the service stops accepting new connections. There are no errors in the logs and no signs of resource or limit exhaustion – it just freezes.


Example from ps:

dovecot/anvil [399 connections] dovecot/auth [1329 wait, 0 passdb, 0 userdb]

For comparison, the exact same setup and load work flawlessly with Dovecot 2.3.
Click to expand...


The server hosts over 3,000 accounts and tens of thousands of mailboxes.
We’ve tried increasing limits and adjusting various settings for Dovecot 2.4, but nothing helped.
With Dovecot 2.3, everything runs smoothly – even under heavy load.


I’m attaching our custom Dovecot configurations (from /usr/local/directadmin/custombuild/custom/) in .tar.gz format:

  • For Dovecot 2.4, where the issue occurs,
  • And for Dovecot 2.3, which remains stable under the same conditions.
Click to expand...

The issue has already been reported to DirectAdmin support, but perhaps someone here can help faster – especially if it turns out to be related to configuration (though I doubt it, since the setup is nearly identical between versions).


Due to this issue, we had to temporarily roll back to Dovecot 2.3 to ensure mail service stability.


Has anyone else experienced similar problems with Dovecot 2.4?
 

Attachments

Yes, we had those settings already applied in Dovecot 2.4 before reverting to 2.3:
service imap-login {
client_limit = 262144
vsz_limit = 8GB
service_restart_request_count = 100
process_limit = 262144
process_min_avail = 32
user = dovecot
}
service pop3-login {
client_limit = 262144
vsz_limit = 8GB
service_restart_request_count = 100
process_limit = 262144
process_min_avail = 32
user = dovecot
}
Click to expand...


We also tried increasing service_restart_request_count to 1000, 10000, and even unlimited – none of those helped.
Dovecot 2.4 continued to freeze under higher load, which eventually forced us to go back to version 2.3.
 
You must log in or register to reply here.
Back
Top