I upgraded to 2.2.26.0 and enabled count as quota backend, expecting the recent fixes to allow me to use the backend, however I get the following errors:
Oct 31 10:52:13 imap(xxxx@xxxx.xx): Error: Transaction log file /mnt/nfs/xxxx.xx/xxx/indexes/dovecot.list.index.log: marked corrupted Oct 31 10:52:15 imap(xxx@xxxx.xx): Error: Transaction log file /mnt/nfs/xxxx.xx/xxx/indexes/dovecot.list.index.log: marked corrupted Oct 31 10:52:37 imap(xxx@xxxx.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing) Oct 31 10:52:37 imap(xxx@xxx.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing) Oct 31 10:52:43 imap(xxx@xxx.xx): Error: Transaction log file /mnt/nfs/xxx.xx/xx/indexes/dovecot.list.index.log: marked corrupted Oct 31 10:52:52 imap(xxx@xxx.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing) Oct 31 10:53:04 imap(xxx@xxx.x): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 60 seconds (syncing) Oct 31 10:53:06 imap(xxx@xxx.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xxx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing)
(all different accounts)
If I disable count as backend, there are no errors.
I'm running my mail-storage on NFS, so I suspect the errors are due to locking? So is there no way to run count as quota backend with NFS?
Thanks.
Tom
On 2016-10-31 11:01, Tom Sommer wrote:
I upgraded to 2.2.26.0 and enabled count as quota backend, expecting the recent fixes to allow me to use the backend, however I get the following errors:
It just occured to me, that the reason for the locking/errors may be, that it is big mailboxes being recalculated?
Tom
On 31 Oct 2016, at 12:01, Tom Sommer mail@tomsommer.dk wrote:
I upgraded to 2.2.26.0 and enabled count as quota backend, expecting the recent fixes to allow me to use the backend, however I get the following errors:
Oct 31 10:52:13 imap(xxxx@xxxx.xx): Error: Transaction log file /mnt/nfs/xxxx.xx/xxx/indexes/dovecot.list.index.log: marked corrupted Oct 31 10:52:15 imap(xxx@xxxx.xx): Error: Transaction log file /mnt/nfs/xxxx.xx/xxx/indexes/dovecot.list.index.log: marked corrupted
These mean that something marked the index as corrupted. There really should be another error message logged about what did it and why..
Oct 31 10:52:37 imap(xxx@xxxx.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing) Oct 31 10:52:37 imap(xxx@xxx.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing)
This just means something is being slow. Not necessarily a problem. Although it could also indicate a deadlock. Is this Maildir? Did you say you were using lock_method=dotlock?
On 2016-10-31 22:04, Timo Sirainen wrote:
Oct 31 10:52:37 imap(xxx@xxxx.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing) Oct 31 10:52:37 imap(xxx@xxx.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing)
This just means something is being slow. Not necessarily a problem. Although it could also indicate a deadlock. Is this Maildir? Did you say you were using lock_method=dotlock?
I removed dotlock some time ago (using director) and switched to:
lock_method = fcntl mail_fsync = always
With "count" as quota backend I get a lot of these errors on the director:
imap-login: Error: proxy(xxx@xxxx.xxx): Login for xxx.xxx.xxx.xxx:143
timed out in state=2 (after 30 secs, local=xxxxx:58478):
user=xxxx@xxxx.dk, method=CRAM-MD5, rip=xxxx, lip=xxxxx, TLS,
session=
on the server:
imap(xxxx@xxxx.xxx): Warning: Locking transaction log file /mnt/nfs/xxxx.dk/xxxxx/indexes/.INBOX/dovecot.index.log took 32 seconds (appending)
On 2016-11-01 09:47, Tom Sommer wrote:
On 2016-10-31 22:04, Timo Sirainen wrote:
Oct 31 10:52:37 imap(xxx@xxxx.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing) Oct 31 10:52:37 imap(xxx@xxx.xx): Warning: Locking transaction log file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 seconds (syncing)
This just means something is being slow. Not necessarily a problem. Although it could also indicate a deadlock. Is this Maildir? Did you say you were using lock_method=dotlock?
I removed dotlock some time ago (using director) and switched to:
lock_method = fcntl mail_fsync = always
With "count" as quota backend I get a lot of these errors on the director:
imap-login: Error: proxy(xxx@xxxx.xxx): Login for xxx.xxx.xxx.xxx:143 timed out in state=2 (after 30 secs, local=xxxxx:58478): user=xxxx@xxxx.dk, method=CRAM-MD5, rip=xxxx, lip=xxxxx, TLS, session=
on the server:
imap(xxxx@xxxx.xxx): Warning: Locking transaction log file /mnt/nfs/xxxx.dk/xxxxx/indexes/.INBOX/dovecot.index.log took 32 seconds (appending)
Actually this is worse than I thought. I don't know if it's because of the lock, or it's a general bug in 'count', but whenever I switch quota backend to 'count', customers complain that they aren't receiving any mails. Mails are stored correctly on the server, but it seems Dovecot doesn't show them, perhaps due to corrupt/hanging/locked indexes.
So either 'count' is very I/O sensitive by design, and so useless on NFS, or there is some bug in there that breaks indexing.
Using maildir and lmtp.
The only errors I see in the logs, are the ones pasted here.
participants (2)
-
Timo Sirainen
-
Tom Sommer