Hello,
on my dovecot-replicator-backend I see lots of panic-messages "assertion
failed: (ctx->nested_parts_count > 0)", produced from a single user. I
assume that this is correlated with
https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b02...
How can I identify the incorrect formatted message in the user's
mailbox? I want to remove it, as the error-processes drive up the
backend's load incredibly.
Will a fixed dovecot-package be out soon?
Any help is appreciated.
Best regards,
Andreas
My system-data:
# 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.11 (6c69c917)
# OS: Linux 4.15.0-122-generic x86_64 Ubuntu 18.04.5 LTS
An example error-message:
Nov 04 08:04:25 vhrz311 dovecot[6163]:
imap(xxx@staff.uni-marburg.de)<63176>: Panic: file
message-parser.c: line 174 (message_part_finish): assertion failed:
(ctx->nested_parts_count > 0)
Nov 04 08:04:25 vhrz311 dovecot[6163]:
imap(xxx@staff.uni-marburg.de)<63173><ORvjlkKzRs2sGQEp>: Fatal: master:
service(imap): child 63173 killed with signal 6 (core dumps disabled -
https://dovecot.org/bugreport.html#coredumps)
Nov 04 08:04:25 vhrz311 dovecot[6163]:
imap(xxx@staff.uni-marburg.de)<63176>: Error: Raw
backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42)
[0x7f1dd28d6d22] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e)
[0x7f1dd28d6e3e] -> /usr/lib/dovecot/libdovecot.so.0(+0xed75e)
[0x7f1dd28e175e] -> /usr/lib/dovecot/libdovecot.so.0(+0xed801)
[0x7f1dd28e1801] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f1dd2836beb] -> /usr/lib/dovecot/libdovecot.so.0(+0xcd40e)
[0x7f1dd28c140e] ->
/usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x15c)
[0x7f1dd28c2b2c] ->
/usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa0)
[0x7f1dd28c52a0] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc8f9e)
[0x7f1dd2c67f9e] ->
/usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45)
[0x7f1dd2be31e5] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xca111)
[0x7f1dd2c69111] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcb214)
[0x7f1dd2c6a214] ->
/usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x10d)
[0x7f1dd2c6a9ed] ->
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x22)
[0x7f1dd2becdf2] -> dovecot/imap(+0x25eb1) [0x561689529eb1] ->
dovecot/imap(command_exec+0x64) [0x561689522bc4] ->
dovecot/imap(+0x25592) [0x561689529592] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x12f)
[0x7f1dd28fa3ff] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbe)
[0x7f1dd28fbebe] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c)
[0x7f1dd28fa75c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38)
[0x7f1dd28fa988] ->
/usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13)
[0x7f1dd2867c23] -> dovecot/imap(main+0x339) [0x561689512d19] ->
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f1dd2424bf7]
-> dovecot/imap(_start+0x2a) [0x561689512f2a]