Thanks for confirming, Steffen!
> Am 19.01.2023 um 10:12 schrieb SteffenAL :
>
> No unnecessary 500 seen anymore in the access log.
>
> Steffen
>
>> --- Original message ---
>> Subject: Re: sporadic 500 errors with 2.4.55
>> From: Stefan Eissing via d
No unnecessary 500 seen anymore in the access log.
Steffen
--- Original message ---
Subject: Re: sporadic 500 errors with 2.4.55
From: Stefan Eissing via dev
To:
Date: Wednesday, 18/01/2023 21:06
Thanks for the fast confirmation. Added as r1906775 to trunk, proposed
for backport to 2.4
Thanks for the fast confirmation. Added as r1906775 to trunk, proposed for
backport to 2.4.x
Kind Regards,
Stefan
> Am 18.01.2023 um 20:12 schrieb Helmut K. C. Tessarek :
>
> On 2023-01-18 13:40, Stefan Eissing via dev wrote:
>> Thanks for the logs. That was really helpful. If you can build a
On 2023-01-18 13:40, Stefan Eissing via dev wrote:
Thanks for the logs. That was really helpful. If you can build a 2.4.55
yourself, could you try the following patch?
Yep, the patch fixed it. I don't see any 500 errors anymore.
The 500 in the access log happens when a client RST (resets) a
Thanks for the logs. That was really helpful. If you can build a 2.4.55
yourself, could you try the following patch?
h2-access-500-on-rst.diff
Description: Binary data
Analysis:
The 500 in the access log happens when a client RST (resets) a stream before
the response has really started.
Helmut,
thanks for setting this up. If you can go a bit deeper and get me logs with
"http2:trace2" that would be supberb.
If you want to keep them out of the open, you can mail at ste...@eissing.org
Thanks a lot!
Stefan
> Am 18.01.2023 um 17:00 schrieb Helmut K. C. Tessarek :
>
> On
On 2023-01-18 06:43, Stefan Eissing via dev wrote:
In that case, maybe your could run the 2.4.55 mod_http2 with "LogLevel
http2:debug" until some 500s show up. That would be very interesting to analyze.
You can mail/link me such a log confidential atste...@eissing.org, if you like.
I've setup
Am Wed, Jan 18, 2023 at 12:43:07PM +0100 schrieb Stefan Eissing via dev:
> In that case, maybe your could run the 2.4.55 mod_http2 with "LogLevel
> http2:debug" until some 500s show up. That would be very interesting to
> analyze.
> You can mail/link me such a log confidential at
> Am 18.01.2023 um 11:00 schrieb Andreas S. Kerber :
>
> Am Wed, Jan 18, 2023 at 10:18:56AM +0100 schrieb Stefan Eissing via dev:
>> thanks for verifying that there is an issue. Would you be able to test a
>> httpd 2.4.55 with a mod_http2 from 2.4.54? If that runs without trouble, we
>> have
Am Wed, Jan 18, 2023 at 10:18:56AM +0100 schrieb Stefan Eissing via dev:
> thanks for verifying that there is an issue. Would you be able to test a
> httpd 2.4.55 with a mod_http2 from 2.4.54? If that runs without trouble, we
> have the problem verified with the recent changes in the http2
Am Wed, Jan 18, 2023 at 10:19:39AM +0100 schrieb Ruediger Pluem:
> Thanks. I understand it only happens with HTTP/2.0 not with other protocol
> versions, correct? Anything in the error logs?
Indeed only HTTP/2.0. No logged 500 errors since Jan 1st. Really started right
after running 2.4.55.
>
On 1/18/23 10:05 AM, Andreas S. Kerber wrote:
> Am Wed, Jan 18, 2023 at 03:15:43AM -0500 schrieb Helmut K. C. Tessarek:
>>> 2. As you see the 500 errors only in the access log are they only for
>>> HTTP/2.0 or also for other protocol versions?
>
> I can confirm this too. I have a bunch of h2
Andreas,
thanks for verifying that there is an issue. Would you be able to test a httpd
2.4.55 with a mod_http2 from 2.4.54? If that runs without trouble, we have the
problem verified with the recent changes in the http2 implementation.
Given that, could we check if we have a problem with the
Am Wed, Jan 18, 2023 at 03:15:43AM -0500 schrieb Helmut K. C. Tessarek:
> > 2. As you see the 500 errors only in the access log are they only for
> > HTTP/2.0 or also for other protocol versions?
I can confirm this too. I have a bunch of h2 servers serving static content and
a very small
These are all good questions.
On 2023-01-18 02:04, Ruediger Pluem wrote:
1. As you suspect h2 have you tried running 2.4.55 without mod_http2?
No.
2. As you see the 500 errors only in the access log are they only for HTTP/2.0
or also for other protocol versions?
I believe so, but after
On 1/18/23 7:01 AM, Helmut K. C. Tessarek wrote:
> Additional info:
>
> I reverted back to 2.4.54 and the errors are gone. It also seems that the
> responses are snappier. The perf observation is
> subjective of course.
>
> Without any proof I suspect that there is some sort of
Additional info:
I reverted back to 2.4.54 and the errors are gone. It also seems that the
responses are snappier. The perf observation is subjective of course.
Without any proof I suspect that there is some sort of contention/lock issue
with h2 that might also result in a 500 now and then
After I have upgraded to 2.4.55, I get internal 500 errors now and then.
The strange thing is that they do not show up in the error log, but only in
the access log.
Another weird thing is that they seem random and happen with random files,
like the favicon.ico
I don't do any redirects so
18 matches
Mail list logo
