Re: [proposed] 2.4 Maintenance SIG

2017-01-22 Thread Noel Butler
On 20/01/2017 07:45, Jacob Champion wrote: > On 01/19/2017 12:52 PM, Noel Butler wrote: > >> Frequent releases set off alarms in system admins minds, frequent >> releases give the view of unstable/unreliable software, and that is the >> largest cause of movement to an alternative. > > So, the

Re: [proposed] 2.4 Maintenance SIG

2017-01-22 Thread Noel Butler
On 20/01/2017 07:07, William A Rowe Jr wrote: > On Thu, Jan 19, 2017 at 2:52 PM, Noel Butler wrote: > On 20/01/2017 05:54, William A Rowe Jr wrote: > > posts, I don't think you will find a single post where I suggested > that there is an issue with the frequency of

Re: mod_http2 and Frequent wake-ups for mpm_event

2017-01-22 Thread Yann Ylavic
Hi Stefan, On Sun, Jan 22, 2017 at 8:00 PM, Stefan Priebe - Profihost AG wrote: > Am 22.01.2017 um 18:02 schrieb Eric Covener: >> On Sun, Jan 22, 2017 at 11:21 AM, Stefan Priebe - Profihost AG >> wrote: >>> Hi Stefan, >>> >>> no i was mistaken

Re: mod_http2 and Frequent wake-ups for mpm_event

2017-01-22 Thread Stefan Priebe - Profihost AG
Am 22.01.2017 um 18:02 schrieb Eric Covener: > On Sun, Jan 22, 2017 at 11:21 AM, Stefan Priebe - Profihost AG > wrote: >> Hi Stefan, >> >> no i was mistaken customer isn't using mod_proxy - but I think this is >> the patch causing me problems: >>

Re: mod_http2 and Frequent wake-ups for mpm_event

2017-01-22 Thread Eric Covener
On Sun, Jan 22, 2017 at 11:21 AM, Stefan Priebe - Profihost AG wrote: > Hi Stefan, > > no i was mistaken customer isn't using mod_proxy - but I think this is > the patch causing me problems: > https://github.com/apache/httpd/commit/a61a4bd02e483fb45d433343740d0130ee3d8d5d >

Re: mod_http2 and Frequent wake-ups for mpm_event

2017-01-22 Thread Stefan Eissing
Not my forté. Yann probably has a better idea here. Let's see if he has time to look at it tomorrow. > Am 22.01.2017 um 17:21 schrieb Stefan Priebe - Profihost AG > : > > Hi Stefan, > > no i was mistaken customer isn't using mod_proxy - but I think this is > the patch

Re: mod_http2 and Frequent wake-ups for mpm_event

2017-01-22 Thread Stefan Priebe - Profihost AG
Hi Stefan, no i was mistaken customer isn't using mod_proxy - but I think this is the patch causing me problems: https://github.com/apache/httpd/commit/a61a4bd02e483fb45d433343740d0130ee3d8d5d What do you think? Greets, Stefan Am 22.01.2017 um 17:17 schrieb Stefan Eissing: > >> Am 22.01.2017

Re: mod_http2 and Frequent wake-ups for mpm_event

2017-01-22 Thread Stefan Eissing
> Am 22.01.2017 um 17:14 schrieb Stefan Priebe - Profihost AG > : > > *arg* it's just mod_proxy - just saw thread safety and apr bucket aloc. ??? Can you elaborate? Is your finding the known hcheck bug or something else? > Stefan > > Am 22.01.2017 um 17:06 schrieb

Re: mod_http2 and Frequent wake-ups for mpm_event

2017-01-22 Thread Stefan Priebe - Profihost AG
*arg* it's just mod_proxy - just saw thread safety and apr bucket aloc. Stefan Am 22.01.2017 um 17:06 schrieb Stefan Priebe - Profihost AG: > Looks like others have the same crashes too: > https://bz.apache.org/bugzilla/show_bug.cgi?id=60071 > and >

Re: mod_http2 and Frequent wake-ups for mpm_event

2017-01-22 Thread Stefan Priebe - Profihost AG
Looks like others have the same crashes too: https://bz.apache.org/bugzilla/show_bug.cgi?id=60071 and https://github.com/apache/httpd/commit/8e63c3c9372cd398f57357099aa941cbba695758 So it looks like mod_http2 is running fine now. Thanks a lot Stefan. Yann i think i can start testing your mpm

Re: mod_http2 and Frequent wake-ups for mpm_event

2017-01-22 Thread Stefan Priebe
Hi, and a new one but also in ap_start_lingering_close: Program terminated with signal SIGSEGV, Segmentation fault. #0 apr_palloc (pool=pool@entry=0x7f455805e138, in_size=in_size@entry=32) at memory/unix/apr_pools.c:684 #0 apr_palloc (pool=pool@entry=0x7f455805e138,