search for: sync_offset

I got the following panic on 1.2.3: Panic: file mail-transaction-log-append.c: line 88 (log_buffer_move_to_memory): assertion failed: (file->buffer_offset + file->buffer->used == file->sync_offset) It's probably related to the file system holding the indexes being full.

...driver: passwd This is happening during peak load; the error msgs I'm seeing look like: Nov 5 15:01:47 mercury mail:err|error dovecot: IMAP(olson): Corrupted transaction log file /var/dci ndx/olson/.imap/INBOX/dovecot.index.log seq 742: file_seq=742, min_file_offset (24) < hdr_size (40) (sync_offset=24) Nov 5 15:04:13 mercury mail:err|error dovecot: IMAP(herchenr): Corrupted transaction log file /var/ dcindx/herchenr/.imap/INBOX/dovecot.index.log seq 357: file_seq=357, min_file_offset (24) < hdr_size (40) (sync_offset=24) Nov 5 15:04:13 mercury mail:info dovecot: IMAP(herchenr): Disconne...

...--------- next part -------------- List of errors: "Trying to close mailbox with open transactions" "Corrupted transaction log file Unexpected garbage at EOF" "fscking index file" "Transaction log got desynced for index" "start_offset (3872) > current sync_offset" "Fixed index file" "log_file_head_offset 3872 -> 3680" "Corrupted transaction log file record size too small" "Transaction log file marked corrupted" "file mail-index-sync-update.c: line 599: unreached" "Duplicate file entry:" &qu...

(I will not make a joke about the streets of Carlyle) Jan 13 19:09:07 mail dovecot: lda(john at example.com): Panic: file mail-transaction-log-file.c: line 1148 (mail_transaction_log_file_get_highest_modseq_at): assertion failed: (offset <= file->sync_offset) Jan 13 19:09:08 mail kernel: pid 8435 (dovecot-lda), uid 89: exited on signal 6 (core dumped) Jan 13 19:14:16 mail dovecot: lda(john at example.com): Panic: file mail-transaction-log-file.c: line 1148 (mail_transaction_log_file_get_highest_modseq_at): assertion failed: (offset <= file->sync_...

...File is already open imap[5565]: (stadiumchair) Error: Transaction log file HOME/stadiumchair/.Drafts/dovecot.index.log: marked corrupted imap[5005]: (stadiumchair) Error: Corrupted transaction log file HOME/stadiumchair/.Drafts/dovecot.index.log seq 2: indexid changed 1418941056 -> 1500658549 (sync_offset=0) imap[20243]: (martha) Error: Transaction log HOME/martha/dovecot.index.log: duplicate transaction log sequence (539) imap[4665]: (emsspam) Error: Index file HOME/emsspam/dovecot.index: indexid changed: 1500658479 -> 1297175382 imap[4665]: (emsspam) Error: Corrupted transaction log file HOME/e...

...inters to debug. I'm running Dovecot 2.0.15 and have a client which keeps causing log-entries like: Nov 4 15:10:42 mail dovecot: imap (test at aaaone.net): Error: Corrupted transaction log file /mail/3340444/.TestMails/dovecot.index.log seq 2: indexid changed 1320419300 -> 1320419441 (sync_offset=0) Nov 4 15:10:42 mail dovecot: imap(test at aaaone.net): Error: Corrupted transaction log file /mail/3340444/.TestMails/dovecot.index.log seq 2: Invalid transaction log size (4476 vs 4360): /mail/3340444/. TestMails/dovecot.index.log (sync_offset=4476) Nov 4 15:10:42 mail dovecot: imap(test at...

...lready open > imap[5565]: (stadiumchair) Error: Transaction log file HOME/stadiumchair/.Drafts/dovecot.index.log: marked corrupted > imap[5005]: (stadiumchair) Error: Corrupted transaction log file HOME/stadiumchair/.Drafts/dovecot.index.log seq 2: indexid changed 1418941056 -> 1500658549 (sync_offset=0) > imap[20243]: (martha) Error: Transaction log HOME/martha/dovecot.index.log: duplicate transaction log sequence (539) > imap[4665]: (emsspam) Error: Index file HOME/emsspam/dovecot.index: indexid changed: 1500658479 -> 1297175382 > imap[4665]: (emsspam) Error: Corrupted transaction...

...lready open > imap[5565]: (stadiumchair) Error: Transaction log file HOME/stadiumchair/.Drafts/dovecot.index.log: marked corrupted > imap[5005]: (stadiumchair) Error: Corrupted transaction log file HOME/stadiumchair/.Drafts/dovecot.index.log seq 2: indexid changed 1418941056 -> 1500658549 (sync_offset=0) > imap[20243]: (martha) Error: Transaction log HOME/martha/dovecot.index.log: duplicate transaction log sequence (539) > imap[4665]: (emsspam) Error: Index file HOME/emsspam/dovecot.index: indexid changed: 1500658479 -> 1297175382 > imap[4665]: (emsspam) Error: Corrupted transaction...

...erent servers. I seem to suffer from never ending index file corruption: Apr 4 16:55:49 mailstore-b dovecot: IMAP(david at everybody-loves.craigon.co.uk): Corrupted transaction log file /mnt/mailstore/e/everybody-loves.craigon.co.uk/d/david/.fish/dovecot.ind ex.log: end_offset (284) > current sync_offset (104) Apr 4 16:55:49 mailstore-b dovecot: IMAP(david at everybody-loves.craigon.co.uk): broken sync positions in index file /mnt/mailstore/e/everybody-loves.craigon.co.uk/d/david/.fish/dovecot.ind ex Apr 4 16:55:49 mailstore-b dovecot: IMAP(david at everybody-loves.craigon.co.uk): fscking index f...

...Panic: file /home/durket/dovecot-1.2.11/src/lib-index/mail-transaction-log-view.c: line 290 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq || max_file_seq != view->head->hdr.file_seq || max_file_offset != (uoff_t)-1 || min_file_offset <= view->head->sync_offset) I realize that there are newer releases of Dovecot (that even may fix this bug) but what I need to know is if there's anything I can do (like having Dovecot recreate indexes or whatnot) that will recover the user's mail (short of having to reconstruct it from backups).

...this post): Panic: file dovecot-1.2.11/src/lib-index/mail-transaction-log-view.c: line 290 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq || max_file_seq != view->head->hdr.file_seq || max_file_offset != (uoff_t)-1 || min_file_offset <= view->head->sync_offset) Is there something I can do to work around this problem for the user, or is this something new and I need to follow the instructions at http://dovecot.org/bugreport.html to send in a bug report?

...s corrupted once at 10:00, user B was corrupted at 10:25" for example. Examples of the corruption are as follows: ########### Corrupted transaction log file ..../dovecot/.INBOX/dovecot.index.log seq 28: Invalid transaction log size (32692 vs 32800): ...../dovecot/.INBOX/dovecot.index.log (sync_offset=32692) Corrupted index cache file ...../dovecot/.Sent Messages/dovecot.index.cache: Corrupted physical size for uid=624: 0 != 53490263 Corrupted transaction log file ..../dovecot/.INBOX/dovecot.index.log seq 66: Unexpected garbage at EOF (sync_offset=21608) Corrupted transaction log file ......

...ike these in my log: Oct 25 01:07:50 box5 dovecot: lmtp(8886, suporte=100br.com at lmtp1.prv.f1.k8.com.br): Error: Corrupted transaction log file /var/lib/imap/user/a3/suporte=100br.com/stor age/dovecot.map.index.log seq 29: Transaction log corrupted unexpectedly at 21536: Invalid size 0 (type=0) (sync_offset=21908) Oct 25 01:07:50 box5 dovecot: lmtp(8886, suporte=100br.com at lmtp1.prv.f1.k8.com.br): Error: Index /var/lib/imap/user/a3/suporte=100br.com/storage/dovecot.map.index: Lost log for seq=29 offset=21796 Oct 25 01:07:55 box5 dovecot: lmtp(8885, suporte=100br.com at lmtp1.prv.f1.k8.com.br): Err...

...lling 2.2.1, with 2.2.2 I seemed to get even more of them so currently back on 2.2.1 Thanks John Jun 11 00:00:05 rosalia dovecot: imap(myemail at mydomain): Error: Corrupted transaction log file /var/vmail/mydomain/myemail at mydomain/dovecot.index.log seq 311: file size shrank (1184 < 1304) (sync_offset=1304) Jun 11 00:00:05 rosalia dovecot: imap(myemail at mydomain): Error: Index /var/vmail/mydomain/myemail at mydomain/dovecot.index: Lost log for seq=310 offset=32816 Jun 11 00:00:05 rosalia dovecot: imap(myemail at mydomain): Warning: fscking index file /var/vmail/mydomain/myemail at mydomain/dov...

...ssue presents itself as a user not being able to login via the webmail interface. The logfile will contain something similar to the following: Apr 3 08:37:51 app02 dovecot: IMAP(user): Corrupted transaction log file /mail_home3/j/ji/user/Maildir/dovecot.index.log: end_offset (23440) > current sync_offset (23368) Apr 3 08:37:51 app02 dovecot: IMAP(user): file mail-index-sync-update.c: line 40 (mail_index_sync_update_log_offset): assertion failed: (prev_offset >= map->hdr.log_file_int_offset || prev_seq > map->hdr.log_file_seq) Apr 3 08:37:51 app02 dovecot: IMAP(user): Raw backtrace: im...

...imap(john at example.com): Error: /usr/local/virtual/john at example.com/dovecot.index: modseq_hdr.log_offset too large dovecot: imap(john at example.com): Panic: file mail-transaction-log-file.c: line 1148 (mail_transaction_log_file_get_highest_modseq_at): assertion failed: (offset <= file->sync_offset) dovecot: imap(john at example.com): Fatal: master: service(imap): child 88284 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) and also: dovecot: lda(john at southgaylord.com): Error: /usr/local/virtual/john at southgaylord.com/dovecot.index: modseq_hdr.log...

Hello, I am running Dovecot 1.0.5 and seem to have lots of errors in my Dovecot logs. The worst errors are things like: Oct 30 16:11:42 delta2 dovecot: IMAP(x): Corrupted transaction log file /home/spamcop-net2/deputies/dovecot.index.log: end_offset (392) > current sync_offset (388) Oct 30 16:11:42 delta2 dovecot: IMAP(x): file mail-index-sync-update.c: line 841 (mail_index_sync_update_index): assertion failed: (view->hdr.messages_count == map->hdr.messages_count) Oct 30 16:11:42 delta2 dovecot: IMAP(x): Raw backtrace: imap [0x462a7e] -> imap [0x46234c] ->...

...m is while its re-builing the users think all of their mail is gone. May 3 09:35:52 mailmachine dovecot: IMAP(test at domain.com): Corrupted transaction log file usershomedir/Maildir/dovecot.index.log seq 3: Invalid transaction log size (32708 vs 32840): usershomedir/Maildir/dovecot.index.log (sync_offset=32708) We are using load balanced servers and data/index's are stored in their home dir's over nfs. All my config details and nfs options are below. We are currently balancing based on source address so most of the time users imap/pop processes should stick to one machine as much as pos...

...in their home. From day one, when people check their mail via imap, a lot of indexes corruption occured : dovecot: IMAP(<user>@domain.org): Corrupted transaction log file /home/<user>/Mail/Maildir/INBOX/dovecot.index.log seq 13: record size too small +(type=0x0, offset=5560, size=0) (sync_offset=5652) dovecot: IMAP(<user>@domain.org): fscking index file /home/<user>/Mail/Maildir/INBOX/dovecot.index dovecot: IMAP(<user>@domain.org): /home/<user>/Mail/Maildir/INBOX/dovecot.index log position went backwards (13,132 < 13,5560) dovecot: IMAP(<user>@domain.org):...

...od=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=29811, secured, session=<ZteFh6P2uAB/AAAB> Apr 9 17:22:00 andromeda dovecot: imap(myuser at mydomain.com): Error: Transaction log file /home/myuser/mail/mydomain.com/myuser/dovecot.index.log seq 4: log_file_tail_offset update shrank it (284 vs 420 sync_offset=268) Apr 9 17:22:00 andromeda dovecot: imap(myuser at mydomain.com): Error: broken sync positions in index file /home/myuser/mail/mydomain.com/myuser/dovecot.index Apr 9 17:22:00 andromeda dovecot: imap(myuser at mydomain.com): Warning: fscking index file /home/myuser/mail/mydomain.com/myuser/dov...