Re: CVE-2019-11500 and LMTP error
Op 9-9-2019 om 11:26 schreef Gabriele Nencioni via dovecot: Hi all, does the dovecot fixed version: 2.3.7.2, 2.2.36.4 (as the CVE-2019-11500 says) fix the LMTP error "Got unexpected reply" as well? The LMTP error "Got unexpected reply" is described here: https://dovecot.org/pipermail/dovecot/2018-August/112562.html https://dovecot.org/pipermail/dovecot/2018-August/112666.html This was tracked internally as DOV-2864, which was released as part of 2.3.6. Regards, Stephan.
Re: Dovecot 2.3.7.2 lucene segfault and coredump
Hi Stephan,
thanks for your replay.
This is bt full output:
(gdb) bt full
#0 clear (this=0x0) at
/usr/src/debug/clucene-core-2.3.3.4/src/core/CLucene/util/VoidMap.h:123
No locals.
#1 lucene::search::FieldSortedHitQueue::_shutdown () at
/usr/src/debug/clucene-core-2.3.3.4/src/core/CLucene/search/FieldSortedHitQueue.cpp:60
No locals.
#2 0x7f7dc5eabe96 in _lucene_shutdown () at
/usr/src/debug/clucene-core-2.3.3.4/src/core/CLucene/StdHeader.cpp:33
No locals.
#3 0x7f7dc973bfbb in module_dir_deinit (modules=) at
module-dir.c:578
_data_stack_cur_id = 4
module = 0x55ddb26268f0
rev = 0x55ddb25bd050
i =
count = 6
#4 0x7f7dc973c001 in module_dir_unload
(modules=modules@entry=0x7f7dc9d2a380 ) at
module-dir.c:590
module =
next =
#5 0x7f7dc9a26264 in mail_storage_service_deinit
(_ctx=_ctx@entry=0x55ddb25d9848) at mail-storage-service.c:1730
ctx = 0x55ddb2612c18
#6 0x55ddb0e0dd35 in doveadm_mail_cmd_exec (ctx=ctx@entry=0x55ddb25d9808,
wildcard_user=wildcard_user@entry=0x0) at doveadm-mail.c:673
cctx =
cli =
ret =
error = 0x7f7dc96762f7 <__x86_return_thunk+5>
"\363\220\017\256\350\353\371H\215d$\b\303\350\a"
#7 0x55ddb0e0ebbd in doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=) at doveadm-mail.c:1144
mctx = 0x55ddb25d9808
wildcard_user =
fieldstr = 0x55ddb25b9318 "\315\"N\305}\177"
pargv = {arr = {buffer = 0x55ddb25d9a38, element_size = 8}, v =
0x55ddb25d9a38, v_modifiable = 0x55ddb25d9a38}
full_args = {arr = {buffer = , element_size = 8}, v =
, v_modifiable = }
i =
cli =
tcp_server =
mail_cmd = {alloc = 0x7f7dc54e1d00 , name =
0x7f7dc54e22b6 "quota get", usage_args = 0x7f7dc54e2291 ""}
dashdash = 0x55ddb0e4a7ca "--"
args_pos = 1
#8 0x55ddb0e1fc98 in doveadm_cmd_run_ver2 (argc=argc@entry=1,
argv=argv@entry=0x55ddb25b9158, cctx=cctx@entry=0x77c52670) at
doveadm-cmd.c:574
param =
pargv = {arr = {buffer = 0x55ddb25b9418, element_size = 104}, v =
0x55ddb25b9418, v_modifiable = 0x55ddb25b9418}
opts = {arr = {buffer = , element_size = 32}, v =
, v_modifiable = }
pargc = 4
c = -1
---Type to continue, or q to quit---
li = -252221570
pool = 0x55ddb25b9248
optbuf = 0x55ddb25b9260
__func__ = "doveadm_cmd_run_ver2"
#9 0x55ddb0e24020 in doveadm_cmd_server_run_ver2 (cctx=0x77c52670,
argv=0x55ddb25b9158, argc=1, conn=0x55ddb260dbf8) at client-connection-tcp.c:178
No locals.
#10 doveadm_cmd_handle (cctx=0x77c52670, argv=0x55ddb25b9158, argc=1,
cmd_name=, conn=0x55ddb260dbf8) at client-connection-tcp.c:342
mail_cmd =
mctx =
cmd_ver2 =
prev_ioloop = 0x55ddb25c1cc0
cmd = 0x0
#11 client_handle_command (args=, conn=0x55ddb260dbf8) at
client-connection-tcp.c:415
cctx = {cmd = 0x55ddb25d73e8, argc = 4, argv = 0x55ddb25b9450, username
= 0x55ddb25b9119
"testcli...@newsvilpec.babel.it",
local_ip = {family = 2, u = {ip6 = {__in6_u = {
__u6_addr8 = "\300\240\n\003", '\000' ,
__u6_addr16 = {41152, 778, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {51028160, 0, 0,
0}}}, ip4 = {s_addr = 51028160}}}, remote_ip = {family = 2, u = {
ip6 = {__in6_u = {__u6_addr8 = "\n\000\b\200", '\000' , __u6_addr16 = {10, 32776, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {2148007946,
0, 0, 0}}}, ip4 = {s_addr = 2148007946}}},
local_port = 924, remote_port = 41491, conn_type =
DOVEADM_CONNECTION_TYPE_TCP, input = 0x55ddb25d2dc0, output = 0x55ddb25d8d00}
flags =
cmd_name =
argc =
#12 client_connection_tcp_input (conn=0x55ddb260dbf8) at
client-connection-tcp.c:561
args =
_data_stack_cur_id = 3
line =
ok = true
minor = 0
#13 0x7f7dc973155f in io_loop_call_io (io=0x55ddb25e7b20) at ioloop.c:704
ioloop = 0x55ddb25c1cc0
t_id = 2
__func__ = "io_loop_call_io"
#14 0x7f7dc9732fa3 in io_loop_handler_run_internal
(ioloop=ioloop@entry=0x55ddb25c1cc0) at ioloop-epoll.c:221
ctx = 0x55ddb25c77b0
events =
list = 0x55ddb260be90
io =
tv = {tv_sec = 2147483, tv_usec = 0}
events_count =
msecs =
ret = 1
i = 0
---Type to continue, or q to quit---
call =
__func__ = "io_loop_handler_run_internal"
#15 0x7f7dc9731666 in io_loop_handler_run
(ioloop=ioloop@entry=0x55ddb25c1cc0) at ioloop.c:756
__func__ = "io_loop_handler_run"
#16 0x7f7dc9731888 in io_loop_run (ioloop=0x55ddb25c1cc0) at ioloop.c:729
__func__ = "io_loop_run"
#17 0x7f7dc96a42d3 in master_service_run (service=0x55ddb25c1b50,
callback=callback@entry=0x55ddb0e27260 ) at
master-service.c:781
No locals.
#18 0x55ddb0dfd421 in main (argc=1, argv=0x55ddb25c18
Re: Dovecot 2.3.7.2 lucene segfault and coredump
Op 16-9-2019 om 11:53 schreef Domenico Pastore via dovecot:
Hi,
I have other information.
I analyzed the core dump:
(gdb) core 22534
[New LWP 22534]
Reading symbols from /usr/libexec/dovecot/doveadm-server...Reading
symbols from
/usr/lib/debug/usr/libexec/dovecot/doveadm-server.debug...done.
done.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `dovecot-devel01/doveadm-server'.
Program terminated with signal 11, Segmentation fault.
#0 clear (this=0x0) at
/usr/src/debug/clucene-core-2.3.3.4/src/core/CLucene/util/VoidMap.h:123
123 if ( dk || dv ){
(gdb)
Can you issue GDB command `bt full` at this point?
Regards,
Stephan.
Br,
Domenico
*Domenico Pastore*
Senior Cloud Engineer
*T* 06.98269600 | *M* 347.1474270 | *F* 06.98269680
*Par-Tec * | *beyond the IT domain*
Via Cristoforo Colombo 163, 00147 Roma
*CONFIDENZIALE*: Questo messaggio ed i suoi allegati sono di carattere
confidenziale. È vietato l'inoltro non autorizzato a destinatari
diversi da quelli indicati nel messaggio originale. Se ricevuto per
errore si prega di informare il mittente e cancellarlo immediatamente.
Il 16/09/19 09:50, Domenico Pastore via dovecot ha scritto:
Hi,
do you have the same problem with lucene?
I collected a strace on the dovecot process during indexing:
[pid 31339] execve("/usr/libexec/dovecot/doveadm-server",
["dovecot-devel01/doveadm-server"], [/* 18 vars */]
[pid 30711] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED,
si_pid=30932, si_uid=0, si_status=SIGSEGV, si_utime=3, si_stime=1} ---
[pid 30711] write(62, "\0", 1) = 1
[pid 30711] read(124, "8x\0\0008\0\0\0\251\3\0\0", 1020) = 12
[pid 30711] read(61, "\0", 64) = 1
[pid 30711] open("/proc/sys/fs/suid_dumpable", O_RDONLY) = 227
[pid 30711] read(227, "0\n", 9) = 2
[pid 30711] write(65, "25 30932 FATAL service(doveadm): child 30932
killed with signal 11 (core not dumped -
https://dovecot.org/bugreport.html#coredumps - set
/proc/sys/fs/suid_dumpable to 2)\n", 170) = 170
[pid 30711] write(14, "KILL\t30932\n", 11) = 11
[pid 30711] write(65, "25 30932 BYE\n", 13) = 13
[pid 31339] <... execve resumed> ) = 0
[pid 31339] open("/usr/lib64/dovecot/tls/x86_64/libz.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot/tls/x86_64", 0x7ffda7e3f1d0) =
-1 ENOENT (No such file or directory)
[pid 31339] open("/usr/lib64/dovecot/tls/libz.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot/tls", 0x7ffda7e3f1d0) = -1
ENOENT (No such file or directory)
[pid 31339] open("/usr/lib64/dovecot/x86_64/libz.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot/x86_64", 0x7ffda7e3f1d0) = -1
ENOENT (No such file or directory)
[pid 31339] open("/usr/lib64/dovecot/libz.so.1", O_RDONLY|O_CLOEXEC)
= -1 ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
[pid 31339] open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 4
[pid 31339] open("/lib64/libz.so.1", O_RDONLY|O_CLOEXEC) = 4
All missing libs are in "/usr/lib64" and no to "/usr/lib64/dovecot"
Can you help me?
Br,
Domenico
*Domenico Pastore*
Senior Cloud Engineer
*T* 06.98269600 | *M* 347.1474270 | *F* 06.98269680
*Par-Tec * | *beyond the IT domain*
Via Cristoforo Colombo 163, 00147 Roma
*CONFIDENZIALE*: Questo messaggio ed i suoi allegati sono di
carattere confidenziale. È vietato l'inoltro non autorizzato a
destinatari diversi da quelli indicati nel messaggio originale. Se
ricevuto per errore si prega di informare il mittente e cancellarlo
immediatamente.
Il 12/09/19 12:07, Domenico Pastore via dovecot ha scritto:
Hi,
i have a problem with libclucene-core.so.2.3.3.4.
I See segfault error to messages log, when dovecot store mail to INBOX.
set 12 13:41:21 box02.par-tec.it kernel: doveadm-server[20285]:
*segfault at 38 ip 7f575b68fc42 sp 7ffc0272e750 error 4 in
libclucene-core.so.2.3.3.4*[7f575b569000+188000]
set 12 13:41:22 box02.par-tec.it kernel: doveadm-server[18871]:
segfault at 38 ip 7f9bea6d2c42 sp 7fff47bceae0 error 4 in
libclucene-core.so.2.3.3.4[7f9bea5ac000+188000]
In the dovecot logs:
2019-09-12 13:45:09 auth: Debug:
ldap(testclient@newsvil,10.0.8.128): Finished userdb lookup
2019-09-12 13:45:09 auth: Debug: userdb out: USER 1
testclient@newsvil
home=/pec_store/pec_mailbox/pec_mailbox_devel01/4/5/6/7/1/45671_18231
quota_rule=*:bytes=1048576000 mail_plugins+=
2019-09-12 13:45:10 SKENO8Uvel0gbAAA5ZKy4w
doveadm(testclient@newsvil): *Fatal: master:
service(doveadm): child 27680 killed with signal 11 (core dumped)*
2019-09-12 13:45:10 auth: Debug: master in: USER 1
testclient@newsvil service=doveadm lip=192.160.10.3
lport=924
Re: Repo for Debian-Buster
We are working on this and hopefully it will be available with next release. Aki On 16/09/2019 17:52 Philip Iezzi via dovecot < dovecot@dovecot.org> wrote: Hi there, Any news about Debian Buster packages in Dovecot community repos? We would greatly appreciate! Soon going live with two rather big Dovecot servers and would prefer upgrading them to Buster before. I will definitely bow my head and look for some donation button! Thanks, Philip On 2 Sep 2019, at 14:43, slater.ch via dovecot < dovecot@dovecot.org> wrote: Hi, is there already a release date for Debian Buster packages? kind regards Christian --- Aki Tuomi
Re: Repo for Debian-Buster
Hi there, Any news about Debian Buster packages in Dovecot community repos? We would greatly appreciate! Soon going live with two rather big Dovecot servers and would prefer upgrading them to Buster before. I will definitely bow my head and look for some donation button! Thanks, Philip > On 2 Sep 2019, at 14:43, slater.ch via dovecot wrote: > > Hi, > > is there already a release date for Debian Buster packages? > > kind regards > > Christian
Re: corrupted mdbox
Hello list, is it save to move the broken m.* files and let dovecot replicate them again? dsync(): Error: zlib.read(/var/spool/mail//storage/m.370): corrupted data at 1486926 dsync(): Error: Mailbox Trash: copy: i_stream_read(zlib(/var/spool/mail//storage/m.370)) failed: read(/var/spool/mail//storage/m.370) failed: zlib.read(/var/spool/mail//storage/m.370): corrupted data at 1486926 dsync(): Error: Mailbox Trash: Saving mail: read(zlib(/var/spool/mail//storage/m.370)) failed: read(/var/spool/mail//storage/m.370) failed: zlib.read(/var/spool/mail//storage/m.370): corrupted data at 1486926 (read reason=) dsync(): Warning: Failed to copy source UID=3239 mail: Mailbox Trash: Saving mail: read(zlib(/var/spool/mail//storage/m.370)) failed: read(/var/spool/mail//storage/m.370) failed: zlib.read(/var/spool/mail//storage/m.370): corrupted data at 1486926 (read reason=) - falling back to regular saving dsync(): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xd4e1e) [0x7ff37f268e1e] -> /usr/lib/dovecot/libdovecot.so.0(+0xd4e61) [0x7ff37f268e61] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff37f1d1824] -> /usr/lib/dovecot/libdovecot-storage.so.0(dbox_file_read_mail_header+0x166) [0x7ff37f589a06] -> /usr/lib/dovecot/libdovecot-storage.so.0(dbox_file_seek+0x43) [0x7ff37f589a73] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_map_append_next+0x7e9) [0x7ff37f57d2c9] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_save_begin+0x59) [0x7ff37f57f6e9] -> /usr/lib/dovecot/modules/lib20_zlib_plugin.so(+0x34b1) [0x7ff37db684b1] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_begin+0x8e) [0x7ff37f565d0e] -> doveadm(+0x4b9ff) [0x5563102199ff] -> doveadm(dsync_mailbox_import_mail+0xd8) [0x55631021ce98] -> doveadm(dsync_brain_sync_mails+0xb2) [0x556310216ad2] -> doveadm(dsync_brain_run+0x5c8) [0x5563102127b8] -> doveadm(+0x29bae) [0x5563101f7bae] -> doveadm(+0x2be2 dsync(): Error: Mailbox Archives: copy: i_stream_read(zlib(/var/spool/mail//storage/m.11677)) failed: read(/var/spool/mail//storage/m.11677) failed: lzma.read(/var/spool/mail//storage/m.11677): corrupted data at 6429691 dsync(): Error: Mailbox Archives: Saving mail: read(zlib(/var/spool/mail//storage/m.11677)) failed: read(/var/spool/mail//storage/m.11677) failed: lzma.read(/var/spool/mail//storage/m.11677): corrupted data at 6429691 (read reason=) dsync(): Warning: Failed to copy source UID=1135314 mail: Mailbox Archives: Saving mail: read(zlib(/var/spool/mail//storage/m.11677)) failed: read(/var/spool/mail//storage/m.11677) failed: lzma.read(/var/spool/mail//storage/m.11677): corrupted data at 6429691 (read reason=) - falling back to regular saving dsync(): Error: Mailbox Archives: Saving mail: read(zlib(/var/spool/mail//storage/m.11677)) failed: read(/var/spool/mail//storage/m.11677) failed: lzma.read(/var/spool/mail//storage/m.11677): corrupted data at 6429691 (read reason=) On 06.09.19 19:11, sch tel wrote: Hello list, i run into another problem. It seems there are some null bytes in the middle of an compressed mdbox, if i look into it with hexdump after run doveadm dump. With mdbox-recover.pl i could recover ~2k messages. What should i do to recover this broken mdbox file and dsync can finish? Sep 06 18:47:28 doveadm: Error: zlib.read(/var/spool/mail//storage/m.770): unexpected EOF at 7947710 Sep 06 18:47:28 doveadm: Error: dsync(server1): read(zlib(/var/spool/mail//storage/m.770)) failed: read(/var/spool/mail//storage/m.770) failed: zlib.read(/var/spool/mail//storage/m.770): unexpected EOF at 7947710 (last sent=mail, last recv=mail_request (EOL)) Sep 06 18:47:29 dsync-local()<+mJrOaCNcl2eZwAA0H466A>: Error: zlib.read(/var/spool/mail//storage/m.770): unexpected EOF at 7947710 Sep 06 18:47:29 dsync-local()<+mJrOaCNcl2eZwAA0H466A>: Error: dsync(server1): read(zlib(/var/spool/mail//storage/m.770)) failed: read(/var/spool/mail//storage/m.770) failed: zlib.read(/var/spool/mail//storage/m.770): unexpected EOF at 7947710 (last sent=mail, last recv=mail_request (EOL))
Re: Dovecot 2.3.7.2 lucene segfault and coredump
Hi,
I have other information.
I analyzed the core dump:
(gdb) core 22534
[New LWP 22534]
Reading symbols from /usr/libexec/dovecot/doveadm-server...Reading symbols from
/usr/lib/debug/usr/libexec/dovecot/doveadm-server.debug...done.
done.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `dovecot-devel01/doveadm-server'.
Program terminated with signal 11, Segmentation fault.
#0 clear (this=0x0) at
/usr/src/debug/clucene-core-2.3.3.4/src/core/CLucene/util/VoidMap.h:123
123if ( dk || dv ){
(gdb)
Br,
Domenico
Domenico Pastore
Senior Cloud Engineer
T 06.98269600 | M 347.1474270 | F 06.98269680
Par-Tec | beyond the IT domain
Via Cristoforo Colombo 163, 00147 Roma
CONFIDENZIALE: Questo messaggio ed i suoi allegati sono di carattere
confidenziale. È vietato l'inoltro non autorizzato a destinatari diversi da
quelli indicati nel messaggio originale. Se ricevuto per errore si prega di
informare il mittente e cancellarlo immediatamente.
Il 16/09/19 09:50, Domenico Pastore via dovecot ha scritto:
Hi,
do you have the same problem with lucene?
I collected a strace on the dovecot process during indexing:
[pid 31339] execve("/usr/libexec/dovecot/doveadm-server",
["dovecot-devel01/doveadm-server"], [/* 18 vars */]
[pid 30711] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=30932,
si_uid=0, si_status=SIGSEGV, si_utime=3, si_stime=1} ---
[pid 30711] write(62, "\0", 1) = 1
[pid 30711] read(124, "8x\0\0008\0\0\0\251\3\0\0", 1020) = 12
[pid 30711] read(61, "\0", 64) = 1
[pid 30711] open("/proc/sys/fs/suid_dumpable", O_RDONLY) = 227
[pid 30711] read(227, "0\n", 9) = 2
[pid 30711] write(65, "25 30932 FATAL service(doveadm): child 30932 killed with
signal 11 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set
/proc/sys/fs/suid_dumpable to 2)\n", 170) = 170
[pid 30711] write(14, "KILL\t30932\n", 11) = 11
[pid 30711] write(65, "25 30932 BYE\n", 13) = 13
[pid 31339] <... execve resumed> ) = 0
[pid 31339] open("/usr/lib64/dovecot/tls/x86_64/libz.so.1", O_RDONLY|O_CLOEXEC)
= -1 ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot/tls/x86_64", 0x7ffda7e3f1d0) = -1 ENOENT
(No such file or directory)
[pid 31339] open("/usr/lib64/dovecot/tls/libz.so.1", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot/tls", 0x7ffda7e3f1d0) = -1 ENOENT (No such
file or directory)
[pid 31339] open("/usr/lib64/dovecot/x86_64/libz.so.1", O_RDONLY|O_CLOEXEC) =
-1 ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot/x86_64", 0x7ffda7e3f1d0) = -1 ENOENT (No
such file or directory)
[pid 31339] open("/usr/lib64/dovecot/libz.so.1", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot", {st_mode=S_IFDIR|0755, st_size=4096,
...}) = 0
[pid 31339] open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 4
[pid 31339] open("/lib64/libz.so.1", O_RDONLY|O_CLOEXEC) = 4
All missing libs are in "/usr/lib64" and no to "/usr/lib64/dovecot"
Can you help me?
Br,
Domenico
Domenico Pastore
Senior Cloud Engineer
T 06.98269600 | M 347.1474270 | F 06.98269680
Par-Tec | beyond the IT domain
Via Cristoforo Colombo 163, 00147 Roma
CONFIDENZIALE: Questo messaggio ed i suoi allegati sono di carattere
confidenziale. È vietato l'inoltro non autorizzato a destinatari diversi da
quelli indicati nel messaggio originale. Se ricevuto per errore si prega di
informare il mittente e cancellarlo immediatamente.
Il 12/09/19 12:07, Domenico Pastore via dovecot ha scritto:
Hi,
i have a problem with libclucene-core.so.2.3.3.4.
I See segfault error to messages log, when dovecot store mail to INBOX.
set 12 13:41:21 box02.par-tec.it kernel: doveadm-server[20285]: segfault at 38
ip 7f575b68fc42 sp 7ffc0272e750 error 4 in
libclucene-core.so.2.3.3.4[7f575b569000+188000]
set 12 13:41:22 box02.par-tec.it kernel: doveadm-server[18871]: segfault at 38
ip 7f9bea6d2c42 sp 7fff47bceae0 error 4 in
libclucene-core.so.2.3.3.4[7f9bea5ac000+188000]
In the dovecot logs:
2019-09-12 13:45:09 auth: Debug:
ldap(testclient@newsvil,10.0.8.128):
Finished userdb lookup
2019-09-12 13:45:09 auth: Debug: userdb out: USER1
testclient@newsvil
home=/pec_store/pec_mailbox/pec_mailbox_devel01/4/5/6/7/1/45671_18231
quota_rule=*:bytes=1048576000mail_plugins+=
2019-09-12 13:45:10 SKENO8Uvel0gbAAA5ZKy4w
doveadm(testclient@newsvil): Fatal: master: service(doveadm): child
27680 killed with signal 11 (core dumped)
2019-09-12 13:45:10 auth: Debug: master in: USER1
testclient@newsvilservice=doveadmlip=192.160.10.3lport=924
rip=10.0.8.128rport=36760
2019-09-12 13:45:10 auth: Debug: ldap(testclient@newsvil 10.0.8.128):
Performing userdb lo
Re: Dovecot 2.3.7.2 lucene segfault and coredump
Hi,
do you have the same problem with lucene?
I collected a strace on the dovecot process during indexing:
[pid 31339] execve("/usr/libexec/dovecot/doveadm-server",
["dovecot-devel01/doveadm-server"], [/* 18 vars */]
[pid 30711] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=30932,
si_uid=0, si_status=SIGSEGV, si_utime=3, si_stime=1} ---
[pid 30711] write(62, "\0", 1) = 1
[pid 30711] read(124, "8x\0\0008\0\0\0\251\3\0\0", 1020) = 12
[pid 30711] read(61, "\0", 64) = 1
[pid 30711] open("/proc/sys/fs/suid_dumpable", O_RDONLY) = 227
[pid 30711] read(227, "0\n", 9) = 2
[pid 30711] write(65, "25 30932 FATAL service(doveadm): child 30932 killed with
signal 11 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set
/proc/sys/fs/suid_dumpable to 2)\n", 170) = 170
[pid 30711] write(14, "KILL\t30932\n", 11) = 11
[pid 30711] write(65, "25 30932 BYE\n", 13) = 13
[pid 31339] <... execve resumed> ) = 0
[pid 31339] open("/usr/lib64/dovecot/tls/x86_64/libz.so.1", O_RDONLY|O_CLOEXEC)
= -1 ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot/tls/x86_64", 0x7ffda7e3f1d0) = -1 ENOENT
(No such file or directory)
[pid 31339] open("/usr/lib64/dovecot/tls/libz.so.1", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot/tls", 0x7ffda7e3f1d0) = -1 ENOENT (No such
file or directory)
[pid 31339] open("/usr/lib64/dovecot/x86_64/libz.so.1", O_RDONLY|O_CLOEXEC) =
-1 ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot/x86_64", 0x7ffda7e3f1d0) = -1 ENOENT (No
such file or directory)
[pid 31339] open("/usr/lib64/dovecot/libz.so.1", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
[pid 31339] stat("/usr/lib64/dovecot", {st_mode=S_IFDIR|0755, st_size=4096,
...}) = 0
[pid 31339] open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 4
[pid 31339] open("/lib64/libz.so.1", O_RDONLY|O_CLOEXEC) = 4
All missing libs are in "/usr/lib64" and no to "/usr/lib64/dovecot"
Can you help me?
Br,
Domenico
Domenico Pastore
Senior Cloud Engineer
T 06.98269600 | M 347.1474270 | F 06.98269680
Par-Tec | beyond the IT domain
Via Cristoforo Colombo 163, 00147 Roma
CONFIDENZIALE: Questo messaggio ed i suoi allegati sono di carattere
confidenziale. È vietato l'inoltro non autorizzato a destinatari diversi da
quelli indicati nel messaggio originale. Se ricevuto per errore si prega di
informare il mittente e cancellarlo immediatamente.
Il 12/09/19 12:07, Domenico Pastore via dovecot ha scritto:
Hi,
i have a problem with libclucene-core.so.2.3.3.4.
I See segfault error to messages log, when dovecot store mail to INBOX.
set 12 13:41:21 box02.par-tec.it kernel: doveadm-server[20285]: segfault at 38
ip 7f575b68fc42 sp 7ffc0272e750 error 4 in
libclucene-core.so.2.3.3.4[7f575b569000+188000]
set 12 13:41:22 box02.par-tec.it kernel: doveadm-server[18871]: segfault at 38
ip 7f9bea6d2c42 sp 7fff47bceae0 error 4 in
libclucene-core.so.2.3.3.4[7f9bea5ac000+188000]
In the dovecot logs:
2019-09-12 13:45:09 auth: Debug:
ldap(testclient@newsvil,10.0.8.128):
Finished userdb lookup
2019-09-12 13:45:09 auth: Debug: userdb out: USER1
testclient@newsvil
home=/pec_store/pec_mailbox/pec_mailbox_devel01/4/5/6/7/1/45671_18231
quota_rule=*:bytes=1048576000mail_plugins+=
2019-09-12 13:45:10 SKENO8Uvel0gbAAA5ZKy4w
doveadm(testclient@newsvil): Fatal: master: service(doveadm): child
27680 killed with signal 11 (core dumped)
2019-09-12 13:45:10 auth: Debug: master in: USER1
testclient@newsvilservice=doveadmlip=192.160.10.3lport=924
rip=10.0.8.128rport=36760
2019-09-12 13:45:10 auth: Debug: ldap(testclient@newsvil 10.0.8.128):
Performing userdb lookup
I have attach the coredump of error and dovecot.conf
Thanks for support.
Br,
Domenico
--- info: ---
# 2.3.7.2 (3c910f64b): /pec/config/dovecot/dovecot-devel01/dovecot.conf
# Pigeonhole version 0.5.7.2 (7372921a)
# OS: Linux 3.10.0-957.27.2.el7.x86_64 x86_64 CentOS Linux release 7.6.1810
(Core)
# Hostname: box02
Re: fts_solr: Error: fts_solr: received invalid uid '0'
On 9/13/2019 1:21 AM, Fabian via dovecot wrote: Hi, we are trying to add full text search functionality with Solr to our Doveoct setup. Our Versions: OS: Debian 9 Tried versions: - Dovecot 2.2.7 with Solr 3.6 - Dovecot 2.3.4 with Solr 8.2 (2.2.7 from offical Debian repository, 2.3.4 from backports) Search is working mostly of the time perfrectly smooth. But sometimes following message appears in mail.err: dovecot: imap(username)<16189>: Error: fts_solr: received invalid uid '0' If this error occurs our webmail frontend delivers most of the time a timeout. Sometimes the search only takes really long. Are there any ideas why this error occurs? We are not able to reproduce the error in such a way that it would always be reproducible. However, we can reproduce the behavior in some form over and over again - but we do not know exactly what is decisive. Are you limiting Solr's memory usage? How much available memory is on your server? To shortcut the conversation - if you don't have at least 16G of *free* RAM it's time to upgrade. My own server has 32G installed - I used to have 16G. My own Solr problems basically disappeared after adding RAM. And I only serve a few users - my own mailstore is the largest as I keep most of my mails. If you're serving 20+ users you'd probably benefit from doubling to at least 64G. -- Daniel
