Mailing List Archive

sporadic 500 errors with 2.4.55
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 it's not a rewrite engine bug or misconfiguration.

I am sorry that this bug report is so vague, but I don't have a record in the
error_log, nor do I actually see the error when browsing to that web server.

I've only noticed this because I get emails when someone encounters a 500 error.

But maybe someone has seen this as well, in which case you have at least the
info that someone else experiences this also. It has happened about 30 times
in the last 4 hours. It's intermittent and makes no sense.

Cheers,
K. C.

--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 due to maybe a race
condition? This his highly speculative of course.

Cheers,
K. C.

--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 contention/lock issue with h2 that might also result in a 500 now and then
> due to maybe a race condition? This his highly speculative of course.

Some questions:

1. As you suspect h2 have you tried running 2.4.55 without mod_http2?
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?
3. Do you use %L in your access and error log which eases correlating the logs?
4. What loglevel do you use and what would be the highest one you could set given the nature of the error (sporadic) and the
traffic on your side?

Regards

RĂ¼diger
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 downgrading the logs were wiped by rotatelogs.
Unfortunately rotatelogs does not append, but always truncates the logs at
server start.

> 3. Do you use %L in your access and error log which eases correlating the logs?

No. I am using the following:

ErrorLogFormat "[%{cu}t] [%-m:%l] [pid %P] [%7F] %M"
LogFormat "%h %u [%{%F %T}t.%{usec_frac}t %{%z}t] \"%r\" %>s %b
\"%{Referer}i\" \"%{User-Agent}i\"" standard
LogFormat "%v %h %u [%{%F %T}t.%{usec_frac}t %{%z}t] \"%r\" %>s %b
\"%{Referer}i\" \"%{User-Agent}i\"" vhosts

> 4. What loglevel do you use and what would be the highest one you could set given the nature of the error (sporadic) and the
> traffic on your side?

I am just using the default log level. (LogLevel warn)

I have downgraded and I won't upgrade to 2.4.55 anytime soon. At least not
this server. I rather depend on this server and the implications are too
great. I might be able to setup a test server in a VM, but can't say if I will
be able to reproduce it there. However, I wouldn't be able to set a debug log
level on my prod server anyway.
2.4.54 works perfectly fine. I don't get any errors and the performance is
subjectively better. Thus I will stick with that version for now.

I will be heading to bed soon. It's rather late (or early) already in EST. ;-)

Cheers,
K. C.


--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 percentage of HTTP/2.0 requests are logged with a 500 error right after upgrading to 2.4.55.

In my case this is on CentOS 7, OpenSSL 1.1.1q, apr-1.6.3, apr-util-1.6.1, libnghttp2-1.33

No customer noticed it, since (in my case) it is only about 0,01% of HTTP/2.0 requests. Downgraded all h2 servers to 2.4.54 and the 500 errors are gone.

First octet, and folder/filenames anonymized. We don't log User Agents or anything more than that. I know this is not very helpful. Sorry about these very sparse information :-(

XX.200.70.42 - - [18/Jan/2023:08:48:18 +0100] "GET /not-revealable/img/rdax_720x390s.jpg HTTP/2.0" 500 -
XX.188.223.140 - - [18/Jan/2023:08:50:48 +0100] "GET /not-revealable/img/favicon.ico HTTP/2.0" 500 -
XX.88.81.152 - - [18/Jan/2023:08:51:04 +0100] "GET /not-revealable/img/favicon.ico HTTP/2.0" 500 -
XX.88.81.152 - - [18/Jan/2023:08:51:09 +0100] "GET /not-revealable/img/favicon.ico HTTP/2.0" 500 -
XX.179.130.67 - - [18/Jan/2023:08:51:45 +0100] "GET /not-revealable/img/Digitae_1570x850px_rdax_720x390p.jpg HTTP/2.0" 500 -
XX.179.130.67 - - [18/Jan/2023:08:51:45 +0100] "GET /not-revealable/img/Slide_rdax_720x390.png HTTP/2.0" 500 -
XX.179.130.67 - - [18/Jan/2023:08:52:58 +0100] "GET /not-revealable/img/Adobetock_259606883_1570x850_rdax_720x390p.jpg HTTP/2.0" 500 -
XX.179.130.67 - - [18/Jan/2023:08:52:59 +0100] "GET /not-revealable/img/logo.png HTTP/2.0" 500 -
XX.247.9.187 - - [18/Jan/2023:08:54:48 +0100] "GET /not-revealable/img/Klutrale_1570x850_rdax_720x390p.jpg HTTP/2.0" 500 -
XX.179.130.67 - - [18/Jan/2023:08:55:11 +0100] "GET / HTTP/2.0" 500 -
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 ulimit on open file descriptors? CentOS should be generous, but we could test if an increased limit has any effects on the situation.

