[Dovecot] Lost transaction log file in alpha2

[James Berry]

On Sep 14, 2005, at 11:04 AM, James Berry wrote:

> I had run alpha1 pretty uneventfully for several weeks. I upgraded  
> to alpha2 a couple of days ago and have since suffered two  
> incidents of "Lost transaction log", resulting in the client being  
> unable to access the mailbox until I "rm dovecot.index.log*"

This just happened to me again. Here's the where it first started  
showing up in the log:

Sep 16 14:27:13 caddy dovecot: imap(jberry): Maildir /Users/jberry/ 
Maildir sync: UID < next_uid (36243 < 36244, file =  
1126905722.Ve000002I164d7f.caddy.edworks.com:2,)
Sep 16 14:27:13 caddy dovecot: imap-login: Login: user=<jberry>,  
method=PLAIN, rip=24.20.133.214, lip=207.149.241.23, TLS
Sep 16 14:27:13 caddy dovecot: imap(jberry): Lost transaction log  
file /Users/jberry/Maildir/dovecot.index.log seq 1
Sep 16 14:27:17 caddy dovecot: imap(jberry): Lost transaction log  
file /Users/jberry/Maildir/dovecot.index.log seq 1
Sep 16 14:27:18 caddy dovecot: imap(jberry): Lost transaction log  
file /Users/jberry/Maildir/dovecot.index.log seq 1
Sep 16 14:27:19 caddy dovecot: imap(jberry): Lost transaction log  
file /Users/jberry/Maildir/dovecot.index.log seq 1
Sep 16 14:27:20 caddy dovecot: imap(jberry): Lost transaction log  
file /Users/jberry/Maildir/dovecot.index.log seq 1
Sep 16 14:27:21 caddy dovecot: imap(jberry): Lost transaction log  
file /Users/jberry/Maildir/dovecot.index.log seq 1

Once it gets in this state, the only way to recover from the failure  
seems to be to delete the log files. The problem does not heal itself.

-jdb


>
> Sep 14 10:48:35 caddy dovecot: imap(jberry): Lost transaction log  
> file /Users/jberry/Maildir/dovecot.index.log seq 1
>
> I should point out that this is a server with a single imap user  
> (myself) and that I know only one imap client was trying to access  
> the server at that point in time (though the client sw Mail.app may  
> have had multiple connections to the server).
>
> Any suggestions/ideas/thoughts on whether something might have  
> changed in alpha2 to start causing this?
>
> James.
>
>