similar to: bug in indexer/indexer-worker

Hi. I am seeing the following in my logs. Happy to downgrade to an earlier version if you think this might be the problem, but dovecot.org is extremely slow (and has been for months) so I found it easier just to pull the latest from mercurial. Thanks. Laeeth Mar 12 20:48:39 indexer: Error: Indexer worker disconnected, discarding 1 reques ts for laeeth at laeeth.com Mar 12 20:48:39

Hi, after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently these errors from different users: Aug 18 11:02:35 Panic: indexer-worker(info at domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) Aug 18 11:02:35 Error: indexer-worker(info at

We're running 2.2.24 with fts_lucene and I wonder why indexer-working can be out-of-memory even with vsz_limit=750 MB ?! Peer May 15 12:14:51 dobby4 dovecot: indexer-worker(user at example.com): Fatal: pool_system_realloc(134217728): Out of memory May 15 12:14:51 dobby4 dovecot: indexer-worker(user at example.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xaa4b7)

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] and [3] encountered while just playing around, since I did not know of "tokenize" and did not find 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):

Hello All, I have a panic error in dovecot when I try to use the fts search with Solr. The version of dovecot I use is version 2.1 I have used a telnet session to search, but I don't know if this make a difference: telnet localhost imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE

On 16 Jun 2015, at 15:07, Infoomatic <infoomatic at gmx.at> wrote: > [1] Then comes the panic which produces loads of errormessages below the "Raw backtrace" part: > Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Warning: I/O leak: 0x7f40b55c39d0 (line 411, fd 20) > Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Warning: Timeout leak: 0x7f40b55c3780

On 19.08.20 17:37, Josef 'Jeff' Sipek wrote: > On Wed, Aug 19, 2020 at 17:03:57 +0200, Alessio Cecchi wrote: >> Hi, >> >> after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently >> these errors from different users: > It looks like this has been around for a while and you just got unlucky and > started seeing this now. Here's a quick

On 16.10.20 18:00, Scott Q. wrote: > This reminds me, the way I was able to reproduce this consistently was > by having large headers ( 100+ lines ). > > > On Friday, 16/10/2020 at 11:49 Patrik Peng wrote: > > On 19.08.20 17:37, Josef 'Jeff' Sipek wrote: > >> On Wed, Aug 19, 2020 at 17:03:57 +0200, Alessio Cecchi wrote: >>> Hi,

On 21/10/2020 16:44, Patrik Peng wrote: > On 16.10.20 18:34, Patrik Peng wrote: >> On 16.10.20 18:00, Scott Q. wrote: >>> This reminds me, the way I was able to reproduce this consistently >>> was by having large headers ( 100+ lines ). >>> >>> >>> On Friday, 16/10/2020 at 11:49 Patrik Peng wrote: >>> >>> On 19.08.20

I thought I had cleared out the corruption I had before - perhaps I was mistaken. What steps should I take to help locate these issues? Currently using 2.1rc1. I see the following errors in my logs, including out of memory and message size issues (at 15:30): Jan 4 05:17:17 bubba dovecot: indexer-worker(user1 at domain.com): Error: Raw backtrace:

Hi, I did a fresh installation of 2.2.9 in my test environment and enabled fts_autoindex=yes. I'm using a solr-server for FTS. I got this error, just once until now: _=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_=_= ==> dovecot-lmtp-errors.log <== Dec 03 16:15:06 lmtp(30601, username at domain.de): Error: Timeout (29s) while waiting for lock for

Hi, I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 2.2.19, but now panics (user with shared folder): /opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser dsync(standl2): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(standl2):

On 22/10/2020 10:23, John Fawcett wrote: > On 21/10/2020 19:00, John Fawcett wrote: >> On 21/10/2020 16:44, Patrik Peng wrote: >>> On 16.10.20 18:34, Patrik Peng wrote: >>>> On 16.10.20 18:00, Scott Q. wrote: >>>>> This reminds me, the way I was able to reproduce this consistently >>>>> was by having large headers ( 100+ lines ).

Hi, after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently these errors from different users: Aug 18 11:02:35 Panic: indexer-worker(info at domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) Aug 18 11:02:35 Error: indexer-worker(info at

Just to confirm, same problem, FreeBSD, after update from 2.3.10.1 to 2.3.11.3 with Solr 7.7. On 8/19/20 5:03 PM, Alessio Cecchi wrote: > Hi, > > after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently > these errors from different users: > > Aug 18 11:02:35 Panic: indexer-worker(info at domain.com) > session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>:

Hi! I use dovecot 2.1.7 on Ubuntu 12.10 with fts_solr und decode2text.sh for indexing attachments. This works great in general. Just for one user there is a problem with an unknown bad attachment. I run "doveadm index -A '*'". After a while I receive: doveadm(xyz): Error: fts_solr: Invalid XML input at line 1: mismatched tag doveadm(xyz): Panic: file solr-connection.c: line

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

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

I'm running, dovecot --version 2.3.11.3 (502c39af9) solr -version 8.6.3 uname -rm 5.8.13-200.fc32.x86_64 x86_64 grep _NAME /etc/os-release PRETTY_NAME="Fedora 32 (Server Edition)" CPE_NAME="cpe:/o:fedoraproject:fedora:32" Solr FTS plugin is enabled/configured, mail_plugins = virtual acl fts fts_solr plugin { fts = solr fts_autoindex = yes