When something "bad" happens to the indexes, my e-mail client (Thunderbird) reports an "unable to succeed" error on opening a mailbox. Leaving that mailbox and coming back works fine. Is this expected behaviour?
-- Daniel
on 12/31/2007 10:54 AM Daniel L. Miller spake the following:
When something "bad" happens to the indexes, my e-mail client (Thunderbird) reports an "unable to succeed" error on opening a mailbox. Leaving that mailbox and coming back works fine. Is this expected behaviour?
You need to at least include which version of dovecot you are using, as there are some very old versions in use on some linux distros. It could be thunderbird timing out as the indexes get rebuilt.
-- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!
Scott Silva wrote:
on 12/31/2007 10:54 AM Daniel L. Miller spake the following:
When something "bad" happens to the indexes, my e-mail client (Thunderbird) reports an "unable to succeed" error on opening a mailbox. Leaving that mailbox and coming back works fine. Is this expected behaviour?
You need to at least include which version of dovecot you are using, as there are some very old versions in use on some linux distros. It could be thunderbird timing out as the indexes get rebuilt.
Ubuntu, Dovecot 1.0.5
-- Daniel
On Mon, 2007-12-31 at 10:54 -0800, Daniel L. Miller wrote:
When something "bad" happens to the indexes, my e-mail client (Thunderbird) reports an "unable to succeed" error on opening a mailbox. Leaving that mailbox and coming back works fine. Is this expected behaviour?
It's expected, but it's not expected that anything bad happens to your indexes normally. What do the logs show as the reason?
Timo Sirainen wrote:
On Mon, 2007-12-31 at 10:54 -0800, Daniel L. Miller wrote:
When something "bad" happens to the indexes, my e-mail client (Thunderbird) reports an "unable to succeed" error on opening a mailbox. Leaving that mailbox and coming back works fine. Is this expected behaviour?
It's expected, but it's not expected that anything bad happens to your indexes normally. What do the logs show as the reason?
I see a variety, but a sample:
Dec 31 11:09:26 bubba dovecot: IMAP(mgillespie@amfes.com): Corrupted transaction log file /var/mail/amfes.com/mgillespie/.Trash/dovecot.index.log: start_offset (20200) > file size (20184) Dec 31 11:09:30 bubba dovecot: IMAP(mgillespie@amfes.com): Transaction log file /var/mail/amfes.com/mgillespie/.Trash/dovecot.index.log: marked corrupted Dec 31 11:09:34 bubba dovecot: IMAP(mgillespie@amfes.com): Unexpected transaction log desync with index /var/mail/amfes.com/mgillespie/.Trash/dovecot.index
-- Daniel
On Wed, 2008-01-02 at 09:55 -0800, Daniel L. Miller wrote:
Timo Sirainen wrote:
On Mon, 2007-12-31 at 10:54 -0800, Daniel L. Miller wrote:
When something "bad" happens to the indexes, my e-mail client (Thunderbird) reports an "unable to succeed" error on opening a mailbox. Leaving that mailbox and coming back works fine. Is this expected behaviour?
It's expected, but it's not expected that anything bad happens to your indexes normally. What do the logs show as the reason?
I see a variety, but a sample:
Dec 31 11:09:26 bubba dovecot: IMAP(mgillespie@amfes.com): Corrupted transaction log file /var/mail/amfes.com/mgillespie/.Trash/dovecot.index.log: start_offset (20200) > file size (20184)
What filesystem is this with? Looks like NFS caching issues.
Timo Sirainen wrote:
On Wed, 2008-01-02 at 09:55 -0800, Daniel L. Miller wrote:
Timo Sirainen wrote:
On Mon, 2007-12-31 at 10:54 -0800, Daniel L. Miller wrote:
When something "bad" happens to the indexes, my e-mail client (Thunderbird) reports an "unable to succeed" error on opening a mailbox. Leaving that mailbox and coming back works fine. Is this expected behaviour?
It's expected, but it's not expected that anything bad happens to your indexes normally. What do the logs show as the reason?
I see a variety, but a sample:
Dec 31 11:09:26 bubba dovecot: IMAP(mgillespie@amfes.com): Corrupted transaction log file /var/mail/amfes.com/mgillespie/.Trash/dovecot.index.log: start_offset (20200) > file size (20184)
What filesystem is this with? Looks like NFS caching issues.
XFS, on a RAID-10, local to the Dovecot server. No NFS used anywhere in the network - Samba used for filesharing.
-- Daniel
participants (3)
-
Daniel L. Miller
-
Scott Silva
-
Timo Sirainen