[users@httpd] [Request received] users Digest 20 Dec 2021 00:26:58 -0000 Issue 6224

##- Please type your reply above this line -## Hi Users, Season’s Greetings from Coin Master Support! We received your message and we’ll get back to you as soon as possible. This holiday season we’re experiencing a higher volume of requests than usual, so it may take us a bit longer to

[users@httpd] [Request received] users Digest 19 Dec 2021 21:37:09 -0000 Issue 6223

##- Please type your reply above this line -## Hi Users, Season’s Greetings from Coin Master Support! We received your message and we’ll get back to you as soon as possible. This holiday season we’re experiencing a higher volume of requests than usual, so it may take us a bit longer to

Re: [users@httpd] MPM event unstable behind AWS ALB

I'm a beginner but I did install fpm to see how it works. Did you set the fpm acces logs? ; The access log file ; Default: not set access.log = "/usr/local/etc/php/8.0/log/www.access.log" And the status page? ; The URI to view the FPM status page. If this value is not set, no URI

Re: [users@httpd] MPM event unstable behind AWS ALB

Yeah the 408 is not easy to troubleshoot it might be anything from malformed HTTP header and slow client (i.e. legit DoS attack where a malicious client sends the headers and then delais sending the request body in order to keep the connection open and exhaust server side resources) to a legit

Re: [users@httpd] MPM event unstable behind AWS ALB

Also worth noting that Nginx OS does not experience the issues (otherwise same setup)... Dan On Mon, Dec 20, 2021 at 10:58 AM Dan Washusen wrote: > Yeah, all those parameters are configured and everything works fine when I > switch to the MPM worker module. The 408 errors are returned by

Re: [users@httpd] MPM event unstable behind AWS ALB

Yeah, all those parameters are configured and everything works fine when I switch to the MPM worker module. The 408 errors are returned by Jetty and ProxyPass is configured to not reuse connections (which seems to suggest not a KeepAlive issue), Jetty is erroring because it receives no request

Re: [users@httpd] MPM event unstable behind AWS ALB

I will still say this is a timeout issue. Set the ALB timeout to 3600 which is the max possible in case you do not know where to start from. I guess you already have ALB logs enabled. In apache check the KeepAliveTimeout, RequestReadTimeout and ProxyTimeout and make sure they make sense for your

Re: [users@httpd] MPM event unstable behind AWS ALB

Thanks for the response. Timeouts are configured appropriately... To clarify; everything works fine through a TCP Network Load Balancer pointing at the same infrastructure. There is something about having a HTTP based Application Load Balancer in front of an MPM event configuration that's causing

Re: [users@httpd] MPM event unstable behind AWS ALB

In a proxy chains like this getting the timeouts in sync is the most important thing. Make sure that you have done that. On Mon, 20 Dec 2021, 08:37 Dan Washusen, wrote: > Hi All, > I've been experimenting with the MPM event module with Apache instances > sitting behind an AWS Application Load

[users@httpd] MPM event unstable behind AWS ALB

Hi All, I've been experimenting with the MPM event module with Apache instances sitting behind an AWS Application Load Balancer (ALB) and it really doesn't seem to be working well. Response times shoot up (compared to MPM event worker) and we see a fair few 502 errors returned (by the AWS ALB.