Re: mod_http2 and Frequent wake-ups for mpm_event

Am 19.01.2017 um 08:26 schrieb Stefan Eissing: > Will look into this. With which patch do you have it most frequently? It happens pretty fast while using: Apache 2.4.25 + mpm_event V6 + mod_http2 V1.8.8 Greets, Stefan > Cheers, Stefan > >> Am 19.01.2017 um 08:22 schrieb Stefan Priebe -

Re: mod_http2 and Frequent wake-ups for mpm_event

Will look into this. With which patch do you have it most frequently? Cheers, Stefan > Am 19.01.2017 um 08:22 schrieb Stefan Priebe - Profihost AG > : > > Hi Stefan, > > Apache 2.4.25 + mpm_event V7 and core mod_http2: > Core was generated by

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi Stefan, Apache 2.4.25 + mpm_event V7 and core mod_http2: Core was generated by `/usr/local/apache2/bin/httpd -k start'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00521d98 in h2_stream_out_prepare () (gdb) bt #0 0x00521d98 in h2_stream_out_prepare () #1

Re: [proposed] 2.4 Maintenance SIG

> Am 19.01.2017 um 06:34 schrieb William A Rowe Jr : > >> On Wed, Jan 18, 2017 at 7:35 PM, Eric Covener wrote: >>> On Wed, Jan 18, 2017 at 6:12 PM, William A Rowe Jr >>> wrote: >>> I'm wondering if there is anyone interested in a

Re: mod_http2 and Frequent wake-ups for mpm_event

Dear Stefan, dear Yann, a longer test run shows it's also crashing without any mpm_event patch at all. So I'm really sorry. It just starts crashing faster with the mpm_event patches. I'll now retest regarding mod_http2 core, plain apache 2.4.25 and mod_http v1.8.8 may be it's a regression in

Re: [proposed] 2.4 Maintenance SIG

On Wed, Jan 18, 2017 at 7:35 PM, Eric Covener wrote: > On Wed, Jan 18, 2017 at 6:12 PM, William A Rowe Jr > wrote: >> I'm wondering if there is anyone interested in a regression-fix-only 2.4.26 >> that >> finally proves to be a workable upgrade for all

Re: [proposed] 2.4 Maintenance SIG

On Wed, Jan 18, 2017 at 6:12 PM, William A Rowe Jr wrote: > I'm wondering if there is anyone interested in a regression-fix-only 2.4.26 > that > finally proves to be a workable upgrade for all httpd users? It sounds reasonable to me, but I think it's a bit of an oversell --

Re: mod_http2 and Frequent wake-ups for mpm_event

On Wed, Jan 18, 2017 at 10:49 PM, Stefan Priebe - Profihost AG wrote: > > v5 does not apply to 2.4.25. If you can send me a v5 version that > applies to 2.4.25 i'll test. Here it is (slightly modified to fix possible deadlocks, per r1762742 and r1774538). Thanks! Index:

Re: [proposed] 2.4 Maintenance SIG

On Tue, Jan 3, 2017 at 2:18 AM, Graham Leggett wrote: > On 03 Jan 2017, at 2:11 AM, William A Rowe Jr wrote: > >> So I'd like to know, in light of a perpetual chain of (often build and/or >> run-time breaking regression) enhancements, if there is support

Re: mod_http2 and Frequent wake-ups for mpm_event

Am 18.01.2017 um 22:53 schrieb Yann Ylavic: > On Wed, Jan 18, 2017 at 10:50 PM, Yann Ylavic wrote: >> On Wed, Jan 18, 2017 at 10:44 PM, Yann Ylavic wrote: >>> On Wed, Jan 18, 2017 at 10:23 PM, Stefan Priebe - Profihost AG >>>

Re: mod_http2 and Frequent wake-ups for mpm_event

Am 18.01.2017 um 22:50 schrieb Yann Ylavic: > On Wed, Jan 18, 2017 at 10:44 PM, Yann Ylavic wrote: >> On Wed, Jan 18, 2017 at 10:23 PM, Stefan Priebe - Profihost AG >> wrote: >>> >> >> Also, do you confirm that: >> 1. it didn't crash with v5 +

Re: mod_http2 and Frequent wake-ups for mpm_event

On Wed, Jan 18, 2017 at 10:50 PM, Yann Ylavic wrote: > On Wed, Jan 18, 2017 at 10:44 PM, Yann Ylavic wrote: >> On Wed, Jan 18, 2017 at 10:23 PM, Stefan Priebe - Profihost AG >> wrote: >>> >> >> Also, do you confirm that: >> 1.

Re: mod_http2 and Frequent wake-ups for mpm_event

On Wed, Jan 18, 2017 at 10:44 PM, Yann Ylavic wrote: > On Wed, Jan 18, 2017 at 10:23 PM, Stefan Priebe - Profihost AG > wrote: >> > > Also, do you confirm that: > 1. it didn't crash with v5 + original (2.4.25's) mod_http2? Hmm, v5 was against 2.4.23,

Re: mod_http2 and Frequent wake-ups for mpm_event

Am 18.01.2017 um 22:44 schrieb Yann Ylavic: > On Wed, Jan 18, 2017 at 10:23 PM, Stefan Priebe - Profihost AG > wrote: >> >> sadly it does not solve the issue. > > OK, thanks, back to the paper. > > Any [error] log maybe? What kind of? server-error.log just says [Wed Jan

Re: mod_http2 and Frequent wake-ups for mpm_event

On Wed, Jan 18, 2017 at 10:42 PM, Stefan Priebe - Profihost AG wrote: > I also tried to remove rev 1762701 from the v6 patchset. But it does not > match. That's more or less what v7 does..

Re: mod_http2 and Frequent wake-ups for mpm_event

On Wed, Jan 18, 2017 at 10:23 PM, Stefan Priebe - Profihost AG wrote: > > sadly it does not solve the issue. OK, thanks, back to the paper. Any [error] log maybe? Also, do you confirm that: 1. it didn't crash with v5 + original (2.4.25's) mod_http2? 2. it started

Re: mod_http2 and Frequent wake-ups for mpm_event

I also tried to remove rev 1762701 from the v6 patchset. But it does not match. Stefan Am 18.01.2017 um 22:23 schrieb Stefan Priebe - Profihost AG: > Hi Yann, > > sadly it does not solve the issue. > > Trace looks still the same: > Core was generated by `/usr/local/apache2/bin/httpd -k start'.

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi Yann, sadly it does not solve the issue. Trace looks still the same: Core was generated by `/usr/local/apache2/bin/httpd -k start'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fe0228a9014 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x7fe0228a9014

Re: Summary: Broken FastCGI with httpd

The thing is that when we are proxying back, some of those values can't make sense, since, for example, there is no "real" path on the httpd server that maps to the actual request file I think the original idea was to simply send the full URL to the FCGI server, to let it parse things out for

Re: Summary: Broken FastCGI with httpd

On 01/18/2017 06:47 AM, David Zuelke wrote: Thanks for picking this up! And thank you for driving this on the PHP side! --Jacob

Re: Summary: Broken FastCGI with httpd

On 01/17/2017 11:46 PM, Stefan Eissing wrote: Would it make sense to narrow down the setups to a few blessed ones that become part of our tests? I think so. Problem is that I don't, myself, know what is actually in use out there. I keep learning about new ways to invoke CGI every month, it

Re: Summary: Broken FastCGI with httpd

On 01/18/2017 06:56 AM, Eric Covener wrote: Unfortunately we might need our own directives for the overrides here to get them to run after the normal vars are calculated and only when we're in the proxy_fcgi handler. See https://bz.apache.org/bugzilla/show_bug.cgi?id=28903 for an older

Re: Summary: Broken FastCGI with httpd

On 01/18/2017 06:43 AM, Jim Jagielski wrote: Also, the fact that different methods of invoking FCGI result in different vars, at 1st blush, doesn't seem "incorrect" assuming that each difference makes some sense, in a way. They don't make sense. For example, mod_proxy_fcgi can be set up in a

Re: Async write completion broken in trunk?

On Wed, Jan 18, 2017 at 2:43 PM, Graham Leggett wrote: > On 18 Jan 2017, at 3:38 PM, Jim Jagielski wrote: > >> That's a good overview... Yeah, it might be getter better, but it does >> seem that the nature of the bugs implies it's also getting more >> fragile.

Re: JSON for mod_status

Really, this is now in the PMC's court. Doug and Aaron designed the BMX bean structure and module implementation. I'm aware that jfc's crew has also been a consumer of the module, so it already falls into that multi-vendor, multi-use case scenario. I'll leave this to them to advocate for httpd

Re: mod_http2 and Frequent wake-ups for mpm_event

On Wed, Jan 18, 2017 at 4:38 PM, Stefan Priebe - Profihost AG wrote: > Ok will wait whether you provide a fix or I should revert that part. Patch updated in PR 57399. Thanks, Yann.

ApacheCon CFP closing soon (11 February)

Hello, fellow Apache enthusiast. Thanks for your participation, and interest in, the projects of the Apache Software Foundation. I wanted to remind you that the Call For Papers (CFP) for ApacheCon North America, and Apache: Big Data North America, closes in less than a month. If you've been

Re: mod_http2 and Frequent wake-ups for mpm_event

Ok will wait whether you provide a fix or I should revert that part. Stefan Excuse my typo sent from my mobile phone. > Am 18.01.2017 um 16:32 schrieb Yann Ylavic : > > On Wed, Jan 18, 2017 at 4:17 PM, Stefan Priebe - Profihost AG > wrote: >> >>

Re: mod_http2 and Frequent wake-ups for mpm_event

On Wed, Jan 18, 2017 at 4:17 PM, Stefan Priebe - Profihost AG wrote: > > is it enought to revert that commit? I think so (worth a try at least). I'm about to commit sort of this revert to trunk, with a possible explanation... Thanks Stefan for all these follow ups.

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi Yann, is it enought to revert that commit? http://svn.apache.org/r1762701 Stefan Am 18.01.2017 um 12:49 schrieb Stefan Priebe - Profihost AG: > Hi, > > site is mostly used with http2. So it may be totally unrelated to > mod_http2. Sorry for the noise than. I just thought it by digging >

Re: Summary: Broken FastCGI with httpd

Just some additional info (the perl script described might be useful, esp if we fold it into the test framework): https://bugs.php.net/bug.php?id=54152 > On Jan 18, 2017, at 9:47 AM, David Zuelke wrote: > >> On 17.01.2017, at 23:16, Jacob Champion

Re: Summary: Broken FastCGI with httpd

On Wed, Jan 18, 2017 at 9:47 AM, David Zuelke wrote: > There's one more caveat around SCRIPT_FILENAME, I think: it might not be the > same for httpd and the FCGI backend if they're running on separate machines! I think this goes to the notion of overriding these variables w/

Re: JSON for mod_status

On 01/18/2017 03:19 PM, Luca Toscano wrote: > > > 2017-01-18 10:56 GMT+01:00 Daniel Gruno >: > > On 01/17/2017 07:33 PM, Jim Jagielski wrote: > > It all depends on what Bill decides regarding mod_bmx and if > > it is something we

Re: Summary: Broken FastCGI with httpd

> On 17.01.2017, at 23:16, Jacob Champion wrote: > > (This conversation is currently spread over Bugzilla, IRC, GitHub, and > php-internals. Here's my attempt at summarizing it for all of you. If you > have no interest in CGI or FastCGI, stop reading now.) Thanks for

Re: Summary: Broken FastCGI with httpd

It seems to me that SCRIPT_FILENAME is the key w/ PHP-FPM, but I could be wrong. Also, the fact that different methods of invoking FCGI result in different vars, at 1st blush, doesn't seem "incorrect" assuming that each difference makes some sense, in a way. Finally, I think that instead of

Re: JSON for mod_status

2017-01-18 10:56 GMT+01:00 Daniel Gruno : > On 01/17/2017 07:33 PM, Jim Jagielski wrote: > > It all depends on what Bill decides regarding mod_bmx and if > > it is something we intent to backport to 2.4.x > > > > Still not sure on how to *use* BMX, or how other modules > >

Re: Async write completion broken in trunk?

On 18 Jan 2017, at 3:38 PM, Jim Jagielski wrote: > That's a good overview... Yeah, it might be getter better, but it does > seem that the nature of the bugs implies it's also getting more > fragile. Could be, likely is, just my impression due to some weird > things I've seen

Re: Async write completion broken in trunk?

> On Jan 18, 2017, at 8:25 AM, Luca Toscano wrote: > > > > 2017-01-18 14:00 GMT+01:00 Jim Jagielski : > > > On Jan 18, 2017, at 7:50 AM, Graham Leggett wrote: > > > > On 17 Jan 2017, at 7:40 PM, Luca Toscano

Re: Async write completion broken in trunk?

2017-01-18 13:50 GMT+01:00 Graham Leggett : > On 17 Jan 2017, at 7:40 PM, Luca Toscano wrote: > > > Since this email thread seems important, is there any update from > anybody working on it? It would be great to open a bugzilla task otherwise, > to track

Re: Async write completion broken in trunk?

2017-01-18 14:00 GMT+01:00 Jim Jagielski : > > > On Jan 18, 2017, at 7:50 AM, Graham Leggett wrote: > > > > On 17 Jan 2017, at 7:40 PM, Luca Toscano wrote: > > > >> Since this email thread seems important, is there any update from >

Re: Async write completion broken in trunk?

> On Jan 18, 2017, at 8:14 AM, Graham Leggett wrote: > > On 18 Jan 2017, at 3:05 PM, Jim Jagielski wrote: > >> Well, there's this, and it seems like there are issues w/ >> the current mutexing as well, causing weird wake-ups. > > Only solution really is to

Re: Async write completion broken in trunk?

On 18 Jan 2017, at 3:05 PM, Jim Jagielski wrote: > Well, there's this, and it seems like there are issues w/ > the current mutexing as well, causing weird wake-ups. Only solution really is to find the bugs and fix them. Regards, Graham — smime.p7s Description: S/MIME

Re: Async write completion broken in trunk?

> On Jan 18, 2017, at 8:01 AM, Graham Leggett wrote: > > On 18 Jan 2017, at 3:00 PM, Jim Jagielski wrote: > >> Somewhat on-topic but also off-topic as well, but it does seem >> that event on trunk is getting much more fragile instead of more >> stable. It

Re: Async write completion broken in trunk?

On 18 Jan 2017, at 3:00 PM, Jim Jagielski wrote: > Somewhat on-topic but also off-topic as well, but it does seem > that event on trunk is getting much more fragile instead of more > stable. It seems to be picking up some kruft which is making > event on trunk a *worse* option

Re: Async write completion broken in trunk?

> On Jan 18, 2017, at 7:50 AM, Graham Leggett wrote: > > On 17 Jan 2017, at 7:40 PM, Luca Toscano wrote: > >> Since this email thread seems important, is there any update from anybody >> working on it? It would be great to open a bugzilla task

Re: Async write completion broken in trunk?

On 17 Jan 2017, at 7:40 PM, Luca Toscano wrote: > Since this email thread seems important, is there any update from anybody > working on it? It would be great to open a bugzilla task otherwise, to track > everything and make sure that we don't forget about it :) I

Re: mod_http2 and Frequent wake-ups for mpm_event

> Am 18.01.2017 um 13:39 schrieb Stefan Eissing : > > There is currently no cleanup register for shutting down that way. If the > main connection pool gets cleaned before the special meta is destroyed, these > problem might happen. Not sure. I am babbling. Of

Re: mod_http2 and Frequent wake-ups for mpm_event

Yann, all these traces point to the connection shutdown case for mod_http2 which is triggered by writing a special meta bucket and cleaning up on its destruction. That's the trick to make sure that all data has been sent and similar to the EOR bucket. There is currently no cleanup register

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi, and a new one just some seconds ago: (gdb) bt #0 0x7f32a3747014 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f32a3bda036 in ?? () from /usr/lib/x86_64-linux-gnu/libapr-1.so.0 #2 0x7f32a3bda46f in apr_hash_set () from /usr/lib/x86_64-linux-gnu/libapr-1.so.0 #3

Re: JSON for mod_status

Nice! > Am 18.01.2017 um 12:46 schrieb Jim Jagielski : > > This is too awesome for words :) > >> On Jan 18, 2017, at 4:56 AM, Daniel Gruno wrote: >> >> On 01/17/2017 07:33 PM, Jim Jagielski wrote: >>> It all depends on what Bill decides regarding

Re: JSON for mod_status

This is too awesome for words :) > On Jan 18, 2017, at 4:56 AM, Daniel Gruno wrote: > > On 01/17/2017 07:33 PM, Jim Jagielski wrote: >> It all depends on what Bill decides regarding mod_bmx and if >> it is something we intent to backport to 2.4.x >> >> Still not sure on

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi, site is mostly used with http2. So it may be totally unrelated to mod_http2. Sorry for the noise than. I just thought it by digging through the traces. Stefan Am 18.01.2017 um 12:34 schrieb Yann Ylavic: > Hi Stefan, > > On Wed, Jan 18, 2017 at 11:33 AM, Stefan Priebe - Profihost AG >

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi Stefan, On Wed, Jan 18, 2017 at 11:33 AM, Stefan Priebe - Profihost AG wrote: > > after applying the event patch to 2.4.25 from > https://bz.apache.org/bugzilla/show_bug.cgi?id=57399. > > I'm seeing segfaults in the mod_http2 code. I already bumped mod_http2 > to

Re: mod_http2 and Frequent wake-ups for mpm_event

On Wed, Jan 18, 2017 at 12:09 PM, Stefan Eissing wrote: > Can't have it all, Stefan! :) > > Seriously, will have a look at this. Thanks for the traces. I possibly messed up with event's locking in latest patch from PR 57399. Actually it removes locks around

Re: mod_http2 and Frequent wake-ups for mpm_event

Can't have it all, Stefan! Seriously, will have a look at this. Thanks for the traces. -Stefan > Am 18.01.2017 um 11:33 schrieb Stefan Priebe - Profihost AG > : > > Hi Stefan, > Hi Yann, > > after applying the event patch to 2.4.25 from >

mod_http2 and Frequent wake-ups for mpm_event

Hi Stefan, Hi Yann, after applying the event patch to 2.4.25 from https://bz.apache.org/bugzilla/show_bug.cgi?id=57399. I'm seeing segfaults in the mod_http2 code. I already bumped mod_http2 to v1.8.8. But the segfaults are still happening. gdb shows this: Core was generated by

Re: JSON for mod_status

On 01/17/2017 07:33 PM, Jim Jagielski wrote: > It all depends on what Bill decides regarding mod_bmx and if > it is something we intent to backport to 2.4.x > > Still not sure on how to *use* BMX, or how other modules > "hook in" (right now we have several modules hook into > mod_status so the

Re: HTTP/2 frame prioritization not honored

> Am 17.01.2017 um 20:52 schrieb Kyriakos Zarifis : > > Hi Stefan, > > Sorry for the delay, I just got back from traveling. I just tried your new > patch and indeed it gets rid of the 100ms delay: The server now serves the > high priority object only ~5-20ms (did a few