Le lundi 22 mai 2023 à 16:36 +0200, Stefan Eissing a écrit :
> 
> 
> > Am 19.05.2023 um 18:50 schrieb Bastien Durel <bast...@durel.org>:
> > 
> > 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 interesting to know.
> > No, I had only 2 segfaults since I upgraded to 2.0.15, and none is
> > in purge_consumed_buckets :
> > 
> > - proxy_pass_brigade
> > - ap_save_brigade
> > 
> > > I do not know if just relying on mod_proxy_http in your setup
> > > would be possible. But it could help us isolating issues.
> > 
> > I don't think so ... The knot-resolver I forward DOH requests to
> > seems to only support HTTP/2 ; if I change it to https://,
> > dog fails to resolve on it :
> > 
> > Error [http]: Nameserver returned HTTP 502 (Proxy Error)
> 
> I just released v2.0.16
> <https://github.com/icing/mod_h2/releases/tag/v2.0.16>. It contains a
> fix in mod_proxy_http2 retry handling. Not sure if this is related to
> your crashes as I was so far unsuccessful to reproduce those locally.
> But maybe you'd like to give this a try.

Hello,

Thanks. I've compiled and installed v2.0.16.

I "only" had 2 crashes([1][2]) since friday, so I guess I'll have to
monitor a few days to report back.

Thanks for your work,


[1]
#0  0x00007f9bb04650b3 in ssl_io_filter_output (f=0x7f9ba03c68d8, 
bb=0x7f9ba04a83b8) at ssl_engine_io.c:2008
#1  0x00007f9bb0597999 in proxy_pass_brigade (flush=1, bb=<optimized out>, 
origin=<optimized out>, p_conn=0x7f9ba03c80a0, bucket_alloc=<optimized out>) at 
h2_proxy_session.c:218
#2  raw_send (ngh2=<optimized out>, data=<optimized out>, length=70, 
flags=<optimized out>, user_data=0x7f9ba04a8190) at h2_proxy_session.c:244
#3  0x00007f9bb14a11f9 in nghttp2_session_send () from 
/usr/lib/x86_64-linux-gnu/libnghttp2.so.14
#4  0x00007f9bb059a9b9 in send_loop (session=0x7f9ba04a8190) at 
h2_proxy_session.c:1517
#5  h2_proxy_session_process (session=0x7f9ba04a8190) at h2_proxy_session.c:1553
#6  0x00007f9bb059db44 in ctx_run (ctx=0x7f9ba03524d0) at mod_proxy_http2.c:258

[2]
#0  0x00007f9bb04650c5 in ssl_io_filter_output (f=0x7f9ba01388d8, 
bb=0x7f9ba05613b8) at ssl_engine_io.c:2008
#1  0x00007f9bb0597999 in proxy_pass_brigade (flush=1, bb=<optimized out>, 
origin=<optimized out>, p_conn=0x7f9ba013a0a0, bucket_alloc=<optimized out>) at 
h2_proxy_session.c:218
#2  raw_send (ngh2=<optimized out>, data=<optimized out>, length=74, 
flags=<optimized out>, user_data=0x7f9ba0561190) at h2_proxy_session.c:244
#3  0x00007f9bb14a11f9 in nghttp2_session_send () from 
/usr/lib/x86_64-linux-gnu/libnghttp2.so.14
#4  0x00007f9bb059a9b9 in send_loop (session=0x7f9ba0561190) at 
h2_proxy_session.c:1517
#5  h2_proxy_session_process (session=0x7f9ba0561190) at h2_proxy_session.c:1553
#6  0x00007f9bb059db44 in ctx_run (ctx=0x7f9ba014c4d0) at mod_proxy_http2.c:258

-- 
Bastien

Reply via email to