httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Eissing <stefan.eiss...@greenbytes.de>
Subject Re: mod_http2 and Frequent wake-ups for mpm_event
Date Mon, 06 Feb 2017 09:11:37 GMT
ok, I'll look at them. 

> Am 05.02.2017 um 19:51 schrieb Stefan Priebe - Profihost AG <s.priebe@profihost.ag>:
> 
> Hi Yann,
> 
> tested your patch against mod_ssl. I haven't seen any pool crashes again
> so it seems to fix this issue.
> 
> But two new ones:
> 
> Program terminated with signal SIGABRT, Aborted.
> #0  0x00007ff523558067 in raise () from /lib/x86_64-linux-gnu/libc.so.6
> #0  0x00007ff523558067 in raise () from /lib/x86_64-linux-gnu/libc.so.6
> #1  0x00007ff523559448 in abort () from /lib/x86_64-linux-gnu/libc.so.6
> #2  0x00007ff5235961b4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #3  0x00007ff52359b98e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #4  0x00007ff52359c923 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #5  0x00007ff523b06c83 in apr_allocator_destroy (allocator=0x7ff4d0000e50)
>    at memory/unix/apr_pools.c:152
> #6  0x0000556e7986bbef in task_destroy (m=0x7ff46402a028,
> task=0x7ff4d0029f00,
>    called_from_master=0) at h2_mplx.c:400
> #7  0x0000556e7986ce5b in task_done_iter (ctx=<optimized out>,
>    val=<optimized out>) at h2_mplx.c:1064
> #8  0x00007ff523afe5e6 in apr_hash_do (
>    comp=comp@entry=0x556e7987f180 <ihash_iter>,
> rec=rec@entry=0x7ff5037e5480,
>    ht=<optimized out>) at tables/apr_hash.c:542
> #9  0x0000556e7987fb5f in h2_ihash_iter (ih=<optimized out>,
>    fn=fn@entry=0x556e7986ce50 <task_done_iter>,
> ctx=ctx@entry=0x7ff46402a028)
>    at h2_util.c:315
> #10 0x0000556e7986d463 in h2_mplx_release_and_join (m=0x7ff46402a028,
>    wait=0x7ff464029fd0) at h2_mplx.c:619
> #11 0x0000556e79872ae4 in session_pool_cleanup (data=0x7ff464020318)
>    at h2_session.c:827
> #12 0x00007ff523b0748e in run_cleanups (cref=0x7ff464029fa8)
>    at memory/unix/apr_pools.c:2352
> #13 apr_pool_destroy (pool=0x7ff464029f38) at memory/unix/apr_pools.c:804
> #14 0x00007ff523b07745 in apr_pool_clear (pool=0x7ff4fc0150e8)
>    at memory/unix/apr_pools.c:769
> #15 0x0000556e798aa698 in ap_push_pool (queue_info=0x1e2e,
>    pool_to_recycle=0x1ebb) at fdqueue.c:234
> #16 0x0000556e798a59da in process_lingering_close (cs=0x7ff4fc015378,
>    pfd=0x556e7b8bd888) at event.c:1513
> #17 0x0000556e798a9510 in listener_thread (thd=0x1e2e,
> dummy=0x547b44ea3e1b3)
>    at event.c:1837
> #18 0x00007ff5238d60a4 in start_thread ()
>   from /lib/x86_64-linux-gnu/libpthread.so.0
> #19 0x00007ff52360b62d in clone () from /lib/x86_64-linux-gnu/libc.so.6
> 
> and
> 
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  apr_bucket_alloc (size=size@entry=64,
> list=list@entry=0x3fb50d4a7aeb1d49)
>    at buckets/apr_buckets_alloc.c:128
> #0  apr_bucket_alloc (size=size@entry=64,
> list=list@entry=0x3fb50d4a7aeb1d49)
>    at buckets/apr_buckets_alloc.c:128
> #1  0x00007ff523d2b1d3 in apr_bucket_heap_create (
>    buf=0x7ff51003b3a8 "
> \311\021A\216y\034\347\034Wy\360\343R\275\226o\020iw\227r\337\377",
> length=1300, free_func=0x7ff523d2ab50 <apr_bucket_free>,
>    list=0x3fb50d4a7aeb1d49) at buckets/apr_buckets_heap.c:81
> #2  0x0000556e79884f85 in append_scratch (io=0x7ff4440377c8)
>    at h2_conn_io.c:165
> #3  0x0000556e79884ffa in assure_scratch_space (io=0x7ff4440377c8)
>    at h2_conn_io.c:182
> #4  0x0000556e79885ce8 in h2_conn_io_pass (io=io@entry=0x7ff4440377c8,
>    bb=0x7ff444133698) at h2_conn_io.c:393
> #5  0x0000556e798732be in on_send_data_cb (ngh2=<optimized out>,
>    frame=<optimized out>, framehd=<optimized out>, length=1291,
>    source=<optimized out>, userp=0x7ff444037780) at h2_session.c:648
> #6  0x00007ff5243dde95 in ?? () from
> /usr/lib/x86_64-linux-gnu/libnghttp2.so.14
> #7  0x00007ff5243deea9 in nghttp2_session_send ()
>   from /usr/lib/x86_64-linux-gnu/libnghttp2.so.14
> #8  0x0000556e79875857 in h2_session_send (session=0x7ff444037780)
>    at h2_session.c:1376
> #9  0x0000556e79878b6c in h2_session_process (session=0x7ff444037780,
>    async=2062228809) at h2_session.c:2208
> #10 0x0000556e79867788 in h2_conn_run (ctx=0x7ff4440376b0, c=0x7ff51003b6a8)
>    at h2_conn.c:214
> #11 0x0000556e7986a421 in h2_h2_process_conn (c=0x7ff51003b6a8) at
> h2_h2.c:658
> #12 0x0000556e7980d050 in ap_run_process_connection (c=0x7ff51003b6a8)
>    at connection.c:42
> #13 0x0000556e798a7590 in process_socket (my_thread_num=<optimized out>,
>    my_child_num=<optimized out>, cs=0x7ff51003b618, sock=<optimized out>,
>    p=<optimized out>, thd=<optimized out>) at event.c:1134
> #14 worker_thread (thd=0x40, dummy=0x3fb50d4a7aeb1d49) at event.c:2137
> #15 0x00007ff5238d60a4 in start_thread ()
>   from /lib/x86_64-linux-gnu/libpthread.so.0
> #16 0x00007ff52360b62d in clone () from /lib/x86_64-linux-gnu/libc.so.6
> 
> Greets,
> Stefan
> 
>> Am 02.02.2017 um 11:09 schrieb Yann Ylavic:
>> Hi Stefan,
>> 
>> On Tue, Jan 31, 2017 at 4:01 PM, Stefan Priebe - Profihost AG
>> <s.priebe@profihost.ag> wrote:
>>> 
>>> any ideas?
>> 
>> I wonder if the attached patch (related to mod_ssl and proposed for
>> another segfault report) could help in your case.
>> 
>> Would you mind give it a try?
>> 
>> 
>> Thanks,
>> Yann.
>> 


Mime
View raw message