v2.2.36 to v2.3.8 maildirlock bug

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

v2.2.36 to v2.3.8 maildirlock bug

Dovecot mailing list
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@spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1
Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
19276[root@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
Reply | Threaded
Open this post in threaded view
|

Re: v2.2.36 to v2.3.8 maildirlock bug

Dovecot mailing list


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@spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1
> Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
> 19276[root@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.
Reply | Threaded
Open this post in threaded view
|

Re: v2.2.36 to v2.3.8 maildirlock bug

Dovecot mailing list
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 <[hidden email]> 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@spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1
>> Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
>> 19276[root@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.

Reply | Threaded
Open this post in threaded view
|

Re: v2.2.36 to v2.3.8 maildirlock bug

Dovecot mailing list
On 06 Dec 2019, at 16:28, Martynas Bendorius <[hidden email]> wrote:
> when zlib compression is enabled in dovecot, old emails remain untouched

I’ve been considering doing this, or at least looking into how much space we’d save (answer so far, less than you might think), but I am hesitant to “alter” the user’s mail stores without a bit more guidance.

Has anyone found a good walkthrough/guide on setting this up and also on compressing the old mail?

Are there any common issues to watch out for? Is it entirely transparent to the user?

https://wiki2.dovecot.org/Plugins/Zlib says it has moved to https://doc.dovecot.org/plugin-settings/zlib_plugin/ which does not exist.

"Not Found
The requested URL /plugin-settings/zlib_plugin/ was not found on this server."



--
I'm dangerous when I know what I'm doing.

Reply | Threaded
Open this post in threaded view
|

Re: v2.2.36 to v2.3.8 maildirlock bug

Dovecot mailing list
On 08 Dec 2019, at 05:58, @lbutlr <[hidden email]> wrote:

> On 06 Dec 2019, at 16:28, Martynas Bendorius <[hidden email]> wrote:
>> when zlib compression is enabled in dovecot, old emails remain untouched
>
> I’ve been considering doing this, or at least looking into how much space we’d save (answer so far, less than you might think), but I am hesitant to “alter” the user’s mail stores without a bit more guidance.
>
> Has anyone found a good walkthrough/guide on setting this up and also on compressing the old mail?
>
> Are there any common issues to watch out for? Is it entirely transparent to the user?
>
> https://wiki2.dovecot.org/Plugins/Zlib says it has moved to https://doc.dovecot.org/plugin-settings/zlib_plugin/ which does not exist.
>
> "Not Found
> The requested URL /plugin-settings/zlib_plugin/ was not found on this server."

The ULR on that page has the _ character instead of a - in the URL.

<https://doc.dovecot.org/plugin-settings/zlib-plugin/> loads and leads to

<https://doc.dovecot.org/configuration_manual/zlib_plugin/#zlib-plugin>

Which, sadly, does not have example code on actually compressing the existing mail, but does say to use maildirlock.




--
Wife: Who are you talking to? Husb: [on phone] Jon Wife: Aren't you
        going to talk to me? Husb: I talked to you at dinner, do I need
        to talk to you again?