similar to: Error: Mailbox INBOX: Transaction commit failed: FTS transaction commit failed: transaction context

Hi, i have a dovecot setup with virtual users. Each user has 2 entries for his mailbox. One is with the username formatted as %username%@%default_realm% , the other %username%@%domain% I've done some tests with it, but I don't complete understand how it works - I've emptied all document in solr so it empty. Doveadm is instructed to do the same with 'doveadm -D -v fts rescan

Hello all, For some time now we've bin using solr as a search engine (working great). I have added tika for searching inside documents, however it keeps crashing when indexing. When just indexing mails that arrive works good, but a reindex on all mail constantly crashes with below stacktrace. When I observe the packets with wireshark I see a HTTP-flow going to tika and suddenly, midway a

Hi, I played around a bit and tried to get tika to run with dovecot. In the end I was at least a bit successful. However, when I tried to index my inbox with "doveadm index -A '*'" I get: doveadm(infoomatic): Error: fts_tika: PUT http://localhost:8081/tika failed: 500 Server Error doveadm(infoomatic): Warning: I/O leak: 0x7f4f697bb170 (line 127, fd 24) doveadm(infoomatic):

On 15/11/2020 20:48, PGNet Dev wrote: > On 11/15/20 11:13 AM, John Fawcett wrote: >> Just a couple of updates about Tika and Solr together. >> >> 1. On mass reindexing I'm seeing panics - see below. These are present >> with Dovecot 2.3.10 and 2.3.11.3. Seem to go away with the fix which was >> previously posted on this list by Josef 'Jeff' Sipek, which

On 11/15/20 11:13 AM, John Fawcett wrote: > Just a couple of updates about Tika and Solr together. > > 1. On mass reindexing I'm seeing panics - see below. These are present > with Dovecot 2.3.10 and 2.3.11.3. Seem to go away with the fix which was > previously posted on this list by Josef 'Jeff' Sipek, which I repeat > below for easy of reference. > > 2. On

Hi, I've seen that latest Dovecot has the ability to use the Apache Tika Server to extract metadata from attachments. That is a pretty useful feature and looks to be an improvement over piping the attachment through a shellscript as done with fts_decoder. Having this feature enabled though I sometimes do see the situation that the tika service does not reply in time and it looks like the

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

Hello, we have a single DC after a clssicupgrade and we need to extend the schema. So we created a attrib.ldif with all our attributes and a object.ldif to add the attributes to the "CN=User" Object. We tested the two ldif-files on a DC with only a few users and groups and it works fine. Then we did the classicupgrade (same NC as the test-system) we have more then 30.000 users

On Wed, 21 Nov 2018 10:06:06 +0100 Stefan Kania via samba <samba at lists.samba.org> wrote: > Hello, > > we have a single DC after a clssicupgrade and we need to extend the > schema. So we created a attrib.ldif with all our attributes and a > object.ldif to add the attributes to the "CN=User" Object. We tested > the two ldif-files on a DC with only a few users

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 January 27, 2018 at 4:19 PM Infoomatic <infoomatic at gmx.at> wrote: > > > Hi, > > While testing our migration to dovecot 2.3.0, we encountered 2 panics, 1 segmentation fault while we wanted to rebuild the solr indizes. Problem [1] was encountered while rebuilding the indizes, and now I don't know how many mails/documents are indexed or where it got stuck. [2]

Hi, I have an AD with samba 4.6.7 (compiled from sources) on Fedora 17, and i tried to upgrade to 4.17.4, but the database upgrade fails. I executed samba-tool dbcheck --reindex --debuglevel=10 to see if i could find where the problem was, and seems it fails on a transaction regarding SID [S-1-5-18] In attachment the output from samba-tool dbcheck --reindex --debuglevel=10. Does any one

On 11/15/20 1:29 PM, John Fawcett wrote: >> atm, listening on localhost, with Dovecot -> Tika direct, no proxy. >> >> similarly fragile under load. throwing ~10 messages with .5-5MB attachments at it at once causes all sorts of complaints. frequently, like this Nov 15 15:59:40 test.loc tika[35696]: INFO tika/ (message/rfc822) Nov 15 15:59:41 test.loc tika[35696]: WARN

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 behind a nginx proxy with > basicauth in place. > >

On 11/13/20 9:56 AM, PGNet Dev wrote: >> (2) see here: https://wiki.dovecot.org/Plugins/FTS/Solr >> >> two useful settings are debug and rawlog_dir=whatever to be added in the same line as fts_solr with fts_solr = ... debug line #35 @ https://pastebin.com/9ecLQspD _looks_ like the 401's from solr server itself. i do NOT currently have service indexer{} service

On 11/13/20 11:37 AM, John Fawcett wrote: >> still dunno why the 401. :-/ > > So I just did a quick check of running dovecot with a standalone > solr-8.7.0 instance and I'm not seeing any issues. +1 > I confirm I haven't configured anything for indexer or indexer-worker in > dovecot, just left the defaults. +1 > For 401's returned from your solr server

> I guess you didn't need to enclose username and password in quotes, i.e. > > fts_solr = > url=https://myuser:my%40pass at solr.example.com:8984/solr/dovecot/ > use_libfts soft_commit=yes batch_size=250 On 11/13/20 12:56 PM, John Fawcett wrote: > I guess you didn't need to enclose username and password in quotes, i.e. > > fts_solr = >

On 13/11/2020 22:04, PGNet Dev wrote: >> I guess you didn't need to enclose username and password in quotes, i.e. >> >> fts_solr = >> url=https://myuser:my%40pass at solr.example.com:8984/solr/dovecot/ >> use_libfts soft_commit=yes batch_size=250 > > On 11/13/20 12:56 PM, John Fawcett wrote: > >> I guess you didn't need to enclose username and

On 13/11/2020 21:32, PGNet Dev wrote: > On 11/13/20 11:37 AM, John Fawcett wrote: >>> still dunno why the 401. :-/ >> >> So I just did a quick check of running dovecot with a standalone >> solr-8.7.0 instance and I'm not seeing any issues. > > +1 > >> I confirm I haven't configured anything for indexer or indexer-worker in >> dovecot, just

On 11/13/20 9:46 AM, John Fawcett wrote: >> (1) Can anyone yet verify Doveoct/fts-solr working with solr 8.7.x?>> (2) What logging config in Dovecot gets me more/detailed output for the fts_solr fail? >> (3) Any obvious clues as to what, specifically, is the source of this prob? >> > (1) I can't, I'm still on an earlier version I'll look for the 8.6.3,