similar to: Dovecot v2.3.18 released

given existing problems with fts_solr = ... use_libfts ... i've rm'd it from dovecot config, and am moving all tokenization to solr config. iiuc, in dovecot + solr context, that's correctly config'd in solr/data/dovecot/conf/schema.xml dovecot release ships with 'starter configs', cp -af /usr/share/doc/dovecot/solr-config-7.7.0.xml

sending to the list as well On 02/11/2020 17:40, PGNet Dev wrote: > On 11/1/20 10:35 AM, John Fawcett wrote: >> Yes, getting more data about any potential problem would be useful. >> >> Just to clarify: I have a fully working search setup for some time now >> over various dovecot releases, so no patches needed to get it working. >> >> My setup does use fts

On 11/1/20 10:35 AM, John Fawcett wrote: > Yes, getting more data about any potential problem would be useful. > > Just to clarify: I have a fully working search setup for some time now > over various dovecot releases, so no patches needed to get it working. > > My setup does use fts plugin and fts-solr plugin, but it does not use > lib-fts functionality (that has many

Difficult to figure out without a coredump + gdb I have also battled quite a lot to make sure dovecot can core dump on my Archlinux servers. I remember that the key point was putting FS.SUID_DUMPABLE=2 in /etc/sysctl.d/ conf files, LIMITCORE=INFINITY in /etc/systemd/system/multi-user.target.wants/dovecot.service, and rebooting the server. My own coredumps are on /var/lib/systemd/coredump/

Hello. We're setting up fts solr and want to have the solr server host be set per-user via UserDB. It looks like if a user connects and fts indexes mail, and then another user connects and indexes mail, indexer-worker is connecting to the first user's fts host: User1, hammer at rp-auth-test.com connects, does a SEARCH for the first time, indexer-worker gets UserDB settings and

The change of "Extern C" suggested by Timo actually solved the situation Now, further question : I put a "i_warning" at each of my functions, and I see in the log : Jan 12 10:33:27 indexer-worker(jom at grosjo.net)<30970><ms9zEnfCOVyHegAA0thIag:8IhwIHfCOVz6eAAA0thIag>: Warning: fts_backend_xapian_alloc Jan 12 10:33:27 indexer-worker(jom at

Not sure if I mentioned it but I'm on FreeBSD too. I wonder if any of the patches FreeBSD applies automatically is causing this. I looked through them but couldn't find anything obvious that might cause this --- configure.orig? ? ? 2020-08-12 12:20:51 UTC +++ configure @@ -28901,13 +28901,13 @@ fi ? ?if test $want_stemmer != no; then -? ? { $as_echo "$as_me:${as_lineno-$LINENO}:

Here it is: Jan 14 09:26:08 mail dovecot: indexer-worker(paul at iwascoding.com <mailto:paul at iwascoding.com>)<16777><IKpfOqBHPFyJQQAADYqDFA>: Debug: Effective uid=8, gid=8, home=/var/spool/mail/iwascoding/paul Jan 14 09:26:08 mail dovecot: indexer-worker(paul at iwascoding.com <mailto:paul at iwascoding.com>)<16777><IKpfOqBHPFyJQQAADYqDFA>: Debug: Quota

Can you send the log part that includes the "init" of the plugins (something similar as below) ? WHich version of Xapian are you on ? Jan 14 09:10:04 gjserver dovecot[31082]: indexer-worker(admin at grosjo.net)<14725><apZfHexRPFy9QAAA0thIag:UL+TNOxRPFyFOQAA0thIag>: FTS Xapian: Partial=2, Full=20 DB_PATH=/data/mail/grosjo.net/admin/xapian-indexes Jan 14 09:10:04 gjserver

On 10/05/2015 5:47 PM, Timo Sirainen wrote: >> How do I go about debugging this further? How do I go about >> getting a backtrace on what is essentially a child process that >> doesn't produce a core? (Note that my installation normally does >> produce cores when it crashes, so there's something different about >> these indexer processes..) > > One

On 11 Jan 2019, at 21.23, Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > > The below patch resolves the compilation error > > $ diff -p compat.h compat.h.joan > *** compat.h 2019-01-11 20:21:00.726625427 +0100 > --- compat.h.joan 2019-01-11 20:14:41.729109919 +0100 > *************** struct iovec; > *** 202,207 **** > --- 202,211 ---- > ssize_t

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

Hi, yesterday i tried to setup Dovecot with Solr (3.6.2) + Tika (1.8) for FTS. i used a fresh Debian 8.0 system in the beginning with Dovecot 2.2.13 from the Debian repository. After i got some issues with Tika/Dovecot and i read on the mailinglist that these problems where fixed in 2.2.14+, so i tried 2.2.18. With 2.2.18 i get panics with big (ok... huge) attachments. Most mailboxes (and their

On 13/11/2020 14:56, PGNet Dev wrote: > I've built a new dovecot + fts-solr instance; I've now picked up & am > running the recently released solr 8.7.0. > > In a test account, I've one message -- in the 'Drafts' folder. > > On exec of fts 'index' > > ????doveadm index -u testuser at example.com -q '*' > > I get a > >

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]:

Hello, I have some mailbox with error on index-worker process on dovecot 2.3.0 If I move the same mailbox to dovecot 2.2.33.2 this problem dos not happen. See below the backtrace: May 18 10:33:55 Error: imap(xxxxx)<249924><Xpj77npscpYKAQMQ>: indexer failed to index mailbox INBOX May 18 10:33:55 Fatal:

On 15/11/2020 18:10, John Fawcett wrote: > On 15/11/2020 15:49, PGNet Dev wrote: >> On 11/15/20 6:33 AM, John Fawcett wrote: >>> I've configured a tika server behind an apache proxy which enforces >>> basic auth, but sending basic auth credentials for a tika server is not >>> currently supported by Dovecot. >> i was _just_ setting up a tika instance

additionally, my logic is that the backend stores one databalse per mailox in /xapian-indexes (in the "root" dir of the user), the name od the database is the GUID of the mailbox For INBOX, that works perfectly, and database is properly createdm and backed starts indexing all emails For other folder, somehow, the process can not access that (root) folder. Am I missing something ?

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

The below patch resolves the compilation error $ DIFF -P COMPAT.H COMPAT.H.JOAN *** compat.h 2019-01-11 20:21:00.726625427 +0100 --- compat.h.joan 2019-01-11 20:14:41.729109919 +0100 *************** struct iovec; *** 202,207 **** --- 202,211 ---- ssize_t i_my_writev(int fd, const struct iovec *iov, int iov_len); #endif + #ifdef __cplusplus + extern "C" { + #endif + #if