namespace assertion failed
Hello,
I'm trying to figure out if this is a configuration issue or an actual bug. Dovecot does start, but if anybody tries to log in or if you run sievec you get an assertion fail and a coredump.
sievec(root): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) sievec(root): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9c3a2) [0x7ff70e2133a2] -> /usr/lib/dovecot/libdovecot.so.0(+0x9c429) [0x7ff70e213429] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff70e1a5e41] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find+0xc8) [0x7ff70e4e03a8] -> /usr/lib/dovecot/modules/lib11_trash_plugin.so(+0x1e56) [0x7ff70d5ace56] -> /usr/lib/dovecot/libdovecot-storage.so.0(hook_mail_user_created+0x1eb) [0x7ff70e4ecfeb] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_user_init+0x206) [0x7ff70e4f1fb6] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_next+0x438) [0x7ff70e4f00c8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_lookup_next+0x4c) [0x7ff70e4f068c] -> sievec(sieve_tool_init_finish+0xc1) [0x403371] -> sievec(main+0xd2) [0x402cb2] -> /usr/lib/libc.so.6(__libc_start_main+0xf1) [0x7ff70ddf3511] -> sievec(_start+0x2a) [0x402f3a] Aborted (core dumped)
Coredump as follows:
#0 0x00007ff70de06a10 in raise () from /usr/lib/libc.so.6 #1 0x00007ff70de0813a in abort () from /usr/lib/libc.so.6 #2 0x00007ff70e21339a in ?? () from /usr/lib/dovecot/libdovecot.so.0 #3 0x00007ff70e213429 in default_fatal_handler () from /usr/lib/dovecot/libdovecot.so.0 #4 0x00007ff70e1a5e41 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 #5 0x00007ff70e4e03a8 in mail_namespace_find () from /usr/lib/dovecot/libdovecot-storage.so.0 #6 0x00007ff70d5ace56 in ?? () from /usr/lib/dovecot/modules/lib11_trash_plugin.so #7 0x00007ff70e4ecfeb in hook_mail_user_created () from /usr/lib/dovecot/libdovecot-storage.so.0 #8 0x00007ff70e4f1fb6 in mail_user_init () from /usr/lib/dovecot/libdovecot-storage.so.0 #9 0x00007ff70e4f00c8 in mail_storage_service_next () from /usr/lib/dovecot/libdovecot-storage.so.0 #10 0x00007ff70e4f068c in mail_storage_service_lookup_next () from /usr/lib/dovecot/libdovecot-storage.so.0 #11 0x0000000000403371 in sieve_tool_init_finish () #12 0x0000000000402cb2 in main ()
Any help appreciated!
-Sam
Here's a core dump from a login process:
#0 0x00007f8ac70cba10 raise (libc.so.6)
#1 0x00007f8ac70cd13a abort (libc.so.6)
#2 0x00007f8ac74d839a n/a (libdovecot.so.0)
#3 0x00007f8ac74d849d n/a (libdovecot.so.0)
#4 0x00007f8ac746ae41 i_panic (libdovecot.so.0)
#5 0x00007f8ac77a53a8 mail_namespace_find(libdovecot-storage.so.0) #6 0x00007f8ac6879e56 n/a (lib11_trash_plugin.so) #7 0x00007f8ac77b1feb hook_mail_user_created (libdovecot-storage.so.0) #8 0x00007f8ac77b6fb6 mail_user_init (libdovecot-storage.so.0) #9 0x00007f8ac77b50c8 mail_storage_service_next (libdovecot-storage.so.0) #10 0x00007f8ac77b568c mail_storage_service_lookup_next (libdovecot-storage.so.0) #11 0x00000000004263d6 client_create_from_input (imap) #12 0x00000000004265df n/a (imap) #13 0x00007f8ac7472c6e n/a (libdovecot.so.0) #14 0x00007f8ac7472efd n/a (libdovecot.so.0) #15 0x00007f8ac74738bf n/a (libdovecot.so.0) #16 0x00007f8ac74ed152 io_loop_call_io (libdovecot.so.0) #17 0x00007f8ac74ee779 io_loop_handler_run_internal (libdovecot.so.0) #18 0x00007f8ac74ed1ec io_loop_handler_run (libdovecot.so.0) #19 0x00007f8ac74ed398 io_loop_run (libdovecot.so.0) #20 0x00007f8ac7475223 master_service_run (libdovecot.so.0) #21 0x000000000040c992 main (imap)
On Thu, Apr 20, 2017 at 11:29 AM, Elisamuel Resto <elisamuel.resto@gmail.com
wrote:
Hello,
I'm trying to figure out if this is a configuration issue or an actual bug. Dovecot does start, but if anybody tries to log in or if you run sievec you get an assertion fail and a coredump.
sievec(root): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) sievec(root): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9c3a2) [0x7ff70e2133a2] -> /usr/lib/dovecot/libdovecot.so.0(+0x9c429) [0x7ff70e213429] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff70e1a5e41] -> /usr/lib/dovecot/libdovecot- storage.so.0(mail_namespace_find+0xc8) [0x7ff70e4e03a8] -> /usr/lib/dovecot/modules/lib11_trash_plugin.so(+0x1e56) [0x7ff70d5ace56] -> /usr/lib/dovecot/libdovecot-storage.so.0(hook_mail_user_created+0x1eb) [0x7ff70e4ecfeb] -> /usr/lib/dovecot/libdovecot- storage.so.0(mail_user_init+0x206) [0x7ff70e4f1fb6] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_next+0x438) [0x7ff70e4f00c8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_lookup_next+0x4c) [0x7ff70e4f068c] -> sievec(sieve_tool_init_finish+0xc1) [0x403371] -> sievec(main+0xd2) [0x402cb2] -> /usr/lib/libc.so.6(__libc_start_main+0xf1) [0x7ff70ddf3511] -> sievec(_start+0x2a) [0x402f3a] Aborted (core dumped)
Coredump as follows:
#0 0x00007ff70de06a10 in raise () from /usr/lib/libc.so.6 #1 0x00007ff70de0813a in abort () from /usr/lib/libc.so.6 #2 0x00007ff70e21339a in ?? () from /usr/lib/dovecot/libdovecot.so.0 #3 0x00007ff70e213429 in default_fatal_handler () from /usr/lib/dovecot/libdovecot.so.0 #4 0x00007ff70e1a5e41 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 #5 0x00007ff70e4e03a8 in mail_namespace_find () from /usr/lib/dovecot/libdovecot-storage.so.0 #6 0x00007ff70d5ace56 in ?? () from /usr/lib/dovecot/modules/ lib11_trash_plugin.so #7 0x00007ff70e4ecfeb in hook_mail_user_created () from /usr/lib/dovecot/libdovecot-storage.so.0 #8 0x00007ff70e4f1fb6 in mail_user_init () from /usr/lib/dovecot/libdovecot-storage.so.0 #9 0x00007ff70e4f00c8 in mail_storage_service_next () from /usr/lib/dovecot/libdovecot-storage.so.0 #10 0x00007ff70e4f068c in mail_storage_service_lookup_next () from /usr/lib/dovecot/libdovecot-storage.so.0 #11 0x0000000000403371 in sieve_tool_init_finish () #12 0x0000000000402cb2 in main ()
Any help appreciated!
-Sam
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 20 Apr 2017, Elisamuel Resto wrote:
I'm trying to figure out if this is a configuration issue or an actual bug.
The assertion certainly is a bug, but you should post your config, too, in order to let Timo, Aki,& Co. see, how to reproduce the issue.
Dovecot does start, but if anybody tries to log in or if you run sievec you
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEVAwUBWPmkR3z1H7kL/d9rAQI3DAf8C/4TsH8wICLPa3JslyRp3QJHC5cXfCQs xS9WTmgSVALqKfz5D0rWbJkjRwdv9QeiXPXwLwLiV57CFYlQIUuWXzEtnv8JNbot FsrzkpLfnJX6hxosgexNE6k+TKrUfkcQCoR13hBNOLbvtcZtXuqzWF6tDrSfzWI5 tzPvfLnwPXOZFphNnTf+SIYcONbAyBK/pCOgaTFb+eoTbaAguytNQH/diURE7EZQ cEWLoflQnO7iaNwv6x5WtkDOhKV3nzWA1bnyfnA9BqYdeLtSGW1VO0WsH8/iBVCT Yu2D51AfFqISchZbBiWmwQYwgOG0iFhGguT8kxRr/ryD2XcB+EhozA== =k6fh -----END PGP SIGNATURE-----
On 20 Apr 2017, at 19.29, Elisamuel Resto <elisamuel.resto@gmail.com> wrote:
Hello,
I'm trying to figure out if this is a configuration issue or an actual bug. Dovecot does start, but if anybody tries to log in or if you run sievec you get an assertion fail and a coredump.
sievec(root): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) sievec(root): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9c3a2) [0x7ff70e2133a2] -> /usr/lib/dovecot/libdovecot.so.0(+0x9c429) [0x7ff70e213429] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff70e1a5e41] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find+0xc8) [0x7ff70e4e03a8] -> /usr/lib/dovecot/modules/lib11_trash_plugin.so(+0x1e56)
Trash plugin was broken in 2.2.28. Use 2.2.29.
participants (3)
-
Elisamuel Resto
-
Steffen Kaiser
-
Timo Sirainen