I've searched the archives and find a lot of references to corrupted indexes but can't seem to find any solutions. It seems like folks either have the problem or they don't. We recently migrated from a RedHat Linux server to an OpenBSD 3.7 server (both using dovecot). Imap was working flawlessly on the RedHat box but now gives numerous index errors. I then upgraded to dovecot-1.0-test66 compiled from ports - still no luck. Here's an example of the errors: Jun 27 12:02:23 mail dovecot: IMAP(epate): Corrupted transaction log file /home/epate/mail/.imap/INBOX/dovecot.index.log: Keyword record UIDs are broken Jun 27 12:02:24 mail dovecot: IMAP(epate): Lost transaction log file /home/epate/mail/.imap/INBOX/dovecot.index.log seq 7 I found references to "disabling indexing" but they don't say how. Would this be a reasonable temporary solution? Any other suggestions? Thanks for your help, Emmett Pate
It sounds to me like the db libraries used on the two systems are different (and incompatible). I would delete all the .log files. Dovecot will regenerate them as needed, in the new format. -Ben On 6/27/05, Emmett Pate <emmett at epate.com> wrote:> I've searched the archives and find a lot of references to corrupted indexes > but can't seem to find any solutions. It seems like folks either have the > problem or they don't. > > We recently migrated from a RedHat Linux server to an OpenBSD 3.7 server (both > using dovecot). Imap was working flawlessly on the RedHat box but now gives > numerous index errors. I then upgraded to dovecot-1.0-test66 compiled from > ports - still no luck. Here's an example of the errors: > > Jun 27 12:02:23 mail dovecot: IMAP(epate): Corrupted transaction log file > /home/epate/mail/.imap/INBOX/dovecot.index.log: Keyword record UIDs are broken > Jun 27 12:02:24 mail dovecot: IMAP(epate): Lost transaction log file > /home/epate/mail/.imap/INBOX/dovecot.index.log seq 7 > > I found references to "disabling indexing" but they don't say how. Would this > be a reasonable temporary solution? Any other suggestions? > > Thanks for your help, > > Emmett Pate > > >
On 27.6.2005, at 19:30, Emmett Pate wrote:> We recently migrated from a RedHat Linux server to an OpenBSD 3.7 > server (both > using dovecot). Imap was working flawlessly on the RedHat box but now > gives > numerous index errors. I then upgraded to dovecot-1.0-test66 compiled > from > ports - still no luck. Here's an example of the errors:0.99.x is pretty broken with OpenBSD. 1.0-test66 is also pretty old, you should try 1.0-test74 instead.> Jun 27 12:02:23 mail dovecot: IMAP(epate): Corrupted transaction log > file > /home/epate/mail/.imap/INBOX/dovecot.index.log: Keyword record UIDs > are brokenThis has been fixed since test66.> I found references to "disabling indexing" but they don't say how. > Would this > be a reasonable temporary solution? Any other suggestions?Often those index problems fix themselves and depending on what the problem is they may not even be visible to user. Disabling indexes works by appending :INDEX=MEMORY to default_mail_env, but I'm not sure if it's working in test66 (it does work with 0.99.x anyway). -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20050628/a5f32827/attachment-0001.bin>
Timo Sirainen wrote:> On 27.6.2005, at 19:30, Emmett Pate wrote: > >> We recently migrated from a RedHat Linux server to an OpenBSD 3.7 >> server (both >> using dovecot). Imap was working flawlessly on the RedHat box but now >> gives >> numerous index errors. I then upgraded to dovecot-1.0-test66 compiled >> from >> ports - still no luck. Here's an example of the errors: > > > 0.99.x is pretty broken with OpenBSD. 1.0-test66 is also pretty old, you > should try 1.0-test74 instead. > >> Jun 27 12:02:23 mail dovecot: IMAP(epate): Corrupted transaction log file >> /home/epate/mail/.imap/INBOX/dovecot.index.log: Keyword record UIDs >> are broken > > > This has been fixed since test66. > >> I found references to "disabling indexing" but they don't say how. >> Would this >> be a reasonable temporary solution? Any other suggestions? > > > Often those index problems fix themselves and depending on what the > problem is they may not even be visible to user. > > Disabling indexes works by appending :INDEX=MEMORY to default_mail_env, > but I'm not sure if it's working in test66 (it does work with 0.99.x > anyway).Thanks. I upgraded to -test74 (from source) and it's a big improvement. Using Thunderbird 1.0.2 and imap, I occasionally see this when deleting a message: Jun 28 12:22:04 mail dovecot: IMAP(epate): file mbox-sync-update.c: line 437 (mbox_sync_update_header_from): assertion failed: (ctx->mail.uid =0 || ctx->mail.uid == mail->uid) It usually takes a couple of tries to get the message to delete. I also see it when telling TB to mark the message as "Junk" or "Not Junk". Thanks for your help, Emmett Pate