> Am 08.06.2023 um 12:02 schrieb Bastien Durel :
>
> Le mercredi 31 mai 2023 à 13:15 +0200, Stefan Eissing a écrit :
>> Hi Bastien,
>>
>> I was finally able to reproduce here what looks like the crashes you
>> see with mod_proxy_http2 (notice the careful wor
Am 24.05.2023 um 19:44 schrieb Stefan Eissing :
>
>
>
>> Am 24.05.2023 um 16:10 schrieb Bastien Durel :
>>
>> Le mercredi 24 mai 2023 à 14:50 +0200, Stefan Eissing a écrit :
>>> I continue to improve mod_proxy_http2:
>>> https://github.com/icing/mod_h2/re
Thanks for the information.
Does this setup also run mod_proxy_http2? (I am investigating issue in that
module that I can somewhat reproduce)
What measurement is the "load average" you mentioned? CPU usage?
As to the observed log entries, these appear when a client connection is
terminated
> Am 24.05.2023 um 16:10 schrieb Bastien Durel :
>
> Le mercredi 24 mai 2023 à 14:50 +0200, Stefan Eissing a écrit :
>> I continue to improve mod_proxy_http2:
>> https://github.com/icing/mod_h2/releases/tag/v2.0.17
>>
>> Added more edge case tests fo
I continue to improve mod_proxy_http2:
https://github.com/icing/mod_h2/releases/tag/v2.0.17
Added more edge case tests for the module, fixed observed bugs. But have not
replicated your crashes which look weird. Sorry.
Kind Regards,
Stefan
> Am 23.05.2023 um 19:30 schrieb Bastien Durel :
>
>
> Am 19.05.2023 um 18:50 schrieb Bastien Durel :
>
> Le 19/05/2023 à 18:11, Stefan Eissing a écrit :
>> Hi Bastien,
> Hello
>
>> I am looking into the failures of mod_proxy_http2 and seeing an issue with
>> connection reuse and subsequent handling of reques
on mod_proxy_http in your setup would be
possible. But it could help us isolating issues.
Kind Regards,
Stefan
> Am 19.05.2023 um 15:04 schrieb Bastien Durel :
>
> Le jeudi 18 mai 2023 à 15:04 +0200, Bastien Durel a écrit :
>> Le 18/05/2023 à 14:41, Stefan Eissing a écrit :
>>>
Could you get me a full backtrace of all threads?
> Am 18.05.2023 um 15:04 schrieb Bastien Durel :
>
> Le 18/05/2023 à 14:41, Stefan Eissing a écrit :
>> Did you have an warning message like "AH03516: unexpected NN streams in
>> hold" at that time in out error
, cleanup = 0x0,
> canceltype = 0}}}
>not_first_call = 0
> #20 0x7f9bb1764a2f in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
>
>
> The request itself seems legit (I can run it without crashing the
> server).
>
> The last log e
Sorry to hear about this. I think the recent change that could be relevant here
is
the addition of:
h2_mplx.c#515:c1_purge_streams(m);
as seen in Apache httpd trunk and at https://github.com/icing/mod_h2.
This is intended to assure that streams and their requests are destroyed
in the right
Might be related to https://bz.apache.org/bugzilla/show_bug.cgi?id=66539
> Am 24.03.2023 um 15:30 schrieb root :
>
> Package: apache2
> Version: 2.4.56-1~deb11u1
> Severity: important
> X-Debbugs-Cc: t...@security.debian.org
>
> Unattended-upgrades applied this new version on 22 march @ 6AM.
11 matches
Mail list logo
