[Dovecot] Errmsgs b4 and after migration DC V1.0.15 to V1.1.8
Stewart Dean
sdean at bard.edu
Tue Jan 20 17:52:39 EET 2009
Last Wednesday at 12:21 I made this switch, which seemed to be
uneventful. In any case, no user has reported problems since the
migration. Not content to leave well enough alone, this morning I
scanned the syslog and maillog for dovecot related errors. What I found
was that:
Before the Migration===========================
I saw a lot of SSL errors that look like this:
> Jan 14 11:49:23 mercury mail:warn|warning dovecot: imap-login: SSL_read() syscall failed: Connection reset by peer [69.180.200.184]
> Jan 14 11:52:28 mercury mail:warn|warning dovecot: imap-login: SSL_read() syscall failed: Connection reset by peer [68.6.82.45]
Which l took to be breakin attempts of some sort, except that I haven't
seen any since the migration!
After the migration====================================
I see errors like this:
> Jan 14 12:21:45 mercury mail:err|error dovecot: IMAP(eg115): Corrupted index cache file /var/dcindx/eg115/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 1934
> Jan 14 12:21:46 mercury mail:err|error dovecot: IMAP(alexande): Corrupted index cache file /var/dcindx/alexande/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 132641
> Jan 14 12:21:46 mercury mail:err|error dovecot: IMAP(ls454): Corrupted index cache file /var/dcindx/ls454/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 47
> Jan 14 12:21:46 mercury mail:err|error dovecot: IMAP(tr489): Corrupted index cache file /var/dcindx/tr489/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 1
> Jan 14 12:21:54 mercury mail:err|error dovecot: IMAP(bh265): Corrupted index cache file /var/dcindx/bh265/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 2
> Jan 14 12:22:01 mercury mail:err|error dovecot: IMAP(crouch): Corrupted index cache file /var/dcindx/crouch/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 4863
>
It appears that this error appears the first time a folder is
referenced, then not again (I think but am not absolutely positive).
Did the indexing method/format change in some way that would cause this
(and Dovecot heals itself!) ? Is there any continuing problem inherent
in this that needs to be dealt with?
Thanks!
--
"Eppur si muove." (But Still it moves) Galileo, leaving the Inquisition,
after buckling under the threat of torture and excommunication and
recanting from his proof that the heavens do not revolve around the
earth --
Stewart Dean, Unix System Admin, Henderson Computer Center, Bard
College, Annandale, New York 12504 sdean at bard.edu voice: 845-758-7475,
fax: 845-758-7035
More information about the dovecot
mailing list