Adam McDougall
2007-May-25 15:28 UTC
[Dovecot] Quick question on multiple access to dovecot indexes
I have up to 4 servers that will run dovecot behind a load balancer, which means the same user might be accessing the same mailbox from multiple servers, and it seems like dovecot doesn't like multiple access to the dovecot indexes for the one user since I currently have them stored in a nfs home directory. Is this a bad thing? Must I keep a seperate index location per server? Just today I started running dovecot on more than one server like this and started seeing things in the logs like: May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Corrupted transaction log file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index.log: end_offset (1332) > current sync_offset (1244) May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): broken sync positions in index file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): fscking index file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Fixed index file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index: log file sync pos 2,1332 -> 2, 1244 May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Unexpected transaction log desync with index /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Disconnected: Mailbox is in inconsistent state, please relogin. May 25 11:19:17 dauterive dovecot: IMAP(mcdouga9): file mail-index.c: line 983 (mail_index_sync_from_transactions): assertion failed: (hdr.messages_count == (*map)->hdr.messages_count) May 25 11:19:17 dauterive dovecot: child 16386 (imap) killed with signal 6 ... May 25 11:19:53 dauterive in.imapproxyd[17211]: LOGIN: '"mcdouga9"' (127.0.0.1:53650) on existing sd [9] May 25 11:19:53 dauterive dovecot: IMAP(mcdouga9): Transaction log file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index.log: marked corrupted May 25 11:19:53 dauterive dovecot: IMAP(mcdouga9): Transaction log file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index.log.2: marked corrupted
Timo Sirainen
2007-May-26 15:23 UTC
[Dovecot] Quick question on multiple access to dovecot indexes
On Fri, 2007-05-25 at 11:28 -0400, Adam McDougall wrote:> I have up to 4 servers that will run dovecot behind a load balancer, which means > the same user might be accessing the same mailbox from multiple servers, and it > seems like dovecot doesn't like multiple access to the dovecot indexes for the > one user since I currently have them stored in a nfs home directory. Is this > a bad thing? Must I keep a seperate index location per server?So you're using NFS? Have you read http://wiki.dovecot.org/NFS? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20070526/8890d5d7/attachment-0002.bin>
Adam McDougall
2007-May-26 15:54 UTC
[Dovecot] Quick question on multiple access to dovecot indexes
On Sat, May 26, 2007 at 06:23:45PM +0300, Timo Sirainen wrote: On Fri, 2007-05-25 at 11:28 -0400, Adam McDougall wrote: > I have up to 4 servers that will run dovecot behind a load balancer, which means > the same user might be accessing the same mailbox from multiple servers, and it > seems like dovecot doesn't like multiple access to the dovecot indexes for the > one user since I currently have them stored in a nfs home directory. Is this > a bad thing? Must I keep a seperate index location per server? So you're using NFS? Have you read http://wiki.dovecot.org/NFS? Oops, sorry. I will take that information into account.
Apparently Analagous Threads
- unlink_directory(....Trash.NewFolder) failed: Directory not empty
- Various uidlist and index errors with 1.1 on NFS
- assertion failed: (mailbox_list_is_valid_existing_name(_list, name))
- crash with fts_squat on an identified email
- do 1.1b4 assertion failed: (mailbox_list_is_valid_existing_name