Interesting. We are expiring the same problem here. But our user is currently traveling in the world and uses our roundcube to access its emails:
The panic is preceeded by Error: Next message unexpectedly corrupted in mbox file PATH
Panic: file mbox-sync.c: line 152 (mbox_sync_read_next_mail): assertion failed: (sync_ctx->input->v_offset != mail_ctx->mail.from_offset || sync_ctx->input->eof)
At #7 in the enclosed backtrace the actual values are sync_ctx->input->v_offset = 564 mail_ctx->mail.from_offset = 564 sync_ctx->input->eof = 0
I can not attach a gdb output because until yet i could not catch a core dump.
Here the last lines from the logfile:
Oct 29 07:46:34 SERVER dovecot: [ID 583609 mail.debug] imap(USERNAME): Debug: Namespace : type=private, prefix=Mail/, sep=/, inbox=no, hidden=yes, list=no, subscriptions=yes location=mbox:~/Mail/:INBOX=/var/mail/USERNAME:INDEX=/usr/SERVER/vault2/dovecot/indexes/USERNAME
Oct 29 07:46:34 SERVER dovecot: [ID 583609 mail.debug] imap(USERNAME): Debug: fs: root=/home/USERNAME/Mail, index=/usr/SERVER/vault2/dovecot/indexes/USERNAME, indexpvt=, control=, inbox=/var/mail/USERNAME, alt=
Oct 29 07:46:34 SERVER dovecot: [ID 583609 mail.info] imap(USERNAME): Disconnected: Logged out in=374 out=60850
Oct 29 07:46:35 SERVER dovecot: [ID 583609 mail.error] imap(USERNAME): Error: Next message unexpectedly corrupted in mbox file /home/USERNAME/Mail/MBOXFILE at 38055772
Oct 29 07:46:35 SERVER dovecot: [ID 583609 mail.crit] imap(USERNAME): Panic: file mbox-sync.c: line 152 (mbox_sync_read_next_mail): assertion failed: (sync_ctx->input->v_offset != mail_ctx->mail.from_offset || sync_ctx->input->eof)
Oct 29 07:46:35 SERVER dovecot: [ID 583609 mail.error] imap(USERNAME): Error: Raw backtrace: 0xffffffff7ed89f64 -> 0xffffffff7ed88f10 -> 0xffffffff7ef77a14 -> 0xffffffff7ef78a1c -> 0xffffffff7ef78e98 -> 0xffffffff7ef962d0 -> 0xffffffff7ef96418 -> 0xffffffff7efc2380 -> 0xffffffff7ef9777c -> 0x100021554 -> 0x100013e8c -> 0x100019044 -> 0x100017b18 -> 0x100017ad8 -> 0x100017f3c -> 0x100018188 -> 0xffffffff7ed9c8a4 -> 0xffffffff7ed9d5a0 -> 0xffffffff7ed9c93c -> 0xffffffff7ed9ca0c -> 0xffffffff7ed3c314 -> 0x100024908 -> 0x10000a74c
Oct 29 07:46:35 SERVER dovecot: [ID 583609 mail.crit] imap(USERNAME): Fatal: master: service(imap): child 19457 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes })
I have set the drop_priv_before_exec to yes, i'm just waiting for the user to connect again ;-)
Our System is a Solaris 10 and we are also using mbox for more or less the same reason as hmk.
As soon as i can catch a coredump i will send a gdb output.
Since all other users do not have such a problem i'm wondering what the reason for this could be? corrupt mbox file?
Best Regards Matthias
-- Matthias Egger ETH Zurich Department of Information Technology maegger@ee.ethz.ch and Electrical Engineering IT Support Group (ISG.EE), ETL/F/24.1 Phone +41 (0)44 632 03 90 Physikstrasse 3, CH-8092 Zurich Fax +41 (0)44 632 11 95