https://bz.apache.org/bugzilla/show_bug.cgi?id=58488
--- Comment #2 from [email protected] --- Of course Luca, httpd version was 2.4.9, you can repro the bug in a configuration with at least two PHP-FPM pools backends and a apache frontend communicating over UDS. Configuration is something like this: <VirtualHost *:80> ServerName poolA.test.com DocumentRoot "/opt/poolA/htdocs/" <Proxy "unix:/dev/shm/poolA.sock|fcgi://php-fpm-poolA.local"> ProxySet min=0 ProxySet acquire=20 ProxySet connectiontimeout=100ms ProxySet retry=0 ProxySet timeout=300 Require all granted </Proxy> # Sintaxis 2.4.10 <FilesMatch \.php$> SetHandler "proxy:fcgi://php-fpm-poolA.local" Require all granted </FilesMatch> RedirectMatch ^/$ /index.php </VirtualHost> <VirtualHost *:80> ServerName poolB.test.com DocumentRoot "/opt/poolB/htdocs/" <Proxy "unix:/dev/shm/poolB.sock|fcgi://php-fpm-poolB.local"> ProxySet min=0 ProxySet acquire=20 ProxySet connectiontimeout=100ms ProxySet retry=0 ProxySet timeout=300 Require all granted </Proxy> # Sintaxis 2.4.10 <FilesMatch \.php$> SetHandler "proxy:fcgi://php-fpm-poolB.local" Require all granted </FilesMatch> RedirectMatch ^/$ /index.php </VirtualHost> So, you can shutdown one of the PHP-FPM pools, by example poolB, killing their FPM processes, and inject requests to both pools, the active pool poolA responds, and the no active pool, poolB, returns 503 errors. But if you persist the requests to both pool, then sometime crash happens and both pools fails. I have observed this behavior in a production system with high load in a pool with we have shutdowned for maintenance and then past a time, the other pools have begun these failures, so, instead of a simple shutdown, we had to set up a maintenance page. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
