Re: Fatal Error after upgrade to 2:2.3.19-2+debian11

So it seems that all the crashes are caused by shared users that no longer exist. There were also mailboxes created by Dovecot at "/var/run/dovecot/user-not-found/us...@domain.de". After I removed the corresponding entries from the user_share database (SQL database), the crashes also seem to ha

Re: Fatal Error after upgrade to 2:2.3.19-2+debian11

Here of course the missing backtrace: #0 0x7fcb470e517c in acl_mailbox_get_aclobj (box=box@entry=0x5586bfc958f8) at acl-mailbox.c:31 #1 0x7fcb470d06ed in imap_acl_cmd_myrights (cmd=0x5586bfc0cbe8, mailbox=0x5586bfc2aef0 "shared/us...@domain.com", box=) at imap-acl-plugin.c:658 #2 c

Re: Fatal Error after upgrade to 2:2.3.19-2+debian11

after installing the dovecot-dbg package I now get additional error logs (or maybe I missed them before): May 16 15:47:21 wv-mail-imap1-1 dovecot: imap(us...@domain.com): Panic: Module context acl_storage_module missing May 16 15:47:21 wv-mail-imap1-1 dovecot: imap(us...@domain.com): Error: R

Re: Fatal Error after upgrade to 2:2.3.19-2+debian11

On 16. May 2022, at 14.09, Sebastian Kroczek wrote: > > Hello all, > > I updated the server tonight and with it Dovecot from 2.2.27 to > 2:2.3.19-2+debian11. However, there seems to be a problem with the ACLs, > because since then fatal errors are logged (see core dump). I suspect that > some

Re: Fatal Error after upgrade to 2:2.3.19-2+debian11

ok the rights can be a bit confusing at times assuming you are running virtual users (or not) try these one at a time, i found that when dovecot starts it will adjust the permissions on the control files accordingly to what is set in the examples below, also note postfix can be a variable in

Fatal Error after upgrade to 2:2.3.19-2+debian11

Hello all, I updated the server tonight and with it Dovecot from 2.2.27 to 2:2.3.19-2+debian11. However, there seems to be a problem with the ACLs, because since then fatal errors are logged (see core dump). I suspect that some outdated configuration is causing this behavior, but so far I cou

Re: Indexer error after upgrade to 2.3.11.3 [trial patch]

On 31.10.20 00:18, Scott Q. wrote: I have implemented this change and the core dumps went away. It appears so far that it's indeed the right fix. Has this change been introduced in 2.3.11.3 ? Thanks! On Tuesday, 27/10/2020 at 08:20 John Fawcett wrote: On 22/10/2020 10:23, John Fawcett wr

Re: Indexer error after upgrade to 2.3.11.3 [trial patch]

On 31/10/2020 15:15, Scott Q. wrote: > But do you know how this bug was introduced ? > > I checked the history of that file and don't see anything introduced > recently that might cause > this:  > https://github.com/dovecot/core/commits/master/src/lib-http/http-client-request.c >

Re: Indexer error after upgrade to 2.3.11.3 [trial patch]

But do you know how this bug was introduced ? I checked the history of that file and don't see anything introduced recently that might cause this:  https://github.com/dovecot/core/commits/master/src/lib-http/http-client-request.c The only one that might be somewhat related is this one from Apr 2

Re: Indexer error after upgrade to 2.3.11.3 [trial patch]

On 31/10/2020 00:18, Scott Q. wrote: > I have implemented this change and the core dumps went away. > > It appears so far that it's indeed the right fix. > > Has this change been introduced in 2.3.11.3 ?  > > Thanks! I've also been running it for 4 days without any further panics / segfaults and n

Re: Indexer error after upgrade to 2.3.11.3 [trial patch]

I have implemented this change and the core dumps went away. It appears so far that it's indeed the right fix. Has this change been introduced in 2.3.11.3 ?  Thanks! On Tuesday, 27/10/2020 at 08:20 John Fawcett wrote: On 22/10/2020 10:23, John Fawcett wrote: On 21/10/2020 19:00, John F

Re: Indexer error after upgrade to 2.3.11.3 [trial patch]

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 havi

Re: Indexer error after upgrade to 2.3.11.3

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 ).

Re: Indexer error after upgrade to 2.3.11.3

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:

Re: Indexer error after upgrade to 2.3.11.3

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 17:37, Josef 'Jeff' Sipek wrote: On

Re: Indexer error after upgrade to 2.3.11.3

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, Al

Re: Indexer error after upgrade to 2.3.11.3

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, after the

Re: Indexer error after upgrade to 2.3.11.3

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

Re: Indexer error after upgrade to 2.3.11.3

On 8/19/20 11:37 PM, Josef 'Jeff' Sipek wrote: > If you can try it, let us know how it went. Hi, Thanks. I had this problem and the patch helped. This suddenly started on two different deployments, a few days apart, one was October 8 and the other October 12, upon delivery of apparently trouble

Re: Indexer error after upgrade to 2.3.11.3

On 2020/10/15 10:07, Scott Q. wrote: > FWIW, I investigated this as much as I could...all I could find is that there > is some sort of > difference in index files between versions. Once a user has been 'converted' > to 2.3.11.3 index > files, the error went away. > > On the other hand I was told

Re: Indexer error after upgrade to 2.3.11.3

FWIW, I investigated this as much as I could...all I could find is that there is some sort of difference in index files between versions. Once a user has been 'converted' to 2.3.11.3 index files, the error went away. On the other hand I was told that index file format hasn't changed in a long time

Re: Indexer error after upgrade to 2.3.11.3

On 2020-09-07, Scott Q. wrote: > > 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 FWIW also seen with 2.3.11.3 on OpenBSD, the only

Re: Indexer error after upgrade to 2.3.11.3

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

Re: Indexer error after upgrade to 2.3.11.3

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(

Re: Indexer error after upgrade to 2.3.11.3

I've actually done a lot of debugging on this and it has to do with very large headers in e-mails. I've sent to Jeff the full GDB debug output and from what I gathered myself, I can replicate the bug 100% of the time when I send a message with 100 header lines of  x-locaweb-id: TsKSlv8kr1xtXZssG

Re: Indexer error after upgrade to 2.3.11.3

On 19/08/2020 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

Re: [EXT] Re: Indexer error after upgrade to 2.3.11.3

On Wed, Sep 02, 2020 at 15:52:36 -0400, Scott Q. wrote: > Sorry about that. My FreeBSD system automatically applied your > patches and I assumed they were already part of the master. No problem, it happens :) Since your setup has a bit of a mind of its own, I have to ask... are you sure you were

Re: Indexer error after upgrade to 2.3.11.3

Sorry about that. My FreeBSD system automatically applied your patches and I assumed they were already part of the master. Unfortunately it still means the bug isn't resolved with these changes. On Wednesday, 02/09/2020 at 15:34 Josef 'Jeff' Sipek wrote: On Wed, Sep 02, 2020 at 15:07:37 -0400,

Re: Indexer error after upgrade to 2.3.11.3

On Wed, Sep 02, 2020 at 15:07:37 -0400, Scott Q. wrote: > Sorry to bump up an old thread. > > 2.3.11.3 already contains this patch and the error still gets > generated.  I'm not sure where you are finding it. The below patch isn't on the release-2.3.11 branch. It isn't in the 2.3.11.3 tarball.

Re: Indexer error after upgrade to 2.3.11.3

Sorry to bump up an old thread. 2.3.11.3 already contains this patch and the error still gets generated.  Anything else we could try ? Scott On Wednesday, 19/08/2020 at 11:37 Josef 'Jeff' Sipek wrote: On Wed, Aug 19, 2020 at 17:03:57 +0200, Alessio Cecchi wrote: > Hi, > > after the upgrade

Indexer error after upgrade to 2.3.11.3

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(i...@domain.com) session=: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL

Re: Indexer error after upgrade to 2.3.11.3

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

Indexer error after upgrade to 2.3.11.3

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(i...@domain.com) session=: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL

Re: Please help: error after upgrade to version 2.1.16

me of my config-files. > What version did you upgrade from? > > Gesendet: Samstag, 18. April 2015 um 20:24 Uhr > Von: "Edgar Pettijohn III" > An: "Dovecot Mailing List" > Betreff: Re: Please help: error after upgrade to version 2.1.16 > I think you may ne

Aw: Re: Please help: error after upgrade to version 2.1.16

ijohn III" An: "Dovecot Mailing List" Betreff: Re: Please help: error after upgrade to version 2.1.16 I think you may need something similar to: protocols = imap pop3 lmtp sieve service auth { unix_listener auth-userdb { group = _smtpd mode = 0666 user = _smtpd } } service imap-l

Re: Please help: error after upgrade to version 2.1.16

I think you may need something similar to: protocols = imap pop3 lmtp sieve service auth { unix_listener auth-userdb { group = _smtpd mode = 0666 user = _smtpd } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes

Please help: error after upgrade to version 2.1.16

Hallo I can not find a forum at dovecot.org and I get a problem I can not solve. After Updating to the version dovecot2  2.1.16  I can no more get eMails with my eMail-client. All has been working fine before. Server: FreeBSD 10.0-RELEASE-p18, with perl 5, version 18, subversion 4 (v5.18.4)   It

Re: Error after Upgrade

Hi Jim, Jim Knuth wrote: > Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): > child 25638 killed with signal 11 (core dumps disabled) You should try to get a core dump and a gdb backtrace with debug symbols package installed. The following article describes how to get

Re: Error after Upgrade

am 25.07.14 12:14 schrieb Reindl Harald : Am 25.07.2014 11:49, schrieb Jim Knuth: am 25.07.14 11:38 schrieb Reindl Harald : Am 25.07.2014 11:23, schrieb Jim Knuth: after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 I discovered that in my log and all mai

Re: Error after Upgrade

Am 25.07.2014 11:49, schrieb Jim Knuth: > am 25.07.14 11:38 schrieb Reindl Harald : > >> Am 25.07.2014 11:23, schrieb Jim Knuth: >>> after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => >>> 2:2.2.13-1~auto+113 >>> I discovered that in my log and all mails stuck in the Queue. >>> I’

Re: Error after Upgrade

am 25.07.14 11:38 schrieb Reindl Harald : Am 25.07.2014 11:23, schrieb Jim Knuth: after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 I discovered that in my log and all mails stuck in the Queue. I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine

Re: Error after Upgrade

Am 25.07.2014 11:23, schrieb Jim Knuth: > after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => > 2:2.2.13-1~auto+113 > I discovered that in my log and all mails stuck in the Queue. > I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine > What’s wrong? the Debian package

Error after Upgrade

Hello, after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 I discovered that in my log and all mails stuck in the Queue. I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine. What’s wrong? Any ideas or solution greatly appreciated. Thanks. Jul 25 11