Displaying 20 results from an estimated 2000 matches similar to: "auth-worker service failed since recent MariaDB upgrade"
2019 Jan 20
2
auth-worker service failed since recent MariaDB upgrade
Hello Aki,
This patch seems to have done the trick - hopefully it works fine and
doesn't mask the problem.
From the patch content, I see that it's from 4th of December.
Is there a reason why this hasn't made it yet into upstream?
Did you come across this bug on your own and patch it temporarily?
Best regards,
---
BOGOMIL VASILEV
For contacts, use this e-mail. My GPG key is
2019 Jan 20
2
auth-worker service failed since recent MariaDB upgrade
Hello,
I rebuilt mariadb and dovecot with debug symbols.
The backtrace is this:
Program terminated with signal SIGABRT, Aborted.
#0 0x00007fb040e0cd7f in raise () from /usr/lib/libc.so.6
(gdb) bt full
#0 0x00007fb040e0cd7f in raise () from /usr/lib/libc.so.6
No symbol table info available.
#1 0x00007fb040df7672 in abort () from /usr/lib/libc.so.6
No symbol table info available.
#2
2019 Jan 20
0
auth-worker service failed since recent MariaDB upgrade
Op 20/01/2019 om 15:30 schreef Bogomil Vasilev via dovecot:
> Hello Aki,
>
> This patch seems to have done the trick - hopefully it works fine and
> doesn't mask the problem.
> From the patch content, I see that it's from 4th of December.
> Is there a reason why this hasn't made it yet into upstream?
It is still being tested in QA (other stuff came first). It is
2019 Jan 20
0
auth-worker service failed since recent MariaDB upgrade
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Can you try if https://github.com/dovecot/core/commit/3c5101ffdd2a8115e03ed7180d53578765dea4c9.patch helps?
<br>
</div>
<div>
<br>
</div>
<div>
Aki
</div>
<blockquote type="cite">
2019 Jan 20
0
auth-worker service failed since recent MariaDB upgrade
Op 20/01/2019 om 10:50 schreef Bogomil Vasilev via dovecot:
> Hello,
>
> I have started having issues with auth-worker. Dovecot version:
>
> ?0 ? root ? ~ # dovecot --version
> 2.3.4 (0ecbaf23d)
> ?0 ? root ? ~ # pacman -Q dovecot
> dovecot 2.3.4-2
>
> OS: Arch Linux
>
> From /var/log/mail.log:
>
> Jan 20 11:31:29 archy dovecot[23070]: auth-worker: Fatal:
2019 Jan 27
1
auth-worker: Error: double free or corruption (fasttop)
Hi,
Sorry fo my late answer. The hole disty are stripped. I must first
rebuild all with debug symbols.
Here comes the complete gdb backtrace:
(gdb) bt full
#0 0x00007f49738486f7 in raise () from /lib64/libc.so.6
No symbol table info available.
#1 0x00007f497384a091 in abort () from /lib64/libc.so.6
No symbol table info available.
#2 0x00007f497389220f in __libc_message () from
2018 Dec 03
3
Dovecot 2.3.4 crash
On 2 Dec 2018, at 22.22, Guillaume via dovecot <dovecot at dovecot.org> wrote:
>
> I also have this kind of segfault since the update :
>
> Dec 2 21:12:11 xxxxxxx dovecot: auth-worker: Error: *** Error in `dovecot/auth': double free or corruption (fasttop): 0x000055573bb99f70
Is this easy to reproduce? Can you try with valgrind? It will slow down the logins a bit though.
2019 Jan 16
2
auth-worker: Error: double free or corruption (fasttop)
Dear list,
since the distri upgrade to glibc 2.28, i can't build working dovecot
binary's.
Older with glibc 2.27 are working. The distri is LFS based.
MariaDB 10.2.18 and 10.3.11 makes no difference. Having this on
different systems.
Messages Log:
Dec 19 17:10:38 test kernel: traps: auth[30189] general protection
ip:7f4b96d6598c sp:7ffef1f31710 error:0 in
2018 Dec 02
0
Dovecot 2.3.4 crash
OK I find out how to extract core dump (sorry), hope this will help you.
gdb /usr/lib/dovecot/auth /var/core/core.28304
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the
2018 Dec 04
3
[2.3.4] Segmentation faults
Thanks for mySql
For Squat vs Solr, Solr does not reach Squat by very far in terms of
results : If I setup Solr, and search (via the search in Roundbube or
Evolution) for a keyword or part of the keyword, the results are
complete non sense. The diference between "search in full body" and
"search in fields" does not even work.
Solr with Dovecot seems very early beta
2018 Dec 04
2
[2.3.4] Segmentation faults
Hi
How to solve this ?
So many similar segfaults
Thank you
On 2018-11-30 06:11, Joan Moreau wrote:
> ANother (very very long) example :
>
> # gdb /usr/libexec/dovecot/indexer-worker core.indexer-worker.0.3a33f56105e043de802a7dfcee265a07.21017.1543533424000000
> GNU gdb (GDB) 8.2
> Copyright (C) 2018 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or
2018 Nov 29
3
[2.3.4] Segmentation faults
finally managed to locate the dump
here the output:
# gdb /usr/libexec/dovecot/auth
/var/lib/systemd/coredump/core.auth.0.3a33f56105e043de802a7dfcee265a07.28130.1543516118000000
GNU gdb (GDB) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
2018 Dec 04
2
[2.3.4] Segmentation faults
> On December 4, 2018 at 8:18 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
>
> We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though.
FWIW, Squat has been deprecated since 2.0, so none of this should come as a surprise.
https://wiki.dovecot.org/Plugins/FTS
> Aki
>
> > On 04 December
2018 Dec 04
0
Dovecot 2.3.4 crash
Hi !
Yes it happens every 2 to 5 minutes so no problem in reproducing.
I made the change with valgrind, I have now this in my log :
Dec 4 12:00:27 xxxxx dovecot: auth-worker: Error: ==2436== Invalid read of size 8
Dec 4 12:00:27 xxxxx dovecot: auth-worker: Error: ==2393== Invalid read of size 8
Dec 4 12:00:27 xxxxx dovecot: auth-worker: Error: ==2476== Invalid read of size 8
Dec 4 12:00:27
2018 Dec 04
3
Dovecot 2.3.4 crash
A full example with dovecot debug symbols activated (note since I have activate valgrind, no more segfault it?s normal I presume ):
Dec 4 12:09:40 dovecot: auth-worker: Error: ==3071== Invalid read of size 8
Dec 4 12:09:40 dovecot: auth-worker: Error: ==3053== Invalid read of size 8
Dec 4 12:09:40 dovecot: auth-worker: Error: ==3057== Invalid read of size 8
Dec 4 12:09:40 dovecot:
2018 Nov 28
2
[2.3.4] Segmentation faults
See https://dovecot.org/bugreport.html#coredumps
Without a backtrace it's not really possible to figure out where it's crashing.
> On 28 Nov 2018, at 13.20, Joan Moreau <jom at grosjo.net> wrote:
>
> Where to get that ?
>
>
> On 2018-11-27 08:50, Aki Tuomi wrote:
>
>> It's still missing core dump (or bt full from it)
>>
>> Aki
2019 Apr 08
1
dovecot[30008]: auth-worker: Fatal: master: service(auth-worker): child 31074 killed with signal 11
Hi
Since a recent DNF update, I see many log file entries like the following:
Apr 08 16:16:36 udoo.symmetrix.ch audit[31074]: ANOM_ABEND
auid=4294967295 uid=0 gid=0 ses=4294967295
subj=system_u:system_r:dovecot_auth_t:s0 pid=31074 comm="auth"
exe="/usr/libexec/dovecot/auth" sig=11 res=1
Apr 08 16:16:36 udoo.symmetrix.ch kernel: traps: auth[31074] general
protection fault
2010 Aug 20
2
PATCH: SQL connect crash
Hi!
Dovecot 2.0.0 auth process seems to crash while attempting to
connect to a nonexistent SQL database. A shallow look at the code
reveals that NULL module->conn in passdb-sql.c is being erroneously
dereferenced while trying to clean up after a failed connection
attempt:
(gdb) bt
#0 0x0806240e in sql_query_callback (result=0x8076c40, sql_request=0x808ff90)
at passdb-sql.c:70
#1
2018 Dec 04
0
[2.3.4] Segmentation faults
> On 04 December 2018 at 16:46 Joan Moreau via dovecot <dovecot at dovecot.org> wrote:
>
>
> Hi
>
> How to solve this ?
>
> So many similar segfaults
>
> Thank you
>
> On 2018-11-30 06:11, Joan Moreau wrote:
>
> > ANother (very very long) example :
> >
> > # gdb /usr/libexec/dovecot/indexer-worker
2018 Dec 04
0
[2.3.4] Segmentation faults
We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though.
Aki
> On 04 December 2018 at 17:16 Joan Moreau <jom at grosjo.net> wrote:
>
>
> Thanks for mySql
>
> For Squat vs Solr, Solr does not reach Squat by very far in terms of
> results : If I setup Solr, and search (via the search in Roundbube