Dovecot issue – dovecot.index file broken ?

Dovecot issue – dovecot.index file corrupted?

Any email user not able to access via his webmail? Does it show
logins failed, even if you are cent percent sure logins are correct?

Check /var/log/maillog.

# tailf /var/log/maillog

If you find anything like dis,

=============

Nov 12 20:59:02 host dovecot: imap(zzzz@yyyy.com): Error: Transaction log file /home/xxxx/mail/yyyy.com/zzzz/dovecot.index.log seq 302:

Nov 12 20:59:02 host dovecot: imap(zzzz@yyyy.com): Error: broken sync positions in index file /home/xxxx/mail/yyyy.com/zzzz/dovecot.index

Nov 12 20:59:02 host dovecot: imap(zzzz@yyyy.com): Warning: fscking index file /home/xxxx/mail/yyyy.com/zzzz/dovecot.index

Nov 12 20:59:02 host dovecot: imap(zzzz@yyyy.com) Error: Fixed index file /home/xxxx/mail/yyyy.com/zzzz/dovecot.index log_file_tail_offset 1184 -> 988

Nov 12 20:59:02 host dovecot: imap(zzzz@yyyy.com): Panic: file mail-transaction-log.c: line 350 (mail_transaction_log_set_mailbox_sync_pos): assertion failed: (file_offset >= log->head->saved_tail_offset)

=============

As indicated in the logs, there seems to be an issue with the dovecot index file for the user ‘zzzz’. The basic idea behind Dovecot’s index files is that it makes reading the mailboxes a lot faster.

This happens to be a long term issue with dovecot.

The solution to fix this issue is to delete dovecot.index file.

 

  • IronHeart

    What if it is getting repeated daily? I am a server admin and I am seeing the same issue daily for same email ids everytime. Customers are not happy at all…

    • http://letushare.com/ Joel T Abraham

      Well, in usual cases it does not repeat daily. It may occur to all the email id’s. Do you have any
      custom mail filters set on the accounts? also what is the locking method used for index files ?
      ( grep lock_method /etc/dovecot/dovecot.conf )

    • joelta

      Well, in usual cases it does not repeat daily. It may occur to all the email id’s. Do you have any
      custom mail filters set on the accounts? also what is the locking method used for index files ?
      ( grep lock_method /etc/dovecot/dovecot.conf )

      • IronHeart

        no custom filters setup. Dovecot version 2.2.9 and cPanel version: 11.40.1.9

        locking method is the default one (fcntl).

        • joelta

          Are you facing this same error ” Error: Transaction log file /home/xxxx/mail/yyyy.com/zzzz/dovecot.index.lo… seq xxx: log_file_tail_offset update shrank it (xxx vs xxx sync_offset=xxx ) ” ? there are other reasons too which might corrupt dovecot.index.log file which in-turn corrupts dovecot.index.

          If its the same issue and you have no custom filters set and uses the default locking method, then the only option is deleting the index file.

          -> What Timo ( creator of dovecot ) has to say on this :

          http://dovecot.2317879.n4.nabble.com/Indexes-recovery-failed-td17423.html

  • joelta

    Are you facing this same error ” Error: Transaction log file /home/xxxx/mail/yyyy.com/zzzz/dovecot.index.log seq xxx: log_file_tail_offset update shrank it (xxx vs xxx sync_offset=xxx ) ” ? there are other reasons too which might corrupt dovecot.index.log file which in-turn corrupts dovecot.index.

    If its the same issue and you have no custom filters set and uses the default locking method, then the only option is deleting the index file.

    -> What Timo ( creator of dovecot ) has to say on this :

    http://dovecot.2317879.n4.nabble.com/Indexes-recovery-failed-td17423.html

  • http://www.eroko.com Jen K

    hi. Thanks for the solution.. it works for me!

    • joelta

      🙂 Glad to hear that