Displaying 20 results from an estimated 10000 matches similar to: "status & use-case of fts_solr?"
2020 Nov 13
2
dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?
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,
2020 Nov 13
2
dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?
On 13/11/2020 19:55, PGNet Dev wrote:
> 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
2020 Oct 18
8
v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)
I've since rebuilt/reconfig'd all parts of my setup from scratch; some good cleanup along the way.
Atm, my entire system for send/recv, store/retrieve, + rules & search is working as I intend. Ok, mostly ...
Except for this accented-character search mystery. I've got a _lot_ of mail with various languages in bodies, so _do_ need to get this sorted.
> On 10/18/20 2:58 PM,
2020 Nov 13
2
dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?
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
2020 Nov 13
1
dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?
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
2020 Oct 19
2
v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)
On 10/18/20 10:28 PM, Aki Tuomi wrote:
> Dovecot FTS tokenization is not done, unless you have `use_libfts` in fts_solr setting, in your case
>
> fts_solr = url=https://solr.example.com:8984/solr/dovecot/ use_libfts
changing
- fts_solr = url=https://solr.example.com:8984/solr/dovecot/ soft_commit=yes batch_size=250
+ fts_solr = url=https://solr.example.com:8984/solr/dovecot/ use_libfts
2020 Nov 13
2
dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?
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
401 unauthorized
indexing failure, only for the one dir+message in 'Drafts',
2020-11-13
2019 Oct 08
2
fts_solr: Error: fts_solr: received invalid uid '0'
On 07/10/2019 15:13, Fabian Kuran via dovecot wrote:
> Hi,
>
>> Am 23.09.2019 um 09:36 schrieb Filip Hanes <filip.hanes at ringier.sk
>> <mailto:filip.hanes at ringier.sk>>:
>>
>>
>> ?t 19. 9. 2019 o?15:30 Fabian via dovecot <dovecot at dovecot.org
>> <mailto:dovecot at dovecot.org>> nap?sal(a):
>>
>> Are there any
2019 Oct 10
2
fts_solr: Error: fts_solr: received invalid uid '0'
Is there a way to get this as a patchset against 2.3.8?
On Tue, Oct 8, 2019 at 12:03 PM Stephan Bosch via dovecot <
dovecot at dovecot.org> wrote:
>
>
> On 08/10/2019 02:52, Stephan Bosch via dovecot wrote:
> >
> >
> > On 07/10/2019 15:13, Fabian Kuran via dovecot wrote:
> >> Hi,
> >>
> >>> Am 23.09.2019 um 09:36 schrieb Filip Hanes
2020 Nov 01
2
v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]
On 11/1/20 1:56 AM, John Fawcett wrote:
> At the moment I don't see other corrections needed in dovecot apart from
> command line doveadm fts which is not a show stopper. Via doveadm search
> I confirm - on my simple config - that search for accented or non
> accented characters works correctly as it does via imap connection.
thx. hopefully it'll get considered for a next
2019 Dec 02
1
fts_solr and # char
Hi,
Dovecot wiki says the solr url is something like 'solr/dovecot/' but
this gives a 404, if I install solr as per the docs I have a
'solr/#/dovecot/' url:
https://wiki.dovecot.org/Plugins/FTS/Solr
I have installed dovecot 2.3 from https://repo.dovecot.org/ and solr 8.3
as per the wiki on a Ubuntu 18.04.
The problem and the guess work I did:
fts_solr =
2019 Dec 10
1
fts_solr: Error: fts_solr: received invalid uid '0'
Any news on this getting into a release?
On Sun, Oct 13, 2019 at 2:24 AM Stephan Bosch <stephan at rename-it.nl> wrote:
>
>
> On 10/10/2019 04:05, Larry Rosenman via dovecot wrote:
> > Is there a way to get this as a patchset against 2.3.8?
> >
>
> https://github.com/stephanbosch/dovecot-core/tree/fix-solr-xml-parser-2.3.8
>
> This hasn't seen any QA
2019 Sep 13
4
fts_solr: Error: fts_solr: received invalid uid '0'
Hi,
we are trying to add full text search functionality with Solr to our Doveoct setup. Our Versions:
OS: Debian 9
Tried versions:
- Dovecot 2.2.7 with Solr 3.6
- Dovecot 2.3.4 with Solr 8.2
(2.2.7 from offical Debian repository, 2.3.4 from backports)
Search is working mostly of the time perfrectly smooth. But sometimes following message appears in mail.err:
dovecot:
2020 Nov 02
1
v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]
> On 02/11/2020 15:11 PGNet Dev <pgnet.dev at gmail.com> wrote:
>
>
> On 11/2/20 12:44 AM, Aki Tuomi wrote:
> > you should try removing use_libfts from your config line and let solr do that part.
>
> sry, i'm a bit confused.
>
> you'd suggested I _add_ it,
>
> https://dovecot.org/pipermail/dovecot/2020-October/120258.html
>
> > I
2016 Jun 23
4
fts_solr not working
I am running ISPConfig 3 on Debian and have managed to install the
dovecot-solr and dovecot-fts plugins.
I have solr running undet tomcat at http://localhost:8880 but the
indexing is not working.
I am using Dovecot 2.17
I do not understand namespaces and why fts_solr needs them, I just want
to index the entire users Maildir.
I am trying to index a users mailbox but am getting the following
2016 Apr 03
2
fts_solr: Lookup failed: 400 Bad Request / GET null null
Hi,
the log file shows suspicious entries as follows:
Apr 3 09:14:49 xxx dovecot: imap(user at domain): Error: fts_solr:
Lookup failed: 400 Bad Request
The tomcat7 log shows for this request:
10.0.0.234 - - [03/Apr/2016:09:14:49 +0200] "GET null null" 400 -
Dovecot is latest 2.2.23 with a pretty standard FTS config copied from the wiki:
mail_plugins = " acl fts fts_solr"
2020 Nov 02
2
v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]
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
2008 Jul 20
4
v1.1.2 release candidate
I've finally read and answered most of the mails on this list. ?If you
haven't received an answer to your question, resend it. There are a
couple of tricky mbox issues left, but I'm not sure if I can do anything
about them unless someone can show me how to reproduce the problems.
There are quite a lot of new features in v1.1.2 actually. Most of them
are in plugins so hopefully they
2020 Oct 19
4
v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)
On 10/19/20 1:18 AM, John Fawcett wrote:
> I would recommend you to redo the tests after correcting the
> configuration. To be doubly sure you can include accented and unique non
> accented text in the same email and search for both. If the non accented
> text is found you know you've searching against the updated index and
> the fact that accented text is not found is not
2010 Nov 01
1
fts_solr on debian lenny dovecot 1.2.15
Hello,
I cannot run FTS SOLR engine. OS is debian lenny. I re-compiled debian
package (from backports) with --with-solr option. Dovecot loads fts_solr
plugin. I know that it loads plugin because if I remove lib21_fts_solr_plugin.so, dovecot does not start. But it does not attempt to communicate with SOLR.
Simple check: stop solr tomcat, and open 8080 port in netcat:
$nc -l -p 8080
dovecot