similar to: Lucene and Zlib with 2.2.1

Displaying 20 results from an estimated 6000 matches similar to: "Lucene and Zlib with 2.2.1"

2014 Jul 01
1
indexer failure: lucene: while doing doveadm commands
I have the following script: #!/bin/sh PATH=$PATH:/usr/local/bin #Expects to be run after midnight on the first of the month # to archive all the previous months mail #Date Run: TODAY=`date "+%Y-%m-%d"` #last month in YYYY/MM YEAR_LAST_MONTH=`date -v-1d "+%Y/%m"` #1st of last month as 01-Mon-YYYY FIRST_LAST_MONTH=`date -v-1d "+01-%b-%Y"` echo 'TODAY='
2020 May 19
5
FTS-lucene errors : language not available for stemming
I'm getting some log errors with clucene that I am having no luck tracking down on the interwebs. Errors: May 19 05:05:16 indexer-worker(gessel at blackrosetech.com)<62971><aPAEI3zLw17A/QAA0J78UA:EF25M3zLw1779QAA0J78UA>: Error: lucene index /mail/blackrosetech.com/gessel//lucene-indexes: IndexWriter::addDocument() failed (#4): language not available for stemming May 19 05:05:16
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
2016 Apr 12
2
fts-lucene with virtual folders
Hi, It looks like I've found something strange. It looks like dovecot updates fts-lucene index every time I'm opening virtual folder that contains FTS query: indexer-worker(dion): Warning: fts-lucene: Settings have changed, rebuilding index for mailbox dovecot-virtual is pretty simple: archive/INBOX BODY "test" first of all, I'm trying to perform FTS in archive/INBOX
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 May 29
4
fts lucene crashes in 2.2.24
Hi, I've just enabled FTS via Lucene on my Dovecot 2.2.24 installation but I see the indexer crashing ?always?. This simple testcase with a very tiny testing mailbox exposes the issue immediately: doveadm -v index -u anmesse INBOX Program received signal SIGSEGV, Segmentation fault. rescan_clear_unseen_mailbox (rescan_ctx=rescan_ctx at entry=0x0, vname=0x555555839820 "INBOX.Testfolder
2016 Nov 01
4
doveadm index: can't index a different namespace?
doveadm -D -vvvvvv index \#ARCHIVE/\* garners the below for ALL mailboxes in the namespace: doveadm(ler): Error: Mailbox #ARCHIVE/2013/04/clamav-rules: Status lookup failed: Internal error occurred. Refer to server log for more information. [2016-11-01 13:25:21] doveadm(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable doveadm(ler): Error: Mailbox
2018 Dec 19
2
Fatal: master: service(indexer-worker): child 493 killed with signal 11 (core dumped)
Dear list, We been having some issues where the indexer-worker is crashing. This happens on production servers which are handling a slight amount of mail, but is also reproducible by moving messages. Also, users on my server are complaining about "Trashed" items coming back etc. Some details: - Dovecot 2.3.2.1 in alpine:3.8 based Docker container. As part of the Mailu distribution.
2012 Feb 06
2
Possible broken indexer(lucene/solr)?
Hello, try to use the new 2.1rc and don't get any data in the searchindex. Tried first lucene, and switched than back so solr. If I do an search in an mailfolder, i get in the dovecot-log 2012-02-06 22:17:11 | dovecot: | indexer-worker(xxxxxx): Indexed 0 messages in INBOX/dovecot Log from solr. Feb 6, 2012 10:17:11 PM org.apache.solr.core.SolrCore execute INFO: []
2014 Nov 04
1
doveadm index message-decoder assertion failed
Hi, I've setup FTS using lucene and it should be working, the lucene index is updated when mail arrives. I also managed to reindex my INBOX: doveadm index -u foo -q INBOX However, when I try to index an Archives folder: doveadm index -u foo -q Archives, the index-work crashed with this log message: dovecot: indexer-worker(foo): Panic: file message-decoder.c: line 363
2014 Apr 22
0
FTS Lucene: Fatal: master: service(indexer-worker): child * killed with signal 6
Hi List, Since we migrated from dovecot 1.2.4 to 2.2.12 with lucene as FTS engine, I have this in my error log: Apr 22 14:01:14 indexer-worker(username): Error: lucene index /var/vmail/username/lucene-indexes: IndexWriter() failed (#1): Lock obtain timed out Apr 22 14:01:14 indexer-worker: Error: indexer-worker [username at mydomain.com MailBox-1 - 20800/22707]:
2018 Dec 19
2
Fatal: master: service(indexer-worker): child 493 killed with signal 11 (core dumped)
Hope this helps. There are no debugging symbols available for dovecot in the alpine repository. (gdb) bt full #0? a_crash () at ./arch/x86_64/atomic_arch.h:108 No locals. #1? free (p=0x55d949250660) at src/malloc/malloc.c:467 ??????? extra = 65 ??????? base = 0x55d94925060f "" ??????? len = 94391723427649 ??????? self = 0x55d949250650 ??????? next = <optimized out> ???????
2012 Oct 15
1
[BUG] Lucene plugin breaks header substring search
According to the IMAP spec if I do a search for "TO isocpp.org" it should find all the messages whose To: field contains the string "isocpp.org", but dovecot is returning me an empty list. However, a search for "TO tm at isocpp.org" produces a long list of messages. This behavior is present if I *even load* the lucene fts plugin. Note that lucene isn't in use
2014 May 09
1
fts_lucene - hiding lucene-indexes folder?
Hi, Is there any way to hide this folder from IMAP clients? I can see it is not runtime configurable and just #defined as LUCENE_INDEX_DIR_NAME in fts-backend-lucene.c. -- Nicholas Riley <njriley at illinois.edu>
2014 Apr 15
1
Segmentation fault running doveadm index (lucene) on a big mailbox
Hi, on a server running dovecot 2.2.12 I have a user with a quite big mailbox (~37000 Mails in the INBOX). I tried to enable full text search using the fts_lucene backend (dovecot 2.2.12). However, the `doveadm -v index -u <username> INBOX` always runs into a segmentation fault after mail number 24200: I tried to get a backtrace using gdb: doveadm(<username>): Info: INBOX:
2007 Apr 26
1
lucene plug-in
Hello, Has anyone tried the lucene plug-in? I am interested to know more about this feature , how to setup / configure it? regards, - Joe
2011 Sep 11
3
2.1: problems compiling fts-lucene - CLucene git version necessary?
Hello! I have problems recompiling the Debian squeeze auto build packages with "--with-lecene". Is the git (2.3) version of CLucene necessary? Debian includes 0.9.21b, which does not work. Lutz
2018 Feb 05
1
Bug in dovecot 2.3 virtual plugin
Hi, did you have time to investigate about 'Panic: file unichar.c' bug ? Because I have the same problem with a 2.3.0 installation without virtual plugin. Thanks, Marco On 2018-01-03 16:52, Aki Tuomi wrote: > This is not a bug in virtual plugin, but in some email which contains invalid unicode sequence somehow. Can you send me a core file? This should not have occured ofc but
2018 Jan 03
4
Bug in dovecot 2.3 virtual plugin
Hi there! I compiled dovecot 2.3 from git. Because there is already a bug in virtual-plugin, and i hoped, it get fixed... but it doesn't. So this is the error-message from the log J?n 03 16:27:08 aldebaran dovecot[26460]: indexer-worker(jakob)<26476><qQ6g1+BhIJvAqAAO:sjYhMTH2TFpsZwAAk1Mx3g>: Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion failed:
2012 Dec 05
1
Error: unlink_directory(.../lucene-indexes) with doveadm index
Hi, Per discussion on this previous thread: http://dovecot.org/pipermail/dovecot/2012-October/068849.html I am updating search indexes on all my mailboxes via a nightly cronjob that runs: doveadm index -A '*' The problem we're running into is that random mailboxes will throw the following error during the update (sanitized to conceal actual domain name): doveadm(user at