[Dovecot] log contents questions?
I switched from using Pegasus and POP3 to Thunderbird and IMAP for my email. Now I get a lot of "Corrupted index cache file" errors in my log. Dovecot is running under Fedora 8 and is version 1.0.13-6.fc8. The Thunderbird is version 2.0.0.14 running under Windows XP. My wife's Blackberry is also using IMAP and not reporting any errors.
Any ideas what the problem is or how to fix it?
Thanks,
knute...
--------------------- Dovecot Begin ------------------------
Dovecot disconnects: Inactivity: 2 Time(s) Logged out: 2606 Time(s) in IDLE: 27 Time(s)
**Unmatched Entries** dovecot: IMAP(knute): Connection closed: 5 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/CR-FFL/dovecot.index.cache: invalid record size: 3 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/INBOX/dovecot.index.cache: invalid record size: 2 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/frazmtn.com/dovecot.index.cache: invalid record size: 4 Time(s) dovecot: IMAP(linux): Connection closed: 4 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Dovecot/dovecot.index.cache: invalid record size: 2 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora List/dovecot.index.cache: invalid record size: 4 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora Selinux List/dovecot.index.cache: invalid record size: 1 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora Test List/dovecot.index.cache: invalid record size: 2 Time(s)
---------------------- Dovecot End -------------------------
--
Knute Johnson linux@www.knutejohnson.com
Charles Marcus wrote:
On 5/22/2008, Knute Johnson (linux@www.knutejohnson.com) wrote:
Any ideas what the problem is or how to fix it?
Output of dovecot -n?
Any additional config parameters? No one here is a mind reader... ;)
Well neither am I. Why didn't you tell me you wanted that before I posted.
Thanks,
[root@www knute]# dovecot -n # 1.0.13: /etc/dovecot.conf protocols: imaps pop3s disable_plaintext_auth: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: passdb: driver: pam userdb: driver: passwd [root@www knute]#
--
Knute Johnson linux@www.knutejohnson.com
On 5/23/2008, Knute Johnson (linux@www.knutejohnson.com) wrote:
Any ideas what the problem is or how to fix it?
Output of dovecot -n?
Any additional config parameters? No one here is a mind reader... ;)
Well neither am I. Why didn't you tell me you wanted that before I posted.
No offense intended, but...
http://www.dovecot.org/mailinglists.html
It [should be] a given that basic configuration information will most likely be necessary to help you find a problem... no? At least, thats the way its always been on every support list I've ever been on...
Anyway, a quick google finds some hits on this error, so if you had already googled the error (and if you hadn't - shouldn't you have?)...
It appears the consensus is, these errors are harmless and don't impact performance, Timo cannot reporoduce them any longer (since post 1.0 release), and he thnks they are fixed in 1.1 version (release imminent).
One thing I saw suggested was to be sure that no client is accessing the affected maildirs, and delete the indexes manually.
There is also a suggeston that there may be an issue with NFS/Redhat and certain kernel versions...
Are you using NFS? What version of the Redhat kernel?
--
Best regards,
Charles
Charles Marcus wrote:
On 5/23/2008, Knute Johnson (linux@www.knutejohnson.com) wrote:
Any ideas what the problem is or how to fix it?
Output of dovecot -n?
Any additional config parameters? No one here is a mind reader... ;)
Well neither am I. Why didn't you tell me you wanted that before I posted.
No offense intended, but...
I probably read that when I signed up for the list a couple of years ago, but I forgot.
It [should be] a given that basic configuration information will most likely be necessary to help you find a problem... no? At least, thats the way its always been on every support list I've ever been on...
You're right!
Anyway, a quick google finds some hits on this error, so if you had already googled the error (and if you hadn't - shouldn't you have?)...
I didn't have as much luck as you, so thank you for finding the info.
It appears the consensus is, these errors are harmless and don't impact performance, Timo cannot reporoduce them any longer (since post 1.0 release), and he thnks they are fixed in 1.1 version (release imminent).
One thing I saw suggested was to be sure that no client is accessing the affected maildirs, and delete the indexes manually.
I'll give that a try and see what the log says tomorrow.
There is also a suggeston that there may be an issue with NFS/Redhat and certain kernel versions...
Are you using NFS? What version of the Redhat kernel?
No NFS. 2.6.24.7-92.fc8.
Thanks,
--
Knute Johnson linux@www.knutejohnson.com
participants (2)
-
Charles Marcus
-
Knute Johnson