> 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 wording). And I fixed it
>> in
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 wording). And I fixed it
> in https://github.com/icing/mod_h2/releases/tag/v2.0.18
>
> Looking
Le 31/05/2023 à 13:15, 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 wording). And I fixed it in
https://github.com/icing/mod_h2/releases/tag/v2.0.18
Looking forward to hear how it fares
Hi Bastien,
I was finally able to reproduce here what looks like the crashes you see with
mod_proxy_http2 (notice the careful wording). And I fixed it in
https://github.com/icing/mod_h2/releases/tag/v2.0.18
Looking forward to hear how it fares on your system.
Kind Regards,
Stefan
> Am
> 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 for the module, fixed observed bugs. But
>>
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 for the module, fixed observed bugs. But
> have not replicated your crashes which look weird. Sorry.
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 :
>
>
Le lundi 22 mai 2023 à 16:36 +0200, Stefan Eissing a écrit :
>
>
> > 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
> 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 requests.
>> Going back to the original
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 requests.
Going back to the original issue, do you still see those with mod_h2 v2.0.15?
That would be
Hi Bastien,
I am looking into the failures of mod_proxy_http2 and seeing an issue with
connection reuse and subsequent handling of requests.
Going back to the original issue, do you still see those with mod_h2 v2.0.15?
That would be interesting to know.
I do not know if just relying on
Le jeudi 18 mai 2023 à 15:04 +0200, Bastien Durel a écrit :
> 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 log?
>
> No (grepping AH03516 in *.log returns nothing (nor does "streams
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 log?
>
> No (grepping AH03516 in
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 log?
No (grepping AH03516 in *.log returns nothing (nor does "streams in hold"))
--
Bastien Durel
Did you have an warning message like "AH03516: unexpected NN streams in hold"
at that time in out error log?
> Am 18.05.2023 um 11:04 schrieb Bastien Durel :
>
> Hello,
>
> I ran with /usr/lib/apache2/modules/mod_http2_2.0.15.so &
> /usr/lib/apache2/modules/mod_proxy_http2_2.0.15.so since
Hello,
I ran with /usr/lib/apache2/modules/mod_http2_2.0.15.so &
/usr/lib/apache2/modules/mod_proxy_http2_2.0.15.so since yesterday
15:20, and got a SIGSEGV at 21:29:30 : it's not in
purge_consumed_buckets but it's in the h2_proxy stack ...
Here is the bt full of the core:
#0
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
Package: apache2
Version: 2.4.56-1~deb11u2
Severity: important
Dear Maintainer,
I see many segmentation faults in apache2, for exemple in the last 24h I got:
Tue 2023-05-16 13:40:59 CEST 7757403333 11 present /usr/sbin/apache2
Tue 2023-05-16 13:52:44 CEST 7983293333 11
18 matches
Mail list logo
