Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)

[Thomas Leuxner]

Am 04.06.2010 um 19:38 schrieb Timo Sirainen:
> Do you still happen to have the m.59.broken file? I'd like to look at
> it. The fixed files' contents are supposed to be preserved..

Unfortunately don't have it anymore, even on backups.

Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)

[Timo Sirainen]

On ti, 2010-03-09 at 19:07 +0100, Thomas Leuxner wrote:
> Am 09.03.2010 um 19:01 schrieb Timo Sirainen:
> 
> > Is it in the fixed m.59? The fixing/resyncing was supposed to preserve all 
> > mails.
> > 
> 
> Actually 'm.59' was not rebuilt but it continued with new containers. 
> Grepping for the content, it remained in the broken container only.

Do you still happen to have the m.59.broken file? I'd like to look at
it. The fixed files' contents are supposed to be preserved..

Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)

[Thomas Leuxner]

Am 09.03.2010 um 19:02 schrieb Timo Sirainen:
> 
> I guess this imap session was open while doveadm was running?
> 

You are right.

Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)

[Thomas Leuxner]

Am 09.03.2010 um 19:01 schrieb Timo Sirainen:

> Is it in the fixed m.59? The fixing/resyncing was supposed to preserve all 
> mails.
> 

Actually 'm.59' was not rebuilt but it continued with new containers. Grepping 
for the content, it remained in the broken container only.

Regards
Thomas

Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)

[Timo Sirainen]

On 9.3.2010, at 20.00, Thomas Leuxner wrote:

> Am 09.03.2010 um 18:54 schrieb Thomas Leuxner:
>> 
>> Could not resync it to the "Inbox" but the message is still in 'm.59.broken' 
>> and the source looks undamaged. Any easy way to restore? No biggie if it is 
>> lost, but just out of curiosity, once an *important* mail would be affected 
>> :)
>> 
>> Thomas
>> 
> 
> Oh and btw: The doveadm imap resync caused another dump:
> 
> Mar  9 18:49:14 spectre dovecot: imap(t...@leuxner.net): 
> /var/vmail/leuxner.net/tlx/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index 
> reset, view is now inconsistent

I guess this imap session was open while doveadm was running?

> Mar  9 18:49:14 spectre dovecot: imap(t...@leuxner.net): Panic: file 
> index-sync.c: line 40 (index_mailbox_set_recent_uid): assertion failed: 
> (seq_range_exists(&ibox->recent_flags, uid))

Yeah, this happens pretty easily when index is reset. Should try to fix it some 
day, but not a huge issue since by that time the client was already going to 
get disconnected anyway.

Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)

[Timo Sirainen]

On 9.3.2010, at 19.54, Thomas Leuxner wrote:

> Am 09.03.2010 um 17:00 schrieb Timo Sirainen:
>> Oh, and make sure it's not empty because your client already cached it
>> as empty message and doesn't realize it has changed on server.
>> 
> 
> Could not resync it to the "Inbox" but the message is still in 'm.59.broken' 
> and the source looks undamaged. Any easy way to restore? No biggie if it is 
> lost, but just out of curiosity, once an *important* mail would be affected :)

Is it in the fixed m.59? The fixing/resyncing was supposed to preserve all 
mails.

Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)

[Thomas Leuxner]

Am 09.03.2010 um 18:54 schrieb Thomas Leuxner:
> 
> Could not resync it to the "Inbox" but the message is still in 'm.59.broken' 
> and the source looks undamaged. Any easy way to restore? No biggie if it is 
> lost, but just out of curiosity, once an *important* mail would be affected :)
> 
> Thomas
> 

Oh and btw: The doveadm imap resync caused another dump:

Mar  9 18:49:14 spectre dovecot: imap(t...@leuxner.net): 
/var/vmail/leuxner.net/tlx/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index 
reset, view is now inconsistent
Mar  9 18:49:14 spectre dovecot: imap(t...@leuxner.net): Panic: file 
index-sync.c: line 40 (index_mailbox_set_recent_uid): assertion failed: 
(seq_range_exists(&ibox->recent_flags, uid))
Mar  9 18:49:14 spectre dovecot: imap(t...@leuxner.net): Disconnected: IMAP 
session state is inconsistent, please relogin. bytes=711/16119
Mar  9 18:49:14 spectre dovecot: imap(t...@leuxner.net): Raw backtrace: 
/usr/lib/dovecot/libdovecot.so.0 [0x7faec9ac62b2] -> 
/usr/lib/dovecot/libdovecot.so.0 [0x7faec9ac631a] -> 
/usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7faec9ac66c3] -> 
/usr/lib/dovecot/libdovecot-storage.so.0(index_mailbox_set_recent_seq+0) 
[0x7faec9d71030] -> 
/usr/lib/dovecot/libdovecot-storage.so.0(index_mailbox_set_recent_seq+0x3c) 
[0x7faec9d7106c] -> 
/usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync_begin+0x37b) 
[0x7faec9d9cdfb] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync+0x12) 
[0x7faec9d9d0e2] -> 
/usr/lib/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0x43) 
[0x7faec9d9d153] -> 
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) 
[0x7faec9d2e4e1] -> dovecot/imap [...@leuxner.net 84.58.106.99 
IDLE](imap_sync_init+0x68) [0x417db8] -> dovecot/imap [...@leuxner.net 
84.58.106.99 IDLE] [0x40ab5e] -> 
/usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x9b) [0x7faec9ad042b] 
-> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x6f) [0x7faec9ad0f8f] 
-> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x18) [0x7faec9ad0168] -> 
/usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7faec9ac0143] -> 
dovecot/imap [...@leuxner.net 84.58.106.99 IDLE](main+0x191) [0x418681] -> 
/lib/libc.so.6(__libc_start_main+0xe6) [0x7faec934d1a6] -> dovecot/imap 
[...@leuxner.net 84.58.106.99 IDLE] [0x4084e9]
Mar  9 18:49:14 spectre dovecot: master: service(imap): child 4451 killed with 
signal 6 (core dumped)

GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...Reading symbols 
from /usr/lib/debug/usr/lib/dovecot/libdovecot-storage.so.0.0.0...done.
done.
Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0
Reading symbols from /usr/lib/dovecot/libdovecot.so.0...Reading symbols from 
/usr/lib/debug/usr/lib/dovecot/libdovecot.so.0.0.0...done.
done.
Loaded symbols for /usr/lib/dovecot/libdovecot.so.0
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/librt.so.1...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib/libpthread.so.0...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /usr/lib/dovecot/modules/lib01_acl_plugin.so...Reading 
symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib01_acl_plugin.so...done.
done.
Loaded symbols for /usr/lib/dovecot/modules/lib01_acl_plugin.so
Reading symbols from 
/usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...Reading symbols from 
/usr/lib/debug/usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...done.
done.
Loaded symbols for /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so
Reading symbols from /usr/lib/dovecot/modules/lib10_quota_plugin.so...Reading 
symbols from 
/usr/lib/debug/usr/lib/dovecot/modules/lib10_quota_plugin.so...done.
done.
Loaded symbols for /usr/lib/dovecot/modules/lib10_quota_plugin.so
Reading symbols from 
/usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...Reading symbols from 
/usr/lib/debug/usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...done.
done.
Loaded symbols for /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Core was generated by `dovecot/imap'.
Program terminated with signal 6, Aborted.
[New process 4451]
#0  0x7faec9360ed5 in raise () from /lib/libc.so.6
(gdb) bt full
#0  0x7faec9360ed5 in raise () from /lib/libc.so.6
No symbol table info available.
#1  0x7faec9362

Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)

[Thomas Leuxner]

Am 09.03.2010 um 17:00 schrieb Timo Sirainen:
> Oh, and make sure it's not empty because your client already cached it
> as empty message and doesn't realize it has changed on server.
> 

Could not resync it to the "Inbox" but the message is still in 'm.59.broken' 
and the source looks undamaged. Any easy way to restore? No biggie if it is 
lost, but just out of curiosity, once an *important* mail would be affected :)

Thomas

Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)

[Timo Sirainen]

On Tue, 2010-03-09 at 17:59 +0200, Timo Sirainen wrote:
> On Tue, 2010-03-09 at 16:40 +0100, Thomas Leuxner wrote:
> > With the latest fix from Mercurial it does not crash anymore. The message 
> > shows empty and the container in question 'm.59.broken' stays in the 
> > 'storage' dir. Is this expected behavior and am I save to delete the broken 
> > container, or how would I clean up the corruption?
> 
> See if "doveadm force-resync username inbox" helps? If not, see if the
> message is still in m.59.broken file. If it's not there either, it
> probably never got actually saved.

Oh, and make sure it's not empty because your client already cached it
as empty message and doesn't realize it has changed on server.



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)

[Timo Sirainen]

On Tue, 2010-03-09 at 16:40 +0100, Thomas Leuxner wrote:
> With the latest fix from Mercurial it does not crash anymore. The message 
> shows empty and the container in question 'm.59.broken' stays in the 
> 'storage' dir. Is this expected behavior and am I save to delete the broken 
> container, or how would I clean up the corruption?

See if "doveadm force-resync username inbox" helps? If not, see if the
message is still in m.59.broken file. If it's not there either, it
probably never got actually saved.



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)

[Thomas Leuxner]

With the latest fix from Mercurial it does not crash anymore. The message shows 
empty and the container in question 'm.59.broken' stays in the 'storage' dir. 
Is this expected behavior and am I save to delete the broken container, or how 
would I clean up the corruption?

Regards
Thomas