Dear all, Dovecot upgraded from v2.2.36 to v2.3.8 There is no problem with the configuration, but the lock directory seems to have an error. [root at spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1 Panic: BUG: No IOs or timeouts set. Not waiting for infinity. 19276[root at spam dovecot]# Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xe227a) [0x7f1cb567a27a] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe2321) [0x7f1cb567a321] -> /usr/lib64/dovecot/libdovecot.so.0(+0x40f31) [0x7f1cb55d8f31] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf93b4) [>xrf1cb56913b4] -> /usr/ Lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x28) [0x7f1cb5693918] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5c) [0x7f1cb5691aac] -> /usr/lib64/dovecot/libdovecot. So.0(io_loop_run+0x38) [0x7f1cb5691cc8] -> /usr/libexec/dovecot/maildirlock(main+0x242) [0x7f1cb5b522c2] -> /lib64/libc.so.6(__libc_start_main+0x100) [0x7f1cb5222d20] -> / Usr/libexec/dovecot/maildirlock(+0xfa9) [0x7f1cb5b51fa9] After google seems to be a bug, this is the address Https://bugs.gentoo.org/682498 If this is not fixed, we are temporarily unable to upgrade to use the new version. Will the next version be fixed? We are looking forward to seeing that we have returned v2.2.36 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20191022/44204a3c/attachment.html>
On 22/10/2019 05:44, lty--- via dovecot wrote:> Dear all, > ? Dovecot upgraded from v2.2.36 to v2.3.8?There is no problem with the > configuration, but the lock directory seems to have an error. > > [root at spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1 > Panic: BUG: No IOs or timeouts set. Not waiting for infinity. > 19276[root at spam dovecot]# Error: Raw backtrace: > /usr/lib64/dovecot/libdovecot.so.0(+0xe227a) [0x7f1cb567a27a] -> > /usr/lib64/dovecot/libdovecot.so.0(+0xe2321) [0x7f1cb567a321] -> > /usr/lib64/dovecot/libdovecot.so.0(+0x40f31) [0x7f1cb55d8f31] -> > /usr/lib64/dovecot/libdovecot.so.0(+0xf93b4) [>xrf1cb56913b4] -> /usr/ > Lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x28) > [0x7f1cb5693918] -> > /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5c) > [0x7f1cb5691aac] -> /usr/lib64/dovecot/libdovecot. > So.0(io_loop_run+0x38) [0x7f1cb5691cc8] -> > /usr/libexec/dovecot/maildirlock(main+0x242) [0x7f1cb5b522c2] -> > /lib64/libc.so.6(__libc_start_main+0x100) [0x7f1cb5222d20] -> / > Usr/libexec/dovecot/maildirlock(+0xfa9) [0x7f1cb5b51fa9] > > > After google seems to be a bug, this is the address > Https://bugs.gentoo.org/682498 > > If this is not fixed, we are temporarily unable to upgrade to use the > new version. Will the next version be fixed? We are looking forward to > seeing that we have returned v2.2.36The maildirlock tool will likely be deprecated. You should use dsync instead for making backups. Regards, Stephan.
Hello, Aki created this patch a while ago: http://files1.directadmin.com/services/custombuild/patches/maildirlock-crash.patch It works perfectly to fix the issue :) Regarding dsync - I don't think it's a good replacement in all the cases, is it? We use maildirlock extensively for compression of email folders (when zlib compression is enabled in dovecot, old emails remain untouched). -- Best regards, Martynas Bendorius> On 2019-12-07, at 00:46, Stephan Bosch via dovecot <dovecot at dovecot.org> wrote: > > > > On 22/10/2019 05:44, lty--- via dovecot wrote: >> Dear all, >> Dovecot upgraded from v2.2.36 to v2.3.8 There is no problem with the configuration, but the lock directory seems to have an error. >> >> [root at spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1 >> Panic: BUG: No IOs or timeouts set. Not waiting for infinity. >> 19276[root at spam dovecot]# Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xe227a) [0x7f1cb567a27a] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe2321) [0x7f1cb567a321] -> /usr/lib64/dovecot/libdovecot.so.0(+0x40f31) [0x7f1cb55d8f31] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf93b4) [>xrf1cb56913b4] -> /usr/ Lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x28) [0x7f1cb5693918] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5c) [0x7f1cb5691aac] -> /usr/lib64/dovecot/libdovecot. So.0(io_loop_run+0x38) [0x7f1cb5691cc8] -> /usr/libexec/dovecot/maildirlock(main+0x242) [0x7f1cb5b522c2] -> /lib64/libc.so.6(__libc_start_main+0x100) [0x7f1cb5222d20] -> / Usr/libexec/dovecot/maildirlock(+0xfa9) [0x7f1cb5b51fa9] >> >> >> After google seems to be a bug, this is the address >> Https://bugs.gentoo.org/682498 >> >> If this is not fixed, we are temporarily unable to upgrade to use the new version. Will the next version be fixed? We are looking forward to seeing that we have returned v2.2.36 > > The maildirlock tool will likely be deprecated. You should use dsync instead for making backups. > > Regards, > > Stephan.