Hi, I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 2.2.19, but now panics (user with shared folder): /opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser
dsync(standl2): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(standl2): Error: Raw backtrace: /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb6fa) [0x7f43679986fa] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb769) [0x7f4367998769] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f43679069c1] -> /opt/dovecot/lib/dovecot/libdovecot-storage.so.0(+0x568ff) [0x7f4367c9d8ff] -> /opt/dovecot/bin/doveadm(dsync_mailbox_import_attribute+0x4d) [0x56234f7b68dd] -> /opt/dovecot/bin/doveadm(dsync_brain_sync_mails+0x2fd) [0x56234f7b217d] -> /opt/dovecot/bin/doveadm(dsync_brain_run+0x538) [0x56234f7adb28] -> /opt/dovecot/bin/doveadm(+0x27fec) [0x56234f793fec] -> /opt/dovecot/bin/doveadm(+0x2a0e7) [0x56234f7960e7] -> /opt/dovecot/bin/doveadm(+0x2ad7b) [0x56234f796d7b] -> /opt/dovecot/bin/doveadm(doveadm_mail_try_run+0x1fa) [0x56234f79769a] -> /opt/dovecot/bin/doveadm(main+0x45b) [0x56234f786b2b] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f4367523830] -> /opt/dovecot/bin/doveadm(_start+0x29) [0x56234f786ca9]
regards, infoomatic
Hi,
Any info on this one? btw, did a c&p error (standl2 is the username, of course)
Regards, infoomatic
Gesendet: Samstag, 07. Juli 2018 um 03:31 Uhr Von: Infoomatic <infoomatic@gmx.at> An: dovecot@dovecot.org Betreff: dsync panic
Hi, I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 2.2.19, but now panics (user with shared folder): /opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser
dsync(standl2): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(standl2): Error: Raw backtrace: /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb6fa) [0x7f43679986fa] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb769) [0x7f4367998769] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f43679069c1] -> /opt/dovecot/lib/dovecot/libdovecot-storage.so.0(+0x568ff) [0x7f4367c9d8ff] -> /opt/dovecot/bin/doveadm(dsync_mailbox_import_attribute+0x4d) [0x56234f7b68dd] -> /opt/dovecot/bin/doveadm(dsync_brain_sync_mails+0x2fd) [0x56234f7b217d] -> /opt/dovecot/bin/doveadm(dsync_brain_run+0x538) [0x56234f7adb28] -> /opt/dovecot/bin/doveadm(+0x27fec) [0x56234f793fec] -> /opt/dovecot/bin/doveadm(+0x2a0e7) [0x56234f7960e7] -> /opt/dovecot/bin/doveadm(+0x2ad7b) [0x56234f796d7b] -> /opt/dovecot/bin/doveadm(doveadm_mail_try_run+0x1fa) [0x56234f79769a] -> /opt/dovecot/bin/doveadm(main+0x45b) [0x56234f786b2b] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f4367523830] -> /opt/dovecot/bin/doveadm(_start+0x29) [0x56234f786ca9]
regards, infoomatic
On 7 Jul 2018, at 4.31, Infoomatic <infoomatic@gmx.at> wrote:
Hi, I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 2.2.19, but now panics (user with shared folder): /opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser
Not sure why it panics, but at least your command line looks incorrect.
please try: doveadm backup -u testuser sdbox:/tmp/testuser
your options are:
doveadm backup doveadm sync doveadm sync -1
https://wiki2.dovecot.org/Tools/Doveadm/Sync <https://wiki2.dovecot.org/Tools/Doveadm/Sync>
Sami
I think I get pretty much the same issue:
dsync(support): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(support): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc9e06) [0x7fba8a348e06] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fba8a348e4a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fba8a2bd813] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x597fc) [0x7fba8a64f7fc] -> dsync(dsync_mailbox_import_attribute+0x3a) [0x55d72a8ac37a] -> dsync(dsync_brain_sync_mails+0x2ef) [0x55d72a8a7e9f] -> dsync(dsync_brain_run+0x2b0) [0x55d72a8a3690] -> dsync(+0x29f5c) [0x55d72a88af5c] -> dsync(+0x2bd97) [0x55d72a88cd97] -> dsync(+0x2c878) [0x55d72a88d878] -> dsync(doveadm_mail_try_run+0x205) [0x55d72a88e1f5] -> dsync(main+0x475) [0x55d72a87de85] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fba89c8d725] -> dsync(_start+0x29) [0x55d72a87e009]
with command:
doveadm backup -x "virtual/*" -x "shared/*" -u support sdbox:/srv/dovecot/support/sdbox
with version 2.3.2.1
Wolfgang
On 13 Jul 2018, at 21.39, Wolfgang Rosenauer <wrosenauer@gmail.com <mailto:wrosenauer@gmail.com>> wrote:
I think I get pretty much the same issue:
dsync(support): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(support): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc9e06) [0x7fba8a348e06] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fba8a348e4a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fba8a2bd813] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x597fc) [0x7fba8a64f7fc] -> dsync(dsync_mailbox_import_attribute+0x3a) [0x55d72a8ac37a] -> dsync(dsync_brain_sync_mails+0x2ef) [0x55d72a8a7e9f] -> dsync(dsync_brain_run+0x2b0) [0x55d72a8a3690] -> dsync(+0x29f5c) [0x55d72a88af5c] -> dsync(+0x2bd97) [0x55d72a88cd97] -> dsync(+0x2c878) [0x55d72a88d878] -> dsync(doveadm_mail_try_run+0x205) [0x55d72a88e1f5] -> dsync(main+0x475) [0x55d72a87de85] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fba89c8d725] -> dsync(_start+0x29) [0x55d72a87e009]
Already fixed, but was scheduled for v2.3.3: https://github.com/dovecot/core/commit/4ff4bd024a9b6e7973b76b186ce085c2ca669... <https://github.com/dovecot/core/commit/4ff4bd024a9b6e7973b76b186ce085c2ca669d3e>
As a workaround, you could disable ACL when running dsync: doveadm -o plugin/acl= ...
Hi,
I can confirm that the commit fixed the crash in dsync for me.
Thanks, Wolfgang
On Fri, Jul 13, 2018 at 10:43 PM, Timo Sirainen <tss@iki.fi> wrote:
On 13 Jul 2018, at 21.39, Wolfgang Rosenauer <wrosenauer@gmail.com> wrote:
I think I get pretty much the same issue:
dsync(support): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(support): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc9e06) [0x7fba8a348e06] -> /usr/lib64/dovecot/libdovecot. so.0(default_fatal_handler+0x2a) [0x7fba8a348e4a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fba8a2bd813] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x597fc) [0x7fba8a64f7fc] -> dsync(dsync_mailbox_import_attribute+0x3a) [0x55d72a8ac37a] -> dsync(dsync_brain_sync_mails+0x2ef) [0x55d72a8a7e9f] -> dsync(dsync_brain_run+0x2b0) [0x55d72a8a3690] -> dsync(+0x29f5c) [0x55d72a88af5c] -> dsync(+0x2bd97) [0x55d72a88cd97] -> dsync(+0x2c878) [0x55d72a88d878] -> dsync(doveadm_mail_try_run+0x205) [0x55d72a88e1f5] -> dsync(main+0x475) [0x55d72a87de85] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fba89c8d725] -> dsync(_start+0x29) [0x55d72a87e009]
Already fixed, but was scheduled for v2.3.3: https://github.com/ dovecot/core/commit/4ff4bd024a9b6e7973b76b186ce085c2ca669d3e
As a workaround, you could disable ACL when running dsync: doveadm -o plugin/acl= ...
Am 13.07.2018 um 22:43 schrieb Timo Sirainen:
On 13 Jul 2018, at 21.39, Wolfgang Rosenauer <wrosenauer@gmail.com <mailto:wrosenauer@gmail.com>> wrote:
I think I get pretty much the same issue:
dsync(support): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(support): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc9e06) [0x7fba8a348e06] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fba8a348e4a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fba8a2bd813] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x597fc) [0x7fba8a64f7fc] -> dsync(dsync_mailbox_import_attribute+0x3a) [0x55d72a8ac37a] -> dsync(dsync_brain_sync_mails+0x2ef) [0x55d72a8a7e9f] -> dsync(dsync_brain_run+0x2b0) [0x55d72a8a3690] -> dsync(+0x29f5c) [0x55d72a88af5c] -> dsync(+0x2bd97) [0x55d72a88cd97] -> dsync(+0x2c878) [0x55d72a88d878] -> dsync(doveadm_mail_try_run+0x205) [0x55d72a88e1f5] -> dsync(main+0x475) [0x55d72a87de85] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fba89c8d725] -> dsync(_start+0x29) [0x55d72a87e009]
Already fixed, but was scheduled for v2.3.3: https://github.com/dovecot/core/commit/4ff4bd024a9b6e7973b76b186ce085c2ca669...
As a workaround, you could disable ACL when running dsync: doveadm -o plugin/acl= ...
Judging the 2.2 master src I assume that this patch is also applicable on 2.2.36? While we are at it: Will the 2.2 branch receive another minor release or is 2.2.36 already the final 2.2 version?
MS
participants (5)
-
Infoomatic
-
Michael Seevogel
-
Sami Ketola
-
Timo Sirainen
-
Wolfgang Rosenauer