similar to: Fatal: write(indexer) failed: Resource temporarily unavailable

> On 06/11/2020 13:37 Joan Moreau <jom at grosjo.net> wrote: > > > Hello > I have this issue for Xapian plugin: > https://github.com/grosjo/fts-xapian/issues/62 > > But I am not sure where can it comes from. > Is dovecot calling some specific function in the plugin after the init, that would create such error ? > In doveadm dealing differently with plugins

ok found it, However, it returns me some random number. Maybe I am missing something On 2020-11-06 13:57, Aki Tuomi wrote: > Duh... src/lib/restrict-process-size.h > > Should be in the installed include files as well, > > /usr/include/dovecot/restrict-process-size.h > > Aki > > On 06/11/2020 15:56 Joan Moreau <jom at grosjo.net> wrote: > > Hello >

Duh... src/lib/restrict-process-size.h Should be in the installed include files as well, /usr/include/dovecot/restrict-process-size.h Aki > On 06/11/2020 15:56 Joan Moreau <jom at grosjo.net> wrote: > > > Hello > I can't find "src/lib/restrict.h" . Is it in dovecot source ? > > > On 2020-11-06 13:20, Aki Tuomi wrote: > > Seems I had

Seems I had forgotten that you can use src/lib/restrict.h, in particular, restrict_get_process_size() to figure out the limit. You can combine this with getrusage to find out current usage. Aki > On 06/11/2020 13:26 Joan Moreau <jom at grosjo.net> wrote: > > > yes, will do so. > It would be nice however to be able to access the actual dovecot config from the plugin side

You could also add it as setting for the fts_xapian plugin parameters? Aki > On 04/11/2020 08:42 Joan Moreau <jom at grosjo.net> wrote: > > > For machines with low memory, I would like to detect how much ram remains available before starting indexing a mail, so I can commit everything on disk before the ram is exhausted (and break the process) > I tried to put a

yes, will do so. It would be nice however to be able to access the actual dovecot config from the plugin side On 2020-11-04 06:46, Aki Tuomi wrote: > You could also add it as setting for the fts_xapian plugin parameters? > > Aki > > On 04/11/2020 08:42 Joan Moreau <jom at grosjo.net> wrote: > > For machines with low memory, I would like to detect how much ram

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

Op 14-1-2019 om 13:40 schreef Aki Tuomi: > > Just to remind that now that there is a github repo for fts-xapian, > you could maybe open these issues there instead? > Although README.md currently says: "Please feel free to send your questions, together with the dovecot log file, to jom at grosjo.net <mailto:jom at grosjo.net> or to the dovecot ML dovecot at dovecot.org

Just to remind that now that there is a github repo for fts-xapian, you could maybe open these issues there instead? Aki On 14.1.2019 14.29, Odhiambo Washington wrote: > Testing a compile on FreeBSD. > > gmake[2]: Entering directory '/usr/home/wash/Tools/Dovecot/fts-xapian/src' > /bin/sh ../libtool? --tag=CXX? ?--mode=compile c++ -DHAVE_CONFIG_H -I. > -I..?

Please kindly check https://github.com/grosjo/fts-xapian On 2019-01-13 20:11, Aki Tuomi wrote: > If you had looked at what I sent, you'd seen it's quite different from what you sent. > > Anyways, put the contents of skeleton.tar.gz and > > ./src/plugins/fts-xapian/fts-xapian-plugin.h > ./src/plugins/fts-xapian/fts-backend-xapian.cpp >

If you had looked at what I sent, you'd seen it's quite different from what you sent. Anyways, put the contents of skeleton.tar.gz and ./src/plugins/fts-xapian/fts-xapian-plugin.h ./src/plugins/fts-xapian/fts-backend-xapian.cpp ./src/plugins/fts-xapian/Makefile.am ./src/plugins/fts-xapian/fts-backend-xapian-functions.cpp ./src/plugins/fts-xapian/fts-xapian-plugin.c into src/ directory

Testing a compile on FreeBSD. gmake[2]: Entering directory '/usr/home/wash/Tools/Dovecot/fts-xapian/src' /bin/sh ../libtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I.. -I/opt/dovecot2.3/include/dovecot -I/opt/dovecot2.3/include/dovecot -g -O2 -MT fts-backend-xapian.lo -MD -MP -MF .deps/fts-backend-xapian.Tpo -c -o fts-backend-xapian.lo fts-backend-xapian.cpp libtool:

THis is already what I send earlier (see : dovecot-xapian-1.0b2.tar.gz [1] ) What I would need is the files so one can download (git) it, and type some command (make ?) to compile it and place it in the right forlder (/usr/lib/dovecot/ or whatever is configured in the installed dovecot, which may differ from distribution to distribution) On 2019-01-13 19:47, Aki Tuomi wrote: > You need

Hi, I installed and tested your version, but the indexer process crashes reproducible with the following command after about 2000 messages were indexed: doveadm index -u paul at iwascoding.com -q \* Jan 14 09:26:15 mail dovecot: indexer-worker(paul at iwascoding.com)<16777><IKpfOqBHPFyJQQAADYqDFA>: Debug: Mailbox sent: UID 2038: Opened mail because: fts indexing Jan 14 09:26:15 mail

It's because you're misunderstanding how the lookup() function works. It gets ALL the search parameters, including the "mailbox inbox". This is intentional, and not a bug. Two reasons being: 1) The FTS plugin in theory could support indexing/searching any kinds of searches, not just regular word searches. So I didn't want to limit it unnecessarily. 2) Especially with

Op 13/01/2019 om 21:25 schreef Joan Moreau via dovecot: > > I tried to combined it, the "autoreconf" errors are solved > > Now, when I type "make install", the lib is not pushed into dovecot > folder, but somewhere in /usr/local/... > > How to adjust this to have it arriving in the proper folder ? > Depends on your system. It mostly a matter of setting

Timo, A little of logic here : 1 - the mailbox is passed by dovecot to the backend as a mailbox * pointer , NOT as a search parameter. -> It works properly when entering a search from roundcube or evolution for instance. -> therefore this is a clear bug of the command line 2 - the loop : Actually, the timeout occurs because the dovecot core is DISCARDING the results of the backend

> On 04/11/2020 05:19 Joan Moreau <jom at grosjo.net> wrote: > > > Hello > I am looking for help around memory management > 1 - How to get the current value of "vsz_limit" from inside a plugin (namely https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker > 2 - Is there a macro or function in dovecot to get the remaining free memory from this

THank you Odhiambo. I updated accordingly On 2019-01-14 08:07, Odhiambo Washington wrote: > In your README.md, perhaps "This project intends to provide a straightforward and simple PROCEDURE to configure FTS plugin for Dovecot, leveraging the efforts by the Xapian.org team." is better?? > Also in the part after cloning from git: > > ./configure --prefix=/usr

Thank you Stephan. The version here shall be up and running : https://github.com/grosjo/fts-xapian On 2019-01-14 00:07, Stephan Bosch wrote: > Op 13/01/2019 om 21:25 schreef Joan Moreau via dovecot: > >> I tried to combined it, the "autoreconf" errors are solved >> >> Now, when I type "make install", the lib is not pushed into dovecot folder, but