similar to: Dovecot 2.3.7.2 lucene segfault and coredump

Displaying 20 results from an estimated 400 matches similar to: "Dovecot 2.3.7.2 lucene segfault and coredump"

2019 Sep 16
2
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
2019 Sep 16
1
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 0x00007f7dc5eabe96 in _lucene_shutdown () at
2019 Sep 16
0
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 */] <unfinished ...> [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} ---
2019 Sep 16
0
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
2019 Mar 31
2
CentOS Repository broken ?
Hello, Am Samstag, 30. M?rz 2019, 21:36:12 CEST schrieb Peter via dovecot: > On 30/03/19 10:56 PM, Gerald Galster via dovecot wrote: > > Maybe there is something wrong with his local yum/repo configuration. > > I'm tending to agree now. > > > CentOS 7 usually doesn't mix 32bit and 64bit packages anymore. > > > > Installiert: 2:dovecot-2.3.5-1.x86_64
2019 Mar 31
1
CentOS Repository broken ?
Hello, I download and install it manual, this working now? waiting for next update to found out, yum is working correct again ;-) Thanks for answers, Am Sonntag, 31. M?rz 2019, 13:59:17 CEST schrieb Kostya Vasilyev via dovecot: > On Sun, Mar 31, 2019, at 2:30 PM, G?nther J. Niederwimmer via dovecot wrote: > > Hello, > > > > Am Samstag, 30. M?rz 2019, 21:36:12 CEST schrieb
2019 Mar 30
1
CentOS Repository broken ?
Hello, All is correct on my system also a yum clean is make. But the dovecot = 2.3.5.1-1 is MISSING on the repositories !! Yum like to update to the new packages dovecot-lua and dovecot-imaptest but can't found the latest passed dovecot Version 2.3.5.1-1 The packages dovecot-lua and dovecot-imaptes 2.3.5.1-1 are found but not the dovecot version?? Am Freitag, 29. M?rz 2019, 14:49:29
2015 Oct 13
2
Indexing fails with .. FIELDS_INDEX_EXTENSION).c_str() )' failed
Hi, Mailing list archives suggest that this problem has been fixed in the older versions itself but I am getting the error still while trying to doveadm index a large folder of emails. Sometimes it throws error after 30000, something 40000, the latest it gave up after 111000. But it just never completes. 111000/322080doveadm:
2011 Dec 15
1
Building 2.1.rc1 with cluence, but without libstemmer
Hi, I'm testing out 2.1.rc1, building against clucene 2.3.3.4. Without libstemmber, the build fails because it attempts to include SnowballAnalyzer.h which is not part of "core" clucene. Simple patch below to make dovecot 2.1.rc1 build with clucene but without libstemmer (or textcat). Looking at libstemmer itself, there are multiple versions. The version in clucene is put into
2012 Feb 17
4
2.0.X -> 2.1 pitfalls?
Hi all, are there any pitfalls known for the migration from 2.0.18 to 2.1? Can I simply stop dovecot, make install and start again? --Frank Elsner
2016 Oct 24
2
keent() from Tika - with doveadm
Hi! We found some problems with those patches, and ended up doing slightly different fix: https://github.com/dovecot/core/compare/3e41b3d%5E...cca98b.patch Aki On 24.10.2016 10:17, Aki Tuomi wrote: > Hi! > > Can you try these two patches? > > Aki > > > On 24.10.2016 08:48, Aki Tuomi wrote: >> Ok so that timeval makes no sense. We'll look into it. >>
2016 Oct 24
2
keent() from Tika - with doveadm
Ok so that timeval makes no sense. We'll look into it. Aki > On October 24, 2016 at 12:22 AM Larry Rosenman <larryrtx at gmail.com> wrote: > > > doveadm(mrm): Debug: http-client: conn 127.0.0.1:9998 [1]: Got 200 response > for request [Req38: PUT http://localhost:9998/tika/] (took 296 ms + 8 ms in > queue) > doveadm(mrm): Panic: kevent(): Invalid argument >
2016 Oct 23
2
keent() from Tika - with doveadm
According to man page, the only way it can return EINVAL (22) is either bad filter, or bad timeout. I can't see how the filter would be bad, so I'm guessing ts must be bad. Unfortunately I forgot to ask for it, so I am going to have to ask you run it again and run p ts if that's valid, then the only thing that can be bad if the file descriptor 23. Aki > On October 23, 2016 at
2019 Mar 31
0
CentOS Repository broken ?
On Sun, Mar 31, 2019, at 2:30 PM, G?nther J. Niederwimmer via dovecot wrote: > Hello, > > Am Samstag, 30. M?rz 2019, 21:36:12 CEST schrieb Peter via dovecot: > > On 30/03/19 10:56 PM, Gerald Galster via dovecot wrote: > > > Maybe there is something wrong with his local yum/repo configuration. > > > > I'm tending to agree now. > > [ ... ] > >
2019 Oct 02
1
Doveadm error during store - segfault clucene
Hi, during the store of the messages, I find the following doveadm errors: 2019-10-02 09:22:19 auth: Debug: ldap(test.pop at test.xxx.it,10.11.47.60<mailto:test.pop at test.xxx.it,10.11.47.60>): result: mailMessageStore=1/1/2/0/8/7/2/1120872_91093 mailQuota=52428800; mailQuota,mailMessageStore unused 2019-10-02 09:22:19 auth: Debug: ldap(test.pop at
2014 Jul 24
1
FTS lucene indexer-worker segfaulting
Hi, I've just set up fts-lucene and when I run searches on my inbox or when I run the indexer (`doveadm index INBOX`) I get the following segfault. I've run it multiple times and noticed that the data value is different each time so I guess it doesn't always crash at the same point. I'm running dovecot 2.2.13-1 with clucene 2.3.3.4-8 on Arch Linux. If you need any more
2016 Oct 24
0
keent() from Tika - with doveadm
that seems to fix this kevent() problem, but I got the following lucene assert. Is that because of previous fails? Also, while I have your attention, is fts_autoindex supposed to work accross NAMESPACES? doveadm(mrm): Debug: Mailbox LISTS/vse-l: Opened mail UID=39483 because: fts indexing doveadm(mrm): Debug: Mailbox LISTS/vse-l: Opened mail UID=39484 because: fts indexing doveadm(mrm): Debug:
2015 Oct 13
0
Indexing fails with .. FIELDS_INDEX_EXTENSION).c_str() )' failed
On 13 Oct 2015, at 23:25, Akash <akbwiz+dovecot at gmail.com> wrote: > > Hi, > > Mailing list archives suggest that this problem has been fixed in the > older versions itself but I am getting the error still while trying to > doveadm index a large folder of emails. Sometimes it throws error > after 30000, something 40000, the latest it gave up after 111000. But > it
2014 May 30
0
doveadm fts optimize CRASH
thebighonker.lerctr.org /home/ler $ gdb -c doveadm.core `which doveadm` GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB.
2013 Apr 05
2
Problem with fts lucene, on solaris 10
Hi all, I'm planning to migrate my courier-imap imap server to dovecot, but I'm experiencing a strange issue with fts-lucene plugin. Basically, every time I start a search, the log starts to write: Apr 05 19:30:53 indexer: Error: Indexer worker disconnected, discarding 1 requests for XXXXXX Apr 05 19:30:53 indexer-worker(XXXXX): Fatal: master: service(indexer-worker): child 809 killed