Le 30/04/2025 à 5:12 PM, Ionel GARDAIS a écrit :
Hi,
For technical showoff, I was using the fcgi-app feature to serve PHP FPM
websites (matomo and a planning portal) but with the 3.0.10 update, haproxy
starts using 100% cpu and requests ended in timeout.
PHP-FPM did not logged anything.
Unfortunately I had to revert quickly to a more academic use of fpm inside an
nginx server and I did not generate dump.
The relevant configuration bits are :
acl is-php path_reg ^/.+\.php(/.*)?
acl is-php path /
use_backend bck-matomo if host-matomo is-php
default_backend bck-nginx
backend bck-matomo
use-fcgi-app fpm-matomo
server fpm-matomo 127.0.0.1:8081 proto fcgi
fcgi-app fpm-matomo
log-stderr global
docroot /opt/matomo
index index.php
path-info ^(/.+\.php)(/.*)?$
Beside Christopher's commit 'BUG/MEDIUM: mux-fcgi: Properly handle read0 on
partial record', I've just noticed that the fcgi-app section name is the same
that the server name declared in the backend.
Are there obvious misconfiguration that could have break things between 3.0.9
and 3.0.10 ?
Thanks!
I can confirm there is an issue. After a bisect, I found the offending commit is
indeed "BUG/MEDIUM: mux-fcgi: Properly handle read0 on partial records". I will
review it because on 3.1 and 3.2, there is no issue.
--
Christopher Faulet
