- "Maildir sync: UID < next_uid (446 < 447, file = .." errors should be fixed
- fixes for detecting changes in uidvalidity and external uidnext changes
- several fixes and cleanups in index file handling. less code than before and now changes to index header also go through transaction log. that should mean that soon I can get mmap_disable = yes to work without reading the main index file more than once.
Are maildir syncing problems finally fixed now? :) I think the "message sequence out of range" problems are fixed now too.
Rest of the important known problems are mostly related to mmap_disable=yes or fcntl_locks_disable=yes settings.
On Mon, May 24, 2004 at 06:16:39AM +0300, Timo Sirainen wrote:
I've upgraded to test12. First glance:
May 24 12:32:40 sp dovecot: Dovecot v1.0-test12 starting up May 24 12:32:51 sp dovecot: imap-login: Login: moe [127.0.0.1] May 24 12:32:51 sp dovecot: imap(moe): Maildir sync: UIDVALIDITY changed (1085306036 -> 1081606448) May 24 12:32:51 sp dovecot: imap(moe): Maildir sync: UIDVALIDITY changed (1085306036 -> 1081780899) May 24 12:33:00 sp dovecot: imap(moe): Transaction log file /home/moe/Maildir/.INBOX.pureftpd/dovecot.index.log: invalid indexid (1085306036 != 1085394780) May 24 12:33:00 sp dovecot: imap(moe): Transaction log file /home/moe/Maildir/.INBOX.rhythmbox/dovecot.index.log: invalid indexid (1085306036 != 1085394780) May 24 12:34:06 sp dovecot: imap(moe): Maildir sync: UIDVALIDITY changed (1085306036 -> 1081606459) May 24 12:34:19 sp dovecot: imap-login: Login: moe [127.0.0.1] May 24 12:34:19 sp dovecot: imap(moe): Transaction log file /home/moe/Maildir/.INBOX.gd/dovecot.index.log: invalid indexid (1085306036 != 1085394859)
- "Maildir sync: UID < next_uid (446 < 447, file = .." errors should be fixed
Haven't seen them anymore, seems fine.
- fixes for detecting changes in uidvalidity and external uidnext changes
Humm. I get a lot of these now:
May 24 13:48:36 sp dovecot: imap(moe): Maildir sync: UIDVALIDITY changed (1085308074 -> 1081682554) May 24 13:48:43 sp dovecot: imap-login: Login: moe [127.0.0.1] May 24 13:49:06 sp dovecot: imap(moe): file mail-index.c: line 138 (mail_index_mmap): assertion failed: (map->buffer == NULL) May 24 13:49:06 sp dovecot: child 28181 (imap) killed with signal 6
Are maildir syncing problems finally fixed now? :) I think the "message sequence out of range" problems are fixed now too.
Rest of the important known problems are mostly related to mmap_disable=yes or fcntl_locks_disable=yes settings.
They're both on default for me (commented out).
best regards
One more note... Opening large folders seems *much* zippier with test12 than ever before. My 6k-msg folder opens up in ~4s now. Before test12 it used to be more like 12-20s.
Kudos! :)
On Mon, May 24, 2004 at 02:28:26PM +0200, Moe Wibble wrote:
On Mon, May 24, 2004 at 06:16:39AM +0300, Timo Sirainen wrote:
- "Maildir sync: UID < next_uid (446 < 447, file = .." errors should be fixed
Haven't seen them anymore, seems fine.
Sorry, I must correct myself. I get them again, it seems to happen once every 2-3 hours:
May 25 16:24:57 sp dovecot: imap(moe): Maildir sync: UID < next_uid (475 < 476, file = msg._K4:2,)
I notice them every time because my mutt is running all day and every time it happens the connection is dropped.
-mw
Hi Timo and list,
On May 24, 2004, at 5:16 AM, Timo Sirainen wrote:
- "Maildir sync: UID < next_uid (446 < 447, file = .." errors should be fixed - fixes for detecting changes in uidvalidity and external uidnext changes - several fixes and cleanups in index file handling. less code than before and now changes to index header also go through transaction log. that should mean that soon I can get mmap_disable = yes to work without reading the main index file more than once.
Are maildir syncing problems finally fixed now? :) I think the "message sequence out of range" problems are fixed now too.
Rest of the important known problems are mostly related to mmap_disable=yes or fcntl_locks_disable=yes settings.
With test 12 I get a lot of these errors on my test box (using NFS &
both settings above set to yes, so this is probably known):
May 24 15:43:57 fruttel dovecot: imap(user@domain.tld):
file_try_lock() failed with file
/var/mail/mounted/d/do/domain.tld/user/Maildir/.INBOX/ dovecot.index.tmp: Operation not supported May 24 15:43:57 fruttel dovecot: imap(user@domain.tld): file
mail-transaction-log.c: line 710 (mail_transaction_log_file_map):
assertion failed: (start_offset <= end_offset) May 24 15:43:57 fruttel dovecot: child 1710 (imap) killed with signal 6 May 24 15:44:02 fruttel dovecot: imap-login: Login: user@domain.tld
[172.31.5.186] May 24 15:44:02 fruttel dovecot: imap(user@domain.tld):
file_try_lock() failed with file
/var/mail/mounted/d/do/domain.tld/user/Maildir/.INBOX/ dovecot.index.tmp: Operation not supported May 24 15:44:06 fruttel dovecot: imap-login: Login: user@domain.tld
[172.31.5.186] May 24 15:44:06 fruttel dovecot: imap(user@domain.tld):
file_try_lock() failed with file
/var/mail/mounted/d/do/domain.tld/user/Maildir/.INBOX/ dovecot.index.tmp: Operation not supported
I can log in and read mail using pop3, but imap won't work using apples
"mail.app" or microsofts "outlook express".
pop3 stops working after I have tried to log in using imap, until I
remove the index* files from the .INBOX/ folder. Pop3 only checked
manually, don't know enough of imap's syntax to try manually. My
mail.app claims "select" is going wrong.
Kind regards,
Maikel Verheijen Ladot Nederland BV.
On Mon, 2004-05-24 at 17:49, Maikel Verheijen wrote:
May 24 15:43:57 fruttel dovecot: imap(user@domain.tld):
file_try_lock() failed with file
/var/mail/mounted/d/do/domain.tld/user/Maildir/.INBOX/ dovecot.index.tmp: Operation not supported
Oh, hadn't noticed this. Was a simple fix anyway.
I can log in and read mail using pop3, but imap won't work using apples
"mail.app" or microsofts "outlook express".pop3 stops working after I have tried to log in using imap, until I
remove the index* files from the .INBOX/ folder. Pop3 only checked
manually, don't know enough of imap's syntax to try manually. My
mail.app claims "select" is going wrong.
But did IMAP fail because of the above error? Try again with test13 once I release it before I go to sleep.. :)
Timo Sirainen tss@iki.fi writes:
But did IMAP fail because of the above error? Try again with test13 once I release it before I go to sleep.. :)
Hmmm... CVS reports v1.0-test10 *shrug*
-- Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
Timo Sirainen tss@iki.fi writes:
BTW, is NAMESPACE planned for 1.0?
-- Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
On 25.5.2004, at 06:46, Matthias Andree wrote:
Timo Sirainen tss@iki.fi writes:
BTW, is NAMESPACE planned for 1.0?
It's already in 1.0-tests. Example below, used for converting existing uw-imap installations with various namespace-prefixes to Dovecot.
inbox = yes is used for namespace that contains INBOX. Each namespace also has location parameter which defaults to default_mail_env if not set. So it's possible to have mixed maildir/mbox namespaces. hidden = yes means it's hidden from NAMESPACE reply.
namespace private { separator = . inbox = yes prefix = } namespace private { separator = / prefix = mail/ hidden = yes } namespace private { separator = / prefix = ~/mail/ hidden = yes } namespace private { separator = / prefix = ~/Maildir/ hidden = yes } namespace private { separator = / prefix = ~%u/mail/ hidden = yes }
Timo Sirainen wrote:
Are maildir syncing problems finally fixed now? :) I think the "message sequence out of range" problems are fixed now too.
I'm not sure if it counts as a problem but after the delivery of some email tonight (again only a few messages arrive every day) I got the following noise from -test12:
May 25 03:08:27 myriad dovecot: imap(andrew): Maildir sync: UIDVALIDITY changed (1085364928 -> 1084812656) May 25 03:18:27 myriad dovecot: imap-login: Login: andrew [192.168.0.2] May 25 03:18:27 myriad dovecot: imap(andrew): Transaction log file /home/andrew/Maildir/.INBOX/dovecot.index.log: invalid indexid (1085364928 != 1085451507)
I configured dovecot with --debug-enable so perhaps that accounts for the noise? It didn't result in imap dying in the way that my previously reported problem did with -test11 anyway.
Andrew
On 25.5.2004, at 08:13, Andrew Boothman wrote:
I'm not sure if it counts as a problem but after the delivery of some email tonight (again only a few messages arrive every day) I got the following noise from -test12:
May 25 03:08:27 myriad dovecot: imap(andrew): Maildir sync: UIDVALIDITY changed (1085364928 -> 1084812656)
This is probably because originally Dovecot didn't use the UIDVALIDITY from your existing dovecot-uidlist files. Now it finally notices that it's different, complains about it and marks the index corrupted. It should happen again after this for the same mailbox .. Looks like the error message is missing mailbox path, I'll add that.
May 25 03:18:27 myriad dovecot: imap-login: Login: andrew [192.168.0.2] May 25 03:18:27 myriad dovecot: imap(andrew): Transaction log file /home/andrew/Maildir/.INBOX/dovecot.index.log: invalid indexid (1085364928 != 1085451507)
This happens because index is recreated.
participants (5)
-
Andrew Boothman
-
Maikel Verheijen
-
Matthias Andree
-
Moe Wibble
-
Timo Sirainen