[Dovecot] child 9436 (pop3) killed with signal 11
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi!
Suddenly since this afternoon the following happens:
Sep 14 18:16:55 UnseenUniversity pop3-login: Login: gunter [127.0.0.1] Sep 14 18:16:55 UnseenUniversity pop3(gunter): Corrupted index data file / home/gunter/Mail/.imap/INBOX/.imap.index.data: Field 1 size points outside file (205408 / 205376) for record 4662 Sep 14 18:16:55 UnseenUniversity pop3(gunter): Corrupted index data file / home/gunter/Mail/.imap/INBOX/.imap.index.data: Missing location field for record 4662 Sep 14 18:16:55 UnseenUniversity dovecot: child 9436 (pop3) killed with signal 11
I thought dovecot would delete damaged index files but I get this always when checking mail for the first time, cheking mail for the second time tells me:
Sep 14 18:18:43 UnseenUniversity pop3-login: Login: gunter [127.0.0.1] Sep 14 18:18:43 UnseenUniversity pop3(gunter): Corrupted binary tree file / home/gunter/Mail/.imap/INBOX/.imap.index.tree: Invalid used_file_size in header (0)
but actually fetches the mail after that. So what can/should I do? Simply delete the offending index file?
The dovecot version I'm using here is Debian's ii dovecot-pop3d 0.99.10-7 A secure POP3 server that supports mbox and and only it's pop3 part.
Greetings,
Gunter
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+PGP-verschlüsselte Mails bevorzugt! +
- I don't sign parts of the body, even if they're still attached.
-- From Terry's Rules of Book Signing (Terry Pratchett, alt.fan.pratchett) +-+-+-+-+-+-+-+-+-+-+-+-+ http://www.lspace.org +-+-+-+-+-+-+-+-+-+-+-+-+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/ZKEX0ORHvREo8l8RAnKoAJoDpKu3OprNQ0W7ZWXpj5/RcYmZFgCfWU2c s5uLQS9yQpe7LQlVDRbnlvk= =ngZu -----END PGP SIGNATURE-----
On Sunday, Sep 14, 2003, at 20:10 Europe/Helsinki, Gunter Ohrner wrote:
I thought dovecot would delete damaged index files
It should rebuild them automatically. I guess there are some situations when it fails to do that.
but I get this always when checking mail for the first time, cheking mail for the second time tells me:
Sep 14 18:18:43 UnseenUniversity pop3-login: Login: gunter [127.0.0.1] Sep 14 18:18:43 UnseenUniversity pop3(gunter): Corrupted binary tree file / home/gunter/Mail/.imap/INBOX/.imap.index.tree: Invalid used_file_size in header (0)
but actually fetches the mail after that. So what can/should I do? Simply delete the offending index file?
Yes, see if it helps.
participants (2)
-
Gunter Ohrner
-
Timo Sirainen