[Dovecot] 1.1.3 panics
Hi,
Installed Dovecot 1.1.3 today and started receiving panic errors on a few of our users:
dovecot: [ID 107833 mail.crit] Panic: IMAP(xx): file mail-index-transaction-view.c: line 204: unreached
When I upgraded, I deleted all of our users index files so it started with a clean slate.
We are running mbox format over NFS with fsquota plugin on Solaris 8. Here is output of dovecot -n:
base_dir: /var/run/dovecot/ protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login login_user: daemon login_log_format_elements: user=%u ip=%r mail_max_userip_connections: 5 first_valid_uid: 100 last_valid_uid: 128000 mail_privileged_group: mail mail_location: mbox:~/Mail:INBOX=/var/mail/%u:INDEX=/var/indexes/local/%u mail_nfs_storage: yes mbox_write_locks: fcntl mbox_lock_timeout: 180 mbox_lazy_writes: no mail_plugins: quota imap_quota namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: Mail/ hidden: yes subscriptions: yes auth default: mechanisms: plain login failure_delay: 5 debug: yes debug_passwords: yes passdb: driver: shadow userdb: driver: passwd plugin: quota: fs
-- Dean Brooks dean@iglou.com
On Sep 3, 2008, at 5:47 PM, Dean Brooks wrote:
dovecot: [ID 107833 mail.crit] Panic: IMAP(xx): file mail-index- transaction-view.c: line 204: unreached
Could you get gdb backtrace? http://dovecot.org/bugreport.html
On Wed, Sep 03, 2008 at 05:50:43PM +0300, Timo Sirainen wrote:
On Sep 3, 2008, at 5:47 PM, Dean Brooks wrote:
dovecot: [ID 107833 mail.crit] Panic: IMAP(xx): file mail-index- transaction-view.c: line 204: unreached
Could you get gdb backtrace? http://dovecot.org/bugreport.html
I'll try to get a backtrace tonight or tommorow. We're getting about 20 of those errors an hour.
Also, we're getting a handful of these panics which I've never seen before either:
dovecot: [ID 107833 mail.crit] Panic: IMAP(xx): file mbox-lock.c: line 675 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK)
-- Dean Brooks dean@iglou.com
On Wed, 2008-09-03 at 15:47 -0400, Dean Brooks wrote:
On Wed, Sep 03, 2008 at 05:50:43PM +0300, Timo Sirainen wrote:
On Sep 3, 2008, at 5:47 PM, Dean Brooks wrote:
dovecot: [ID 107833 mail.crit] Panic: IMAP(xx): file mail-index- transaction-view.c: line 204: unreached
Could you get gdb backtrace? http://dovecot.org/bugreport.html
I'll try to get a backtrace tonight or tommorow. We're getting about 20 of those errors an hour.
This is fixed now: http://hg.dovecot.org/dovecot-1.1/rev/984f8a9d5a71
Also, we're getting a handful of these panics which I've never seen before either:
dovecot: [ID 107833 mail.crit] Panic: IMAP(xx): file mbox-lock.c: line 675 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK)
But backtrace from this would be nice.
Dean Brooks wrote:
Hi,
Installed Dovecot 1.1.3 today and started receiving panic errors on a few of our users:
dovecot: [ID 107833 mail.crit] Panic: IMAP(xx): file mail-index-transaction-view.c: line 204: unreached
Hi,
I am also seeing this problem. I haven't managed to generate a core dump yet, however I did get more logging in mail.err:
Sep 4 13:25:36 songbird dovecot: IMAP(user): Raw backtrace: imap [0x486942] -> imap [0x4869b3] -> imap [0x486026] -> imap [0x46775c] -> imap(mail_index_lookup_ext_full+0x17) [0x469fc7] -> imap(mail_index_lookup_ext+0x17) [0x469fe7] -> imap(mbox_file_lookup_offset+0x33) [0x4382f3] -> imap(mbox_file_seek+0x2e) [0x43837e] -> imap [0x439c98] -> imap [0x43a022] -> imap [0x43a149] -> /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so(quota_try_alloc+0x29) [0x7f706e92b6b9] -> /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so [0x7f706e92ea9b] -> imap [0x4186fd] -> imap [0x418e9e] -> imap(io_loop_handler_run+0xf8) [0x48d6d8] -> imap(io_loop_run+0x1d) [0x48c7fd] -> imap(main+0x3c2) [0x425b92] -> /lib/libc.so.6(__libc_start_main+0xf4) [0x7f706eb511c4] -> imap [0x418449] Sep 4 13:25:36 songbird dovecot: child 5531 (imap) killed with signal 6
We were also using the quota plugin to access mailboxes via NFS. We have since disabled this plugin, and are no-longer observing this fault.
(We have found a way to reliably trigger this particular fault. Using Alpine, if a user deletes their postponed-messages IMAP folder, and then attempts to postpone a message, the IMAP process will crash shortly after the postponed-messages folder is recreated.)
Cheers, David
David McBride dwm@tastycake.net dwm@doc.ic.ac.uk
OSep 4 13:25:36 songbird dovecot: IMAP(user): Raw backtrace: imap
[0x486942] -> imap [0x4869b3] -> imap [0x486026] -> imap [0x46775c] -> imap(mail_index_lookup_ext_full+0x17) [0x469fc7] -> imap(mail_index_lookup_ext+0x17) [0x469fe7] -> imap(mbox_file_lookup_offset+0x33) [0x4382f3] -> imap(mbox_file_seek+0x2e) [0x43837e] -> imap [0x439c98] -> imap [0x43a022] -> imap [0x43a149] -> /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so(quota_try_alloc+0x29) [0x7f706e92b6b9] -> /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so [0x7f706e92ea9b] -> imap [0x4186fd] -> imap [0x418e9e] -> imap(io_loop_handler_run+0xf8) [0x48d6d8] -> imap(io_loop_run+0x1d) [0x48c7fd] -> imap(main+0x3c2) [0x425b92] -> /lib/libc.so.6(__libc_start_main+0xf4) [0x7f706eb511c4] -> imap [0x418449] Sep 4 13:25:36 songbird dovecot: child 5531 (imap) killed with signal 6
We were also using the quota plugin to access mailboxes via NFS. We have since disabled this plugin, and are no-longer observing this fault.
What quota backend were you using? Could you post your entire dovecot -n output?
(We have found a way to reliably trigger this particular fault. Using Alpine, if a user deletes their postponed-messages IMAP folder, and then attempts to postpone a message, the IMAP process will crash shortly after the postponed-messages folder is recreated.)
So if
- mailbox is created
- a new mail is APPENDed there
it crashes? The deletion part is probably irrelevant to the crash?
Timo Sirainen wrote:
What quota backend were you using? Could you post your entire dovecot -n output?
We were using the "fs" quota backend.
I'll be able to post our dovecot -n configuration output when I get back to somewhere with proper bandwidth -- but the service configuration has since changed in minor ways since the crash occured, and as it's now in production I'm most reluctant to put it back!
So if
- mailbox is created
- a new mail is APPENDed there
it crashes? The deletion part is probably irrelevant to the crash?
I don't have a rawlog of the transaction involved, but unless Alpine is doing something particularly interesting, then yes, that is the case.
I also agree that the deletion is almost certainly irrelevant to the crash.
Cheers, David
David McBride dwm@tastycake.net
On Thu, 2008-09-11 at 18:01 +0100, David McBride wrote:
So if
- mailbox is created
- a new mail is APPENDed there
it crashes? The deletion part is probably irrelevant to the crash?
I don't have a rawlog of the transaction involved, but unless Alpine is doing something particularly interesting, then yes, that is the case.
I also agree that the deletion is almost certainly irrelevant to the crash.
Looks like I can reproduce this with the above commands as long as quota plugin is loaded. I'll try to get it fixed soon.
On Thu, 2008-09-11 at 20:33 +0300, Timo Sirainen wrote:
On Thu, 2008-09-11 at 18:01 +0100, David McBride wrote:
So if
- mailbox is created
- a new mail is APPENDed there
it crashes? The deletion part is probably irrelevant to the crash?
I don't have a rawlog of the transaction involved, but unless Alpine is doing something particularly interesting, then yes, that is the case.
I also agree that the deletion is almost certainly irrelevant to the crash.
Looks like I can reproduce this with the above commands as long as quota plugin is loaded. I'll try to get it fixed soon.
participants (3)
-
David McBride
-
Dean Brooks
-
Timo Sirainen