Nick Urbanik
2012-Apr-27 06:34 UTC
[Dovecot] 2.1.5: Panic: file mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name))
Dear Folks, We had this assertion failure on Dovecot 2.1.1 on a particular mailbox. I upgraded to 2.1.5, and we have the same assertion failure, on the same mailbox: Apr 27 16:02:03 imap(nu-imaptest00258 at example.com): Panic: file mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) Apr 27 16:02:03 imap(nu-imaptest00258 at example.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x4246a) [0x7f310c28146a] -> /usr/lib64/dovecot/libdovecot.so.0(+0x424b6) +[0x7f310c2814b6] -> /usr/lib64/dovecot/libdovecot.so.0(+0x1950a) [0x7f310c25850a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x889b5) [0x7f310c5539b5] -> +/usr/lib64/dovecot/lib10_quota_plugin.so(+0x8a30) [0x7f3109ccea30] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0x8cdf) [0x7f3109ccecdf] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0x93c8) +[0x7f3109ccf3c8] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0x9436) [0x7f3109ccf436] -> /usr/lib64/dovecot/lib10_quota_plugin.so(quota_get_resource+0x72) [0x7f3109cca792] -> +/usr/lib64/dovecot/lib10_quota_plugin.so(quota_test_alloc+0x1bd) [0x7f3109ccaaed] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0xa870) [0x7f3109cd0870] -> +/usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_save_begin+0x4d) [0x7f310c544b9d] -> dovecot/imap [nu-imaptest00258 at example.com 127.0.0.1 APPEND]() [0x408ac4] -> dovecot/imap +[nu-imaptest00258 at example.com 127.0.0.1 APPEND](cmd_append+0x139) [0x408d69] -> dovecot/imap [nu-imaptest00258 at example.com 127.0.0.1 APPEND](command_exec+0x3d) [0x410aed] -> dovecot/imap +[nu-imaptest00258 at example.com 127.0.0.1 APPEND]() [0x40fa2e] -> dovecot/imap [nu-imaptest00258 at example.com 127.0.0.1 APPEND]() [0x40fb1a] -> dovecot/imap [nu-imaptest00258 at example.com +127.0.0.1 APPEND](client_handle_input+0x135) [0x40fd45] -> dovecot/imap [nu-imaptest00258 at example.com 127.0.0.1 APPEND](client_input+0x5f) [0x41066f] -> +/usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f310c28d9d6] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) [0x7f310c28ea5f] -> +/usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f310c28d978] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f310c279c73] -> dovecot/imap [nu-imaptest00258 at example.com +127.0.0.1 APPEND](main+0x29d) [0x418b3d] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f310bebccdd] -> dovecot/imap [nu-imaptest00258 at example.com 127.0.0.1 APPEND]() [0x408449] Apr 27 16:02:03 imaptest01 perdition.imap4[15893]: Closing session: 211.29.132.209:42922->211.29.132.245:143 authorisation_id=NONE authentication_id="nu-imaptest00258" received=67 sent=53 Apr 27 16:02:03 imap(nu-imaptest00258 at example.com): Fatal: master: service(imap): child 15894 killed with signal 6 (core not dumped) Any suggestions welcome. I guess enabling core dumps is a good start, I'll do that, but has anyone seen this before? -- Nick Urbanik http://nicku.org 808-71011 nick.urbanik at optusnet.com.au GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24 I disclaim, therefore I am.
Timo Sirainen
2012-May-01 00:53 UTC
[Dovecot] 2.1.5: Panic: file mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name))
On Fri, 2012-04-27 at 16:34 +1000, Nick Urbanik wrote:> I upgraded to 2.1.5, and we have the same assertion failure, on the > same mailbox: > > Apr 27 16:02:03 imap(nu-imaptest00258 at example.com): Panic: file mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name))..> Any suggestions welcome. > > I guess enabling core dumps is a good start, I'll do that, but has > anyone seen this before?1) doveconf -n output 2) Can you show the list of all mailbox names? Or especially the one that is causing this crash? (The raw backtrace indicates it happens during quota recalculation, which gets a list of all mailboxes, so it might not really be the same mailbox as what appears to be broken.)