Further, looking at the list, all failed request seem to be plain files except the last. Is "/" the path used and does it also map to something like "index.html". Do you have non-file looksup where errors happen? I know that this is not a strong indicator, but may it helps us narrow this down.

Thanks for your help,

Stefan

> Am 18.01.2023 um 10:05 schrieb Andreas S. Kerber <ask@ag-trek.de>:
>
> 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 percentage of HTTP/2.0 requests are logged with a 500 error right after upgrading to 2.4.55.
>
> In my case this is on CentOS 7, OpenSSL 1.1.1q, apr-1.6.3, apr-util-1.6.1, libnghttp2-1.33
>
> No customer noticed it, since (in my case) it is only about 0,01% of HTTP/2.0 requests. Downgraded all h2 servers to 2.4.54 and the 500 errors are gone.
>
> First octet, and folder/filenames anonymized. We don't log User Agents or anything more than that. I know this is not very helpful. Sorry about these very sparse information :-(
>
> XX.200.70.42 - - [18/Jan/2023:08:48:18 +0100] "GET /not-revealable/img/rdax_720x390s.jpg HTTP/2.0" 500 -
> XX.188.223.140 - - [18/Jan/2023:08:50:48 +0100] "GET /not-revealable/img/favicon.ico HTTP/2.0" 500 -
> XX.88.81.152 - - [18/Jan/2023:08:51:04 +0100] "GET /not-revealable/img/favicon.ico HTTP/2.0" 500 -
> XX.88.81.152 - - [18/Jan/2023:08:51:09 +0100] "GET /not-revealable/img/favicon.ico HTTP/2.0" 500 -
> XX.179.130.67 - - [18/Jan/2023:08:51:45 +0100] "GET /not-revealable/img/Digitae_1570x850px_rdax_720x390p.jpg HTTP/2.0" 500 -
> XX.179.130.67 - - [18/Jan/2023:08:51:45 +0100] "GET /not-revealable/img/Slide_rdax_720x390.png HTTP/2.0" 500 -
> XX.179.130.67 - - [18/Jan/2023:08:52:58 +0100] "GET /not-revealable/img/Adobetock_259606883_1570x850_rdax_720x390p.jpg HTTP/2.0" 500 -
> XX.179.130.67 - - [18/Jan/2023:08:52:59 +0100] "GET /not-revealable/img/logo.png HTTP/2.0" 500 -
> XX.247.9.187 - - [18/Jan/2023:08:54:48 +0100] "GET /not-revealable/img/Klutrale_1570x850_rdax_720x390p.jpg HTTP/2.0" 500 -
> XX.179.130.67 - - [18/Jan/2023:08:55:11 +0100] "GET / HTTP/2.0" 500 -
>
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 servers serving static content and a very small percentage of HTTP/2.0 requests are logged with a 500 error right after upgrading to 2.4.55.
>
> In my case this is on CentOS 7, OpenSSL 1.1.1q, apr-1.6.3, apr-util-1.6.1, libnghttp2-1.33
>
> No customer noticed it, since (in my case) it is only about 0,01% of HTTP/2.0 requests. Downgraded all h2 servers to 2.4.54 and the 500 errors are gone.
>
> First octet, and folder/filenames anonymized. We don't log User Agents or anything more than that. I know this is not very helpful. Sorry about these very sparse information :-(
>
> XX.200.70.42 - - [18/Jan/2023:08:48:18 +0100] "GET /not-revealable/img/rdax_720x390s.jpg HTTP/2.0" 500 -
> XX.188.223.140 - - [18/Jan/2023:08:50:48 +0100] "GET /not-revealable/img/favicon.ico HTTP/2.0" 500 -
> XX.88.81.152 - - [18/Jan/2023:08:51:04 +0100] "GET /not-revealable/img/favicon.ico HTTP/2.0" 500 -
> XX.88.81.152 - - [18/Jan/2023:08:51:09 +0100] "GET /not-revealable/img/favicon.ico HTTP/2.0" 500 -
> XX.179.130.67 - - [18/Jan/2023:08:51:45 +0100] "GET /not-revealable/img/Digitae_1570x850px_rdax_720x390p.jpg HTTP/2.0" 500 -
> XX.179.130.67 - - [18/Jan/2023:08:51:45 +0100] "GET /not-revealable/img/Slide_rdax_720x390.png HTTP/2.0" 500 -
> XX.179.130.67 - - [18/Jan/2023:08:52:58 +0100] "GET /not-revealable/img/Adobetock_259606883_1570x850_rdax_720x390p.jpg HTTP/2.0" 500 -
> XX.179.130.67 - - [18/Jan/2023:08:52:59 +0100] "GET /not-revealable/img/logo.png HTTP/2.0" 500 -
> XX.247.9.187 - - [18/Jan/2023:08:54:48 +0100] "GET /not-revealable/img/Klutrale_1570x850_rdax_720x390p.jpg HTTP/2.0" 500 -
> XX.179.130.67 - - [18/Jan/2023:08:55:11 +0100] "GET / HTTP/2.0" 500 -

Thanks. I understand it only happens with HTTP/2.0 not with other protocol versions, correct? Anything in the error logs?
Would it be possible for you to run 2.4.55 with loglevel increased?
If yes would it be possible for you to add %L to access log and error log?

Regards

RĂ¼diger
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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.

> Would it be possible for you to run 2.4.55 with loglevel increased?
> If yes would it be possible for you to add %L to access log and error log?

Sure, I'm now running with:

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\" %L"
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\" %L" common
LogLevel info

access log:
XXX.179.130.67 - - [18/Jan/2023:10:37:22 +0100] "GET /XXX/img/Karriere_rdax_720x390s.jpg HTTP/2.0" 500 - "https://www.XXX/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0" -
XXX.116.188.146 - - [18/Jan/2023:10:41:10 +0100] "GET /XXX/img/St%202018_Lisa%20Viertel_025_1570x850px_rdax_720x390p.jpg HTTP/2.0" 500 - "https://www.XXX/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 Edg/109.0.1518.52" -


webspace error log:
[Wed Jan 18 10:37:22.741094 2023] [core:info] [pid 17529:tid 139803164256000] [remote XXX.179.130.67:38661] AH00128: File does not exist: /data/wwwcust/virt1/html/XXX/XXX/css/ajax-loader.gif, referer: https://www.XXX/XXX/css/style.css

server error log:
[Wed Jan 18 10:32:47.130811 2023] [mpm_worker:notice] [pid 16656:tid 139803628373824] AH00292: Apache/2.4.55 (Unix) OpenSSL/1.1.1q configured -- resuming normal operations
[Wed Jan 18 10:32:47.130833 2023] [mpm_worker:info] [pid 16656:tid 139803628373824] AH00293: Server built: Jan 17 2023 15:58:35
[Wed Jan 18 10:32:47.130859 2023] [core:notice] [pid 16656:tid 139803628373824] AH00094: Command line: '/usr/local/apache2/bin/httpd'
[Wed Jan 18 10:32:47.131948 2023] [http2:info] [pid 17532:tid 139803628373824] h2_workers: created with min=64 max=96 idle_ms=600000
[Wed Jan 18 10:32:47.132285 2023] [http2:info] [pid 17529:tid 139803628373824] h2_workers: created with min=64 max=96 idle_ms=600000
[Wed Jan 18 10:32:47.132858 2023] [http2:info] [pid 17530:tid 139803628373824] h2_workers: created with min=64 max=96 idle_ms=600000
[Wed Jan 18 10:32:47.133224 2023] [http2:info] [pid 17531:tid 139803628373824] h2_workers: created with min=64 max=96 idle_ms=600000
[Wed Jan 18 10:32:58.145502 2023] [http2:info] [pid 18070:tid 139803628373824] h2_workers: created with min=64 max=96 idle_ms=600000
[Wed Jan 18 10:33:08.158243 2023] [http2:info] [pid 18218:tid 139803628373824] h2_workers: created with min=64 max=96 idle_ms=600000
[Wed Jan 18 10:42:33.709887 2023] [http2:info] [pid 19017:tid 139803628373824] h2_workers: created with min=64 max=96 idle_ms=600000
[Wed Jan 18 10:42:36.714291 2023] [http2:info] [pid 19150:tid 139803628373824] h2_workers: created with min=64 max=96 idle_ms=600000
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 implementation.

I just started the server with mod_http2.so from 2.4.54 and no further 500 errors where logged after that.

> Given that, could we check if we have a problem with the ulimit on open file descriptors? CentOS should be generous, but we could test if an increased limit has any effects on the situation.

Seems fine to me. Not a very busy server after all - just 15-20 requests per second. Load average 0.05 ;-)

> Further, looking at the list, all failed request seem to be plain files except the last. Is "/" the path used and does it also map to something like "index.html". Do you have non-file looksup where errors happen? I know that this is not a strong indicator, but may it helps us narrow this down.

We're using "DirectoryIndex index.html" and this index.html file is also just a static file. No fancy .htaccess RewriteRules or anything complex.
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
> Am 18.01.2023 um 11:00 schrieb Andreas S. Kerber <ask@ag-trek.de>:
>
> 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 implementation.
>
> I just started the server with mod_http2.so from 2.4.54 and no further 500 errors where logged after that.
>
>> Given that, could we check if we have a problem with the ulimit on open file descriptors? CentOS should be generous, but we could test if an increased limit has any effects on the situation.
>
> Seems fine to me. Not a very busy server after all - just 15-20 requests per second. Load average 0.05 ;-)

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 stefan@eissing.org, if you like.

>
>> Further, looking at the list, all failed request seem to be plain files except the last. Is "/" the path used and does it also map to something like "index.html". Do you have non-file looksup where errors happen? I know that this is not a strong indicator, but may it helps us narrow this down.
>
> We're using "DirectoryIndex index.html" and this index.html file is also just a static file. No fancy .htaccess RewriteRules or anything complex.
>
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 stefan@eissing.org, if you like.

Ok, I will do so.
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 atstefan@eissing.org, if you like.

I've setup a test VM and was able to reproduce the problem. However, in my
test I got only one 500 error, but I do have an access log and an error_log
set to http2:debug.

Do you want the 2 logs or is Andreas' log sufficient?

Cheers,
K. C.

--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 stefan@eissing.org

Thanks a lot!

Stefan

> Am 18.01.2023 um 17:00 schrieb Helmut K. C. Tessarek <tessarek@evermeet.cx>:
>
> 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 atstefan@eissing.org, if you like.
>
> I've setup a test VM and was able to reproduce the problem. However, in my test I got only one 500 error, but I do have an access log and an error_log set to http2:debug.
>
> Do you want the 2 logs or is Andreas' log sufficient?
>
> Cheers,
> K. C.
>
> --
> regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
> Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
>
> /*
> Thou shalt not follow the NULL pointer for chaos and madness
> await thee at its end.
> */
>
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
Thanks for the logs. That was really helpful. If you can build a 2.4.55 yourself, could you try the following patch?
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 stream before the response has really started. The HTTP/2 processing of this is totally fine and as should be. We just have an entry in the access log where there should be none.

It's also generating a 500 that can be seen by the server. e.g. I found this
by using a php file as an ErrorDocument that sends an email when encountering
a 500.

Thus this 500 is not only in the logs but must also trigger the ErrorDocument
500. Those are also gone now.

Thanks a bunch for fixing this.

Cheers,
K. C.

--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 <tessarek@evermeet.cx>:
>
> 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 stream before the response has really started. The HTTP/2 processing of this is totally fine and as should be. We just have an entry in the access log where there should be none.
>
> It's also generating a 500 that can be seen by the server. e.g. I found this by using a php file as an ErrorDocument that sends an email when encountering a 500.
>
> Thus this 500 is not only in the logs but must also trigger the ErrorDocument 500. Those are also gone now.
>
> Thanks a bunch for fixing this.
>
> Cheers,
> K. C.
>
> --
> regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
> Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
>
> /*
> Thou shalt not follow the NULL pointer for chaos and madness
> await thee at its end.
> */
>
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
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 <dev@httpd.apache.org>
> To: <dev@httpd.apache.org>
> Date: Wednesday, 18/01/2023 21:06
>
> 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
>> <tessarek@evermeet.cx>:
>>
>> 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 stream
>>> before the response has really started. The HTTP/2 processing of this
>>> is totally fine and as should be. We just have an entry in the access
>>> log where there should be none.
>>
>> It's also generating a 500 that can be seen by the server. e.g. I
>> found this by using a php file as an ErrorDocument that sends an email
>> when encountering a 500.
>>
>> Thus this 500 is not only in the logs but must also trigger the
>> ErrorDocument 500. Those are also gone now.
>>
>> Thanks a bunch for fixing this.
>>
>> Cheers,
>> K. C.
>>
>> --
>> regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
>> Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
>>
>> /*
>> Thou shalt not follow the NULL pointer for chaos and madness
>> await thee at its end.
>> */
>>
>
Re: sporadic 500 errors with 2.4.55 [ In reply to ]
Thanks for confirming, Steffen!

> Am 19.01.2023 um 10:12 schrieb SteffenAL <info@apachelounge.com>:
>
> 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 <dev@httpd.apache.org>
>> To: <dev@httpd.apache.org>
>> Date: Wednesday, 18/01/2023 21:06
>>
>> 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 <tessarek@evermeet.cx>:
>>>
>>> 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 stream before the response has really started. The HTTP/2 processing of this is totally fine and as should be. We just have an entry in the access log where there should be none.
>>>
>>> It's also generating a 500 that can be seen by the server. e.g. I found this by using a php file as an ErrorDocument that sends an email when encountering a 500.
>>>
>>> Thus this 500 is not only in the logs but must also trigger the ErrorDocument 500. Those are also gone now.
>>>
>>> Thanks a bunch for fixing this.
>>>
>>> Cheers,
>>> K. C.
>>>
>>> --
>>> regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
>>> Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
>>>
>>> /*
>>> Thou shalt not follow the NULL pointer for chaos and madness
>>> await thee at its end.
>>> */
>>>
>>
>
>