Re: rabbitmq behind apache / mod_rewrite

33 schrieb Stefan Priebe - Profihost AG: > Hi, > > i'm trying to run the webgui of rabbitmq behind apache proxy while using > mod_rewrite. > > RabbitMQ generates URLs like: > http://rabbit.example.com/#/queues/%2F/myqueue > > but those always generate a 404 >

rabbitmq behind apache / mod_rewrite

Hi, i'm trying to run the webgui of rabbitmq behind apache proxy while using mod_rewrite. RabbitMQ generates URLs like: http://rabbit.example.com/#/queues/%2F/myqueue but those always generate a 404 What i tried is: AllowEncodedSlashes NoDecode or Yes RewriteRule ^/?rabbitmq/(.*)$

Apache 0-day / apache-uaf / use after free bugs

Hi, in twitter and other social media channels they're talking about a current apache 0 day: https://twitter.com/i/web/status/1087593706444730369 which wasn't handled / isn't currently fixed. Some details are here: https://github.com/hannob/apache-uaf If this is true there will be exploits

Re: https vhosts

Hi Stefan, as i've tried todo nearly the same some weeks ago i can tell you what i did. Comment inline. Am 24.05.2018 um 13:34 schrieb Stefan Eissing: > So, we are lacking an option here to abort SSL connections without a vhost > match, it seems. Something like > > SSLStrictSNIVHostCheck

Re: Http2 stats into mod_systemd

Am 04.04.2018 um 11:59 schrieb Stefan Eissing: > >> Am 30.03.2018 um 19:20 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Hi Stefan, >> >> would it be possible to add some http2 stats into mod_systemd status? > > S

Http2 stats into mod_systemd

Hi Stefan, would it be possible to add some http2 stats into mod_systemd status? Greets, Stefan Excuse my typo sent from my mobile phone.

Re: build mod_systemd static

Am 27.03.2018 um 13:52 schrieb Eric Covener: > On Tue, Mar 27, 2018 at 7:45 AM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> Hello, >> >> i've backported mod_systemd to httpd 2.4 which was / is very straight >> forward. >> >>

build mod_systemd static

Hello, i've backported mod_systemd to httpd 2.4 which was / is very straight forward. Now i would like to build mod_systemd statically but don't get it. While --enable-unixd=static work fine --enable-systemd=static still builds it as a shared module. Any hints? Greets, Stefan

Re: Apache server-status Monitoring / why is it only available through http?

might this be something - where mod_systemd can be extended? I have never used it but it already seems to provide some stats. Am 26.03.2018 um 12:17 schrieb Stefan Priebe - Profihost AG: > > Am 24.03.2018 um 15:28 schrieb Eric Covener: >> On Sat, Mar 24, 2018 at 10:18 AM, S

Re: Apache server-status Monitoring / why is it only available through http?

Am 24.03.2018 um 15:28 schrieb Eric Covener: > On Sat, Mar 24, 2018 at 10:18 AM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> Hello, >> >> is there any reason why the srever-status output isn't: >> - available through a local unix

Apache server-status Monitoring / why is it only available through http?

Hello, is there any reason why the srever-status output isn't: - available through a local unix socket - so you can grab it even all workers are busy - available in a machine readable format even it might be csv... Thanks! Greets, Stefan

Re: apache 2.4.29: mod_http2 stucks from time to time

Hello, here is the relevant commit: https://github.com/icing/mod_h2/commit/51085e0c26da1f47ea9cf91930af8cef0dececb9 Stefan Excuse my typo sent from my mobile phone. > Am 02.12.2017 um 14:39 schrieb Stefan Priebe - Profihost AG > <s.pri...@profihost.ag>: > > Hello Luca, &

Re: apache 2.4.29: mod_http2 stucks from time to time

cano.l...@gmail.com>: > > Hi everybody, > > did I miss an update or are we still waiting for more data? (Don't mean to > rush you Stefan, just to understand what's the status of the thread :) > > Luca > > 2017-11-24 15:26 GMT+01:00 Stefan Priebe - Profihost AG >

Re: apache 2.4.29: mod_http2 stucks from time to time

checked, in case that interferes here. > > Cheers, > > Stefan > > > > >> Am 23.11.2017 um 14:16 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Hi, >>> Am 23.11.2017 um 14:10 schrieb Stefan Eissing: &

Re: apache 2.4.29: mod_http2 stucks from time to time

times. > We are not ghosted by some strange blabla-lake hyper threading thingie > singularity? Huhoh what's that? Any chance to add some more debugging? Greets, Stefan > > Need to think about this. > >> Am 23.11.2017 um 13:43 schrieb Stefan Priebe - Profihost AG

Re: apache 2.4.29: mod_http2 stucks from time to time

*argh*, i was too fast no it did NOT fix the problem. It even happens with: H2MaxWorkers4096 Sorry about that. Stefan Am 23.11.2017 um 13:42 schrieb Stefan Priebe - Profihost AG: > Hello,, > > setting: > H2MaxWorkers1024 > > fixes the issue for me. The main proble

Re: apache 2.4.29: mod_http2 stucks from time to time

Hello,, setting: H2MaxWorkers1024 fixes the issue for me. The main problem is how to i know how many workers are needed? How can i detect whether all workers of h2 are busy? Stefan Am 22.11.2017 um 13:23 schrieb Stefan Priebe - Profihost AG: > Hell Stefan, > > will send a l

Re: apache 2.4.29: mod_http2 stucks from time to time

Hell Stefan, will send a log to you in a few seconds via private email. Greets, Stefan Am 21.11.2017 um 23:18 schrieb Stefan Eissing: > sorry for the late reply. for stucks trace2 is best. > >> Am 21.11.2017 um 19:35 schrieb Stefan Priebe - Profihost AG >> <

Re: apache 2.4.29: mod_http2 stucks from time to time

Hello Stefan, which loglevel do you need? trace2? Greets, Stefan Am 21.11.2017 um 16:48 schrieb Stefan Eissing: > Never done this, but https://www.howtoforge.com/setenvif_apache2 seems like > one way to do make it work. > >> Am 21.11.2017 um 16:16 schrieb Stefan Priebe

Re: apache 2.4.29: mod_http2 stucks from time to time

Am 21.11.2017 um 16:06 schrieb Stefan Priebe - Profihost AG: > Am 21.11.2017 um 15:45 schrieb Stefan Eissing: >> >>> Am 21.11.2017 um 14:33 schrieb Stefan Priebe - Profihost AG >>> <s.pri...@profihost.ag>: >>> >>> Hello Stefan, >>>

Re: apache 2.4.29: mod_http2 stucks from time to time

Am 21.11.2017 um 15:45 schrieb Stefan Eissing: > >> Am 21.11.2017 um 14:33 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Hello Stefan, >> Hello Yann, >> >> me the http2 bug tester is calling again ;-) > >

apache 2.4.29: mod_http2 stucks from time to time

Hello Stefan, Hello Yann, me the http2 bug tester is calling again ;-) We've the problem "most probably" since apadhe 2.4.29 that http2 stucks from time to time. While running two bash curl while loops the one using http1.1 always finishes in < 0.05s while the http2 one takes sometimes 0.4 to

Re: We have soon 5 SVN repo's

> Am 04.11.2017 um 11:03 schrieb Steffen : > > Soon we have: > > branches 2.4.x > trunk > 2.5.0-alpha > patches/2.4.x > patches/trunk > > Please a procedure: where and when do we apply patches/fixes. > Why don‘t move to git? Greets, Stefan Excuse my typo sent from

Re: Time for 2.4.28 ?

> Am 19.09.2017 um 15:50 schrieb Jacob Perkins : > > > >> On Sep 18, 2017, at 11:24 AM, Jim Jagielski wrote: >> >> Seems like a good time to push for a 2.4.28 T by end-of-week. >> Review STATUS! Test and Vote on backports! >> >> Comments? Do we

implement multiple AuthType's

Hello, would it be possible to implement multiple AuthType's? I know that this is not possible in all cases but it would be great to be able have a fallback. For example: Having GSSAPI Auth in the first place and if the browser does not send a valid ticket fallback to other auth systems like

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

4tr i was able to fix this by mod_h2 v1.10.10 Greets, Stefan Am 25.07.2017 um 15:40 schrieb Stefan Eissing: > Well, if the customer could reproduce this at a > > LogLevel http2:trace2 > > that would help. > >> Am 25.07.2017 um 15:38 schrieb Stefan Priebe -

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

ch that i hope addresses the problem. The 2.4.x version I attach > to this mail. > > Thanks! > > Stefan > > > > > >> Am 25.07.2017 um 08:13 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> >> Am 24.07

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

sing and the connection results in >> ERR_CONNECTION_CLOSED after 60s. What kind of details do you need? >> >> Greets, >> Stefan >>> Am 22.07.2017 um 13:35 schrieb Yann Ylavic: >>>> On Sat, Jul 22, 2017 at 2:18 AM, Yann Ylavic <ylavic@gmail.com> w

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

13:35 schrieb Yann Ylavic: > On Sat, Jul 22, 2017 at 2:18 AM, Yann Ylavic <ylavic@gmail.com> wrote: >> On Fri, Jul 21, 2017 at 10:31 PM, Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag> wrote: >>> >>> your new defer linger V3 dead

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

@gmail.com> wrote: >> On Fri, Jul 21, 2017 at 10:31 PM, Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag> wrote: >>> >>> your new defer linger V3 deadlocked as well. >>> >>> GDB traces: >>> https://www.apaste.info/

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

, Stefan Am 21.07.2017 um 01:08 schrieb Yann Ylavic: > On Thu, Jul 20, 2017 at 12:48 PM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> V3 didn't help. > > I just posted a new patch in this thread, with a new approach which I > think is better anyway.

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

Hello Yann, i downloaded V3. Can't guarantee when i can test. May be today or on monday. Greets, Stefan Am 21.07.2017 um 01:08 schrieb Yann Ylavic: > On Thu, Jul 20, 2017 at 12:48 PM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> V3 didn't help. > > I

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

8192 0 5 4294967283 Sum 7 025 38 1362 0 10 -3489 Stefan Excuse my typo sent from my mobile phone. > Am 20.07.2017 um 15:18 schrieb Yann Ylavic <ylavic@gmail.com>: > > On Thu, Jul 20, 2017 at 2:58 PM, Stefan Priebe

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

Yes it looks the same but I can't tell if it is. Here's a backtrace from V3: https://apaste.info/Aw0r Greets, Stefan Excuse my typo sent from my mobile phone. > Am 20.07.2017 um 13:01 schrieb Yann Ylavic <ylavic@gmail.com>: > > On Thu, Jul 20, 2017 at 12:48 PM, Stefan Pri

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

V3 didn't help. Will post a new gdb backtrace soon takes some time as I'm on holiday. Stefan Excuse my typo sent from my mobile phone. > Am 20.07.2017 um 01:26 schrieb Yann Ylavic <ylavic@gmail.com>: > > On Wed, Jul 19, 2017 at 11:14 PM, Stefan Priebe - Profih

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

Am 20.07.2017 um 01:26 schrieb Yann Ylavic: > On Wed, Jul 19, 2017 at 11:14 PM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> Am 19.07.2017 um 22:46 schrieb Yann Ylavic: >>> >>> Attached is a v2 if you feel confident enough, still ;) &

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

Am 19.07.2017 um 22:46 schrieb Yann Ylavic: > Hi Stefan, > > thanks for testing again! > > On Wed, Jul 19, 2017 at 7:42 PM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> >> What looks strange >> from a first view is that async connec

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

> > Am 19.07.2017 um 16:59 schrieb Stefan Priebe - Profihost AG: > > Hello Yann, > > > > i'm observing some deadlocks again. > > > > I'm using > > httpd 2.4.27 > > + mod_h2 > > + httpd-2.4.x

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

22 -150 Greets, Stefan Am 19.07.2017 um 17:48 schrieb Luca Toscano: > Hello Stefan, > > 2017-07-19 17:05 GMT+02:00 Stefan Priebe - Profihost AG > <s.pri...@profihost.ag <mailto:s.pri...@profihost.ag>>: > > > Am 19.07.2017 um 16:59 schrieb Stefan Pr

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

2198 0 2 4294966949 Sum 28020 10 5590 0 8 -16400 Greets, Stefan Am 19.07.2017 um 17:05 schrieb Stefan Priebe - Profihost AG: > > Am 19.07.2017 um 16:59 schrieb Stefan Priebe - Profihost AG: >> Hello Yann, >> >

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

Am 19.07.2017 um 16:59 schrieb Stefan Priebe - Profihost AG: > Hello Yann, > > i'm observing some deadlocks again. > > I'm using > httpd 2.4.27 > + mod_h2 > + httpd-2.4.x-mpm_event-wakeup-v7.1.patch > + your ssl linger fix patch from this thread > > What kind o

Re: [Bug 60956] Event MPM listener thread may get blocked by SSL shutdowns

Hello Yann, i'm observing some deadlocks again. I'm using httpd 2.4.27 + mod_h2 + httpd-2.4.x-mpm_event-wakeup-v7.1.patch + your ssl linger fix patch from this thread What kind of information do you need? If you need a full stack backtrace - from which pid? Or from all httpd pids? Thanks!

Apache 2.4.26 mpm_event_listener_wakeup_bug57399_V7

Hello Yann, is your wakeup patch (mpm_event_listener_wakeup_bug57399_V7) still needed for 2.4.26? Greets, Stefan

Re: The drive for 2.4.26

Hi Luca, Am 27.05.2017 um 09:10 schrieb Luca Toscano: > Hi Jim, > > 2017-05-25 14:23 GMT+02:00 Jim Jagielski >: > > Until a proposal in in STATUS (and apologies if it is), its > suitability for 2.4.x is a big unknown. > > > you are

VUDDY: unpatched CVEs in apache httpd

Hello list, while reading "http://www.ieee-security.org/TC/SP2017/papers/71.pdf; they claim to have found unpatched security holes in apache httpd. While reading further it seems that the only missing peace is the unpatched xmlparse from expat. While searching on our build server it turns out to

Re: hanging apache httpd processes due to mod_h2

looks good so war. Will wait some more days. Greets, Stefan Am 19.04.2017 um 11:09 schrieb Stefan Eissing: > Thanks, the backtraces really helped. Could you try the following patch? > > -Stefan > > > > >> Am 19.04.2017 um 08:32 schrieb Stefan Priebe - Profihost AG

Re: hanging apache httpd processes due to mod_h2

thread is: Thread 6 Greets, Stefan Am 18.04.2017 um 15:06 schrieb Stefan Priebe - Profihost AG: > > Am 18.04.2017 um 15:03 schrieb Stefan Eissing: >> Stefan, >> >> that is a 1.10.0, right? That was the first version without nested locking >> and I fixed 2 possible dea

Re: hanging apache httpd processes

nt omitting EOF flags. Could you give that one a try? Yes sure where is 1.10.2? Stefan > > -Stefan > >> Am 18.04.2017 um 14:57 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Hi, >> >> i saw that all of them are still s

Re: hanging apache httpd processes

6> opt_arg = 0x7ffda735eef1 "FOREGROUND" signal_server = 0xfe00 Greets, Stefan Am 18.04.2017 um 14:47 schrieb Eric Covener: > On Tue, Apr 18, 2017 at 8:43 AM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> bt of such a

hanging apache httpd processes

Hi, not sure whether this is related to mod_http2 v1.10.0 or is something else. I've seen two servers where old httpd processes get stuck. server-status looks like this: SlotPID StoppingConnections Threads Async connections total accepting busyidlewriting

Re: Apache 2.4.26 AH: scoreboard is full, not at MaxRequestWorkers.Increase,ServerLimit

Hi, Am 16.03.2017 um 18:05 schrieb Luca Toscano: > > > 2017-03-16 15:24 GMT+01:00 Stefan Priebe - Profihost AG > <s.pri...@profihost.ag <mailto:s.pri...@profihost.ag>>: > > Hi, > > Am 16.03.2017 um 12:26 schrieb Luca Toscano: > > Hi Stefa

Re: Apache 2.4.26 AH: scoreboard is full, not at MaxRequestWorkers.Increase,ServerLimit

Hi, Am 16.03.2017 um 12:26 schrieb Luca Toscano: > Hi Stefan, > > 2017-03-16 12:14 GMT+01:00 Stefan Priebe - Profihost AG > <s.pri...@profihost.ag <mailto:s.pri...@profihost.ag>>: > > Hi Yann, > > no sure whether this is due to your mpm event pat

Apache 2.4.26 AH: scoreboard is full, not at MaxRequestWorkers.Increase,ServerLimit

Hi Yann, no sure whether this is due to your mpm event patch. >From time to time i see the following error mesages in my logs and the only chance to fix it is to restart apache. [Thu Mar 16 01:00:35.445184 2017] [mpm_event:error] [pid 27485:tid 140212799559552] AH: scoreboard is full, not at

Re: mod_http2 v1.9.3

from /lib/x86_64-linux-gnu/libc.so.6 Stefan Am 12.03.2017 um 19:53 schrieb Stefan Priebe - Profihost AG: > Thanks. Installed. > > Greets, > Stefan > Am 12.03.2017 um 15:58 schrieb Stefan Eissing: >> Stefan, >> >> I would be very interested in hearing how v1.9.3 f

Re: mod_http2 v1.9.3

Thanks. Installed. Greets, Stefan Am 12.03.2017 um 15:58 schrieb Stefan Eissing: > Stefan, > > I would be very interested in hearing how v1.9.3 fares in your environment: > - I found and fixed a race in connection shutdown that could potentially > explain your sometimes observed crashes > - I

Re: release v1.9.2

to keep looking... May be Yann has an idea? May be it's not related to http2 at all? Stefan >> Am 09.03.2017 um 17:32 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Hi Stefan, >> >> while doing longer testing i can say that also

Re: release v1.9.2

Hi Stefan, while doing longer testing i can say that also the version which was working for 4 days segfaults. So it was never solved ;-( Sorry about that. Testing was just too short. Greets, Stefan Am 05.03.2017 um 14:49 schrieb Stefan Priebe - Profihost AG: > Hi Stefan, > > yes t

Re: release v1.9.2

this correct? > >> Am 04.03.2017 um 22:34 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Hi Stefan, >> >> current trace - not sure whether this is http2 related at all: >> >> Core was generated by `/usr/local/apache/bi

Re: release v1.9.2

/lib/x86_64-linux-gnu/libc.so.6 Stefan Am 03.03.2017 um 21:02 schrieb Stefan Priebe - Profihost AG: > Hi Stefan, > > live. Sorry for the late reply. > > Stefan > > Am 28.02.2017 um 11:49 schrieb Stefan Eissing: >> Meh, my mistake. Sorry about that. Did not

Re: release v1.9.2

Hi Stefan, live. Sorry for the late reply. Stefan Am 28.02.2017 um 11:49 schrieb Stefan Eissing: > Meh, my mistake. Sorry about that. Did not cleanup properly. Dare you with an > improved version: > > > > > >> Am 28.02.2017 um 08:41 schrieb Stefan Prieb

Re: release v1.9.2

> Damnit. Can you try the attached patch on top of mod_http2 v1.9.2? This one > sets a mutex on the main connection allocator if missing and is pretty close > to the version we ran successfully with on your site for days. > > Thanks again! > > -Stefan > > > &g

Re: release v1.9.2

om /lib/x86_64-linux-gnu/libc.so.6 (gdb) (gdb) quit Stefan Am 26.02.2017 um 19:46 schrieb Stefan Priebe - Profihost AG: > Hi Stefan, > > currently everything fine. No segfaults. > > Stefan > > Am 25.02.2017 um 20:40 schrieb Stefan Priebe - Profihost AG: >> Hi Stefan, &

Re: release v1.9.2

Hi Stefan, currently everything fine. No segfaults. Stefan Am 25.02.2017 um 20:40 schrieb Stefan Priebe - Profihost AG: > Hi Stefan, > Am 25.02.2017 um 13:51 schrieb Stefan Eissing: >> Stefan, >> >> whenever you have time, please deploy >> https://github.com/ic

Re: release v1.9.0

round between placing that on the main conn (as we had > in the crash free version) and 1.9.1 behaviour. Thanks! done. But please keep in mind that this crash might be very rare and might even have happened with v1.9.0 if we've waited more time. Greets, Stefan > -Stefan > >> Am 24.02

Re: release v1.9.0

Hi Yann, here we go: (gdb) p *ipsub $1 = {family = 2, sub = {1367753145, 0, 0, 0}, mask = {4294967295, 4294967295, 4294967295, 4294967295}} (gdb) p *sa $2 = {pool = 0x10b500c4ff0b0a, hostname = 0x503040203030102 , servname = 0x17d01040405 , port = 770, family = 554829073, salen =

Re: release v1.9.0

No we don't use IPv6 at all. Do you still need those values? Greets, Stefan Excuse my typo sent from my mobile phone. > Am 24.02.2017 um 14:18 schrieb Yann Ylavic : > > Hi Stefan (Priebe), > > Is IPv6 (really) involved in your network? > > Could you please show up the

Re: release v1.9.0

in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #13 0x7f459649662d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Stefan Am 23.02.2017 um 07:59 schrieb Stefan Priebe - Profihost AG: > Am 22.02.2017 um 12:22 schrieb Yann Ylavic: >> Hi Stefan, >> >> On Wed, Feb

Re: release v1.9.0

Am 22.02.2017 um 12:22 schrieb Yann Ylavic: > Hi Stefan, > > On Wed, Feb 22, 2017 at 11:32 AM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> >> @Yann how should i test? Vanilla 2.4.25 + MPM V7 + mod_http2 v1.9.1? > > Yes, I think this is th

Re: release v1.9.0

1.02.2017 um 09:40 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Hi Yann, >> >> Am 20.02.2017 um 16:38 schrieb Yann Ylavic: >>> On Wed, Feb 15, 2017 at 8:53 PM, Stefan Priebe - Profihost AG >>> <s.pr

Re: release v1.9.0

Hi, Am 16.02.2017 um 11:39 schrieb Stefan Eissing: > >> Am 15.02.2017 um 20:53 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Hi, >> >> still no segfaults. > > My heart sings with joy. Can you keep on sending that messa

Re: release v1.9.0

Hi, still no segfaults. @Yann Are those patches (the addon on top of v7) and the one on top of mod_ssl still correct / needed? Stefan Am 15.02.2017 um 12:45 schrieb Stefan Priebe - Profihost AG: > Hi, > Am 15.02.2017 um 12:19 schrieb Yann Ylavic: >> Hi Stefan, >> >> O

Re: release v1.9.0

Hi, Am 15.02.2017 um 12:19 schrieb Yann Ylavic: > Hi Stefan, > > On Wed, Feb 15, 2017 at 9:34 AM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> Current status: no segfaults. > > Is this with or without the mpm_event's wakeup a

Re: release v1.9.0

Current status: no segfaults. Am 14.02.2017 um 19:59 schrieb Stefan Priebe - Profihost AG: > Hi, > > up and running - Thanks! > > Greets, > Stefan > > Am 14.02.2017 um 17:05 schrieb Stefan Eissing: >> Stefan, >> >> if you'd like, please throw >&

Re: release v1.9.0

Hi, up and running - Thanks! Greets, Stefan Am 14.02.2017 um 17:05 schrieb Stefan Eissing: > Stefan, > > if you'd like, please throw > https://github.com/icing/mod_h2/releases/tag/v1.9.0 > into your pit of segfaults and let's see if we find a new one! > > Many thanks for testing. > > Stefan

Re: mod_http2 and Frequent wake-ups for mpm_event

> Hope to give you something better to verify in your environment soon. Just tell me i'm ready to test. Greets, Stefan > Cheers, > > Stefan > >> Am 07.02.2017 um 20:56 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Hi, >> &

Re: mod_http2 and Frequent wake-ups for mpm_event

/x86_64-linux-gnu/libc.so.6 Am 06.02.2017 um 22:24 schrieb Stefan Priebe - Profihost AG: > Am 06.02.2017 um 22:22 schrieb Stefan Priebe - Profihost AG: >> Hi Stefan, >> >> this one does not apply on top of yann's >> mpm_event_listener_wakeup_bug57399_V7.patch patch. &

Re: mod_http2 and Frequent wake-ups for mpm_event

Am 06.02.2017 um 22:22 schrieb Stefan Priebe - Profihost AG: > Hi Stefan, > > this one does not apply on top of yann's > mpm_event_listener_wakeup_bug57399_V7.patch patch. i've now used his patch to mpm and yours for mod_http2. Stefan > > Stefan > Am 06.02.2017 um 15:34 s

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi Stefan, this one does not apply on top of yann's mpm_event_listener_wakeup_bug57399_V7.patch patch. Stefan Am 06.02.2017 um 15:34 schrieb Stefan Eissing: > Yes, that was mixing the order. The attached v4 compiles and runs the h2 > tests for me without errors. > > > > > >> Am 06.02.2017

Re: mod_http2 and Frequent wake-ups for mpm_event

Am 06.02.2017 um 16:06 schrieb Stefan Eissing: > It does, at the end. Traversed the directories in different order it seems. *arg* sorry > >> Am 06.02.2017 um 16:05 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Am 06.02.2017 um 16:0

Re: mod_http2 and Frequent wake-ups for mpm_event

; -Stefan > >> Am 06.02.2017 um 15:41 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Hi, >> >> so i should test the mpm event part from Yann + your http2 part? >> >> Stefan >> >> Am 06.02.2017 um 15:34 schrie

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi, so i should test the mpm event part from Yann + your http2 part? Stefan Am 06.02.2017 um 15:34 schrieb Stefan Eissing: > Yes, that was mixing the order. The attached v4 compiles and runs the h2 > tests for me without errors. > > > > > >> Am 06.02.2017 um 14:43 schrieb Yann Ylavic

Re: mod_http2 and Frequent wake-ups for mpm_event

Am 06.02.2017 um 11:56 schrieb Yann Ylavic: > Hi Stefan, > > On Mon, Feb 6, 2017 at 9:57 AM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> >> your last patch results in multiple crashes every second: > > Sorry about that, the changes in

Re: mod_http2 and Frequent wake-ups for mpm_event

, dummy=0x547d8caf3534b) at event.c:1837 #5 0x7f2bc8ff20a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f2bc8d2762d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Stefan Am 06.02.2017 um 09:33 schrieb Stefan Priebe - Profihost AG: > Hallo, > > up an

Re: mod_http2 and Frequent wake-ups for mpm_event

Hallo, up and running (apache 2.4.25 + mpm_event V7 + mpd_http2 v1.8.11 + mod_ssl patch + your new allocator patch). Will report back. Greets, Stefan Am 06.02.2017 um 01:19 schrieb Yann Ylavic: > Hi Stefan, > > On Sun, Feb 5, 2017 at 7:51 PM, Stefan Priebe - Profihost AG

Re: mod_http2 and Frequent wake-ups for mpm_event

avic: > Hi Stefan, > > On Tue, Jan 31, 2017 at 4:01 PM, Stefan Priebe - Profihost AG > <s.pri...@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.

Re: mod_http2 and Frequent wake-ups for mpm_event

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.pri...@profihost.ag> wrote: >> >> any ideas? > > I wonder if the attached patch (related to mod_ssl and proposed for > another s

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi Yann, Hi Stefan, any ideas? Stefan Am 27.01.2017 um 20:30 schrieb Ruediger Pluem: > > > On 01/27/2017 08:10 PM, Stefan Priebe - Profihost AG wrote: >> Hi Yann, >> >> this is now a segfault with mod_http2 + beam v4 patch + mpm v7 patch: >> Progr

Re: mod_http2 and canceled requests logs status 500 internal server error code

helps. thanks will report back most probably on monday. Stefan > Cheers, Stefan > >> Am 26.01.2017 um 16:36 schrieb Stefan Eissing <stefan.eiss...@greenbytes.de>: >> >> Hi, will do that tomorrow. >> >>> Am 26.01.2017 um 16:35 schrieb Stefan Priebe -

Re: mod_http2 and Frequent wake-ups for mpm_event

:10 schrieb Stefan Priebe - Profihost AG: > Am 25.01.2017 um 10:46 schrieb Stefan Eissing: >> Thanks Yann! >> >> Stefan: here is the patch as committed to trunk: > > Up and running. Will report back. > >> >> >> Cheers, Stefan >> >>> A

Re: mod_http2 and canceled requests logs status 500 internal server error code

Hi Stefan, did you already had the time to look at the 500 status code in case of canceled requests? Stefan Am 25.01.2017 um 15:55 schrieb Stefan Priebe - Profihost AG: > > Am 25.01.2017 um 15:50 schrieb Stefan Eissing: >> >>> Am 25.01.2017 um 15:31 schrieb Stefan

Re: mod_http2 and canceled requests logs status 500 internal server error code

Hi, Am 25.01.2017 um 15:59 schrieb Eric Covener: > On Wed, Jan 25, 2017 at 9:55 AM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> I also saw some more entries with 0 byte size in logs if there is no >> body. http/1.1 logs the header size as well. &g

Re: mod_http2 and canceled requests logs status 500 internal server error code

Am 25.01.2017 um 15:50 schrieb Stefan Eissing: > >> Am 25.01.2017 um 15:31 schrieb Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag>: >> >> Chrome docs says: >> >> "cancelled / net::ERR_ABORTED is intended to only be generated whe

Re: mod_http2 and canceled requests logs status 500 internal server error code

it's just wrong that mod_http2 generates a 500 in the logs. Stefan Am 25.01.2017 um 15:27 schrieb Stefan Priebe - Profihost AG: > Am 25.01.2017 um 14:57 schrieb Yann Ylavic: >> Hi, >> >> On Wed, Jan 25, 2017 at 2:46 PM, Stefan Priebe - Profihost AG >> <s.pri...@pr

Re: mod_http2 and canceled requests logs status 500 internal server error code

Am 25.01.2017 um 14:57 schrieb Yann Ylavic: > Hi, > > On Wed, Jan 25, 2017 at 2:46 PM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> >> Is this a bug or a feature? Is it correct that it logs a 500 code? > > ErrorLog's file should tell more

mod_http2 and canceled requests logs status 500 internal server error code

Hello, while digging through some apache logfiles i saw some strange entries: "GET URL HTTP/2.0" 500 0 They all had a 500 status error code and a size of 0. I'm able to reproduce them while clicking fast on a php site. For each log line with status code 500 i get a STATUS (canceled) in my

Re: mod_http2 and Frequent wake-ups for mpm_event

Am 25.01.2017 um 10:46 schrieb Stefan Eissing: > Thanks Yann! > > Stefan: here is the patch as committed to trunk: Up and running. Will report back. > > > Cheers, Stefan > >> Am 25.01.2017 um 01:41 schrieb Yann Ylavic : >> >> Hi Stefan, >> >> On Tue, Jan 24, 2017 at

Re: mod_http2 and Frequent wake-ups for mpm_event

Hi Yann, Am 25.01.2017 um 01:41 schrieb Yann Ylavic: > Hi Stefan, > > On Tue, Jan 24, 2017 at 1:37 PM, Stefan Eissing > wrote: >> Yann, thanks for the patch. I agree that the cleanups need to be killed in >> the right place. Not certain if it was wrong before, but

Re: mod_http2 and Frequent wake-ups for mpm_event

Am 24.01.2017 um 14:22 schrieb Yann Ylavic: > On Tue, Jan 24, 2017 at 10:02 AM, Stefan Priebe - Profihost AG > <s.pri...@profihost.ag> wrote: >> >> Am 23.01.2017 um 23:42 schrieb Yann Ylavic: >>> On Mon, Jan 23, 2017 at 11:37 PM, Yann Ylavic <ylavic.

Re: mod_http2 and Frequent wake-ups for mpm_event

Am 23.01.2017 um 23:42 schrieb Yann Ylavic: > On Mon, Jan 23, 2017 at 11:37 PM, Yann Ylavic wrote: >> Hi Stefan, >> >> On Mon, Jan 23, 2017 at 9:54 PM, Stefan Eissing >> wrote: >>> >>> I am not aware of any special expectations now. Almost all

Re: mod_http2 and Frequent wake-ups for mpm_event

Am 23.01.2017 um 21:54 schrieb Stefan Eissing: > >> Am 22.01.2017 um 22:22 schrieb Yann Ylavic : >> >> @icing: Any special expectation in mod_h2 with regard to mpm workers >> threads' lifetime (or keepalive connections that should stay alive for >> the configured limit)? >>

  1   2   >