Large jumps in dovecot-uidlist
Since upgrading to Debian Wheezy I have been observing large jumps in the value stored in dovecot-uidlist. The effect of these jumps is to confuse some mail clients (Thunderbird, Opera Mail) causing them not to display messages from a (random?) point in time onwards in the affected folder.
I have been unable to determine the root cause of these jumps.
What I do know:
I never observed the problem while running Debian Squeeze.
The only way I have found to fix the issue is to remove all the dovecot* files from the affected folder and restart dovecot. I have tried removing various subsets of the dovecot* files but haven't yet found a subset that works.
I first tried upgrading from Squeeze to Wheezy within a few weeks of the Wheezy release. At that point the problem occurred so frequently that I couldn't sync my mail client with my mail box. Multiple folders exhibited this problem and while I was fixing them the problem appeared in other folders. I was unable to reach a point where the system was stable so I reverted back to Squeeze.
Some time later (I think a year but I am not sure) I tried the upgrade to Wheezy again. This time the system was stable. After a few days I noticed that the problem was still occurring but less frequently. Since then I have been fixing the problem as I notice it and experimenting with various settings (mainly locking related) without success. I now have a cron job that looks for problematic folders and fixes them when found.
I have updated Dovecot packages to those from Jessie via wheezy-backports and the problem still occurs.
Dovecot is installed along with postfix, amavisd-new, clamav-daemon, procmail and fetchmail.
The mail server is running on a eSATA SheevaPlug that boots of an external USB drive. All user home dirs (and associated mailboxes) are located on a LUKS/ext3 encrypted partition.
The output of dovecot -n may be found at the end of this mail.
Uid values for the three most recent instances of this problem are: 3801596527, 3371927249, 3443181615
Some folders seem more susceptible to this problem but I have not been able to identify any common factors/triggers.
The problem occurs - on average - once a day.
I am happy to provide any further information, configure any debug logging and/or test suggested configuration settings that may help track down the root cause of this problem.
Any help gratefully appreciated.
Mark
# 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-kirkwood armv5tel Debian 7.8 mail_debug = yes mail_location = maildir:~/Maildir mail_max_userip_connections = 100 namespace { inbox = yes location = mailbox { special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { special_use = \Trash name = Trash } prefix = name = inbox } passdb { driver = pam } protocols = " imap" service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service { unix_listener { group = postfix mode = 0666 user = postfix path = /var/spool/postfix/private/auth-client } name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service { inet_listener { port = 0 name = imap } inet_listener { port = 993 ssl = yes name = imaps } process_min_avail = 5 name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service { executable = imap postlogin name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service { executable = script-login -d rawlog name = postlogin } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl_cert = </etc/ssl/certs/smtpd.crt ssl_cipher_list = HIGH:MEDIUM:!aNULL:!MD5:!RC4 ssl_key = </etc/ssl/private/smtpd.key userdb { driver = passwd } protocol imap { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } }
Am Sonntag, den 14.06.2015, 10:46 +0100 schrieb Mark:
Since upgrading to Debian Wheezy ... # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-kirkwood armv5tel Debian 7.8
So it's dovecot from the backports. Didn't you notice that since about 2 months there's now jessie out? That has 2.2.13 too but maybe it's an issue outside of dovecot in some library. Or just a bug in the backport.
I have no problem at all with my dovecot under jessie. But it's currently only responsible for my own private mails. So it hasn't much to do. Oh and now by looking again at your full mail: I mainly use IMAP + Evolution or on my Android Smartphone K-9 Mail to access them.
On 15/06/2015 17:46, Felix Zielcke wrote:
Am Sonntag, den 14.06.2015, 10:46 +0100 schrieb Mark:
Since upgrading to Debian Wheezy ... # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-kirkwood armv5tel Debian 7.8
So it's dovecot from the backports. Didn't you notice that since about 2 months there's now jessie out?
I did. Based on my previous experience of upgrading Debian as soon as the new release was announced and having to roll everything back because of this problem I'm taking a more cautious approach this time.
That has 2.2.13 too but maybe it's an issue outside of dovecot in some library. Or just a bug in the backport.
Possibly. I'm not against doing the full upgrade to Jessie to see what effect that has. I've been running the backport for a while and the problem certainly hasn't got worse. I'll see if I can find some time in the next few days to try the upgrade.
I have no problem at all with my dovecot under jessie. But it's currently only responsible for my own private mails. So it hasn't much to do.
This install supports three users who access via IMAP using various combinations of Thunderbird, Opera Mail, native iPhone client, native Android client and K9.
It seems to be the case that the mobile clients handle the UID jump gracefully whereas the desktop clients can't handle the larger UIDs.
Oh and now by looking again at your full mail: I mainly use IMAP + Evolution or on my Android Smartphone K-9 Mail to access them.
Thanks,
Mark
On 15/06/2015 18:04, Mark wrote:
On 15/06/2015 17:46, Felix Zielcke wrote:
Am Sonntag, den 14.06.2015, 10:46 +0100 schrieb Mark:
Since upgrading to Debian Wheezy ... # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-kirkwood armv5tel Debian 7.8
So it's dovecot from the backports. Didn't you notice that since about 2 months there's now jessie out?
I did. Based on my previous experience of upgrading Debian as soon as the new release was announced and having to roll everything back because of this problem I'm taking a more cautious approach this time.
That has 2.2.13 too but maybe it's an issue outside of dovecot in some library. Or just a bug in the backport.
Possibly. I'm not against doing the full upgrade to Jessie to see what effect that has. I've been running the backport for a while and the problem certainly hasn't got worse. I'll see if I can find some time in the next few days to try the upgrade.
I haven't found the time to do the upgrade to Jessie yet but I have tweaked my checking script to run more frequently. That gave me a narrower window to look at in the logs and these messages appear at the same time as the jump is introduced into the UID list:
Jun 19 17:00:57 server02 dovecot: imap(mark): Error: Log synchronization error at seq=2,offset=152 for /secure/home/mark/Maildir/.Apache.Misc.committers/dovecot.index: Append with UID 2427206830, but next_uid = 2685375011 Jun 19 17:00:57 server02 dovecot: imap(mark): Warning: fscking index file /secure/home/mark/Maildir/.Apache.Misc.committers/dovecot.index
I've done some Googling but haven't (yet) found anything that might match up.
I'm hoping that the above might provide enough information to someone more familiar with Dovecot than me to suggest what I might be able to do to fix this. If not, I'll see what happens post Jessie upgrade.
Thanks in advance,
Mark
On 19/06/2015 18:41, Mark wrote:
On 15/06/2015 18:04, Mark wrote:
On 15/06/2015 17:46, Felix Zielcke wrote:
Am Sonntag, den 14.06.2015, 10:46 +0100 schrieb Mark:
Since upgrading to Debian Wheezy ... # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-kirkwood armv5tel Debian 7.8
So it's dovecot from the backports. Didn't you notice that since about 2 months there's now jessie out?
I did. Based on my previous experience of upgrading Debian as soon as the new release was announced and having to roll everything back because of this problem I'm taking a more cautious approach this time.
That has 2.2.13 too but maybe it's an issue outside of dovecot in some library. Or just a bug in the backport.
Possibly. I'm not against doing the full upgrade to Jessie to see what effect that has. I've been running the backport for a while and the problem certainly hasn't got worse. I'll see if I can find some time in the next few days to try the upgrade.
I haven't found the time to do the upgrade to Jessie yet but I have tweaked my checking script to run more frequently. That gave me a narrower window to look at in the logs and these messages appear at the same time as the jump is introduced into the UID list:
Jun 19 17:00:57 server02 dovecot: imap(mark): Error: Log synchronization error at seq=2,offset=152 for /secure/home/mark/Maildir/.Apache.Misc.committers/dovecot.index: Append with UID 2427206830, but next_uid = 2685375011 Jun 19 17:00:57 server02 dovecot: imap(mark): Warning: fscking index file /secure/home/mark/Maildir/.Apache.Misc.committers/dovecot.index
I've done some Googling but haven't (yet) found anything that might match up.
I'm hoping that the above might provide enough information to someone more familiar with Dovecot than me to suggest what I might be able to do to fix this. If not, I'll see what happens post Jessie upgrade.
One more information point. I still see the same symptoms after upgrading to Jessie.
I haven't been able to see a pattern in the errors yet but I'll keep looking. Spending some time trying to isolate a test case is on my TODO list but until I find the time to do that any other suggestions welcome.
Mark
participants (2)
-
Felix Zielcke
-
Mark