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
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
>
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
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
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
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
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 ).
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 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
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,
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
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
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
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
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
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
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 @@
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:
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:
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
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
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
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.
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
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 !=
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
26 matches
Mail list logo
