On a openSUSE Tumbleweed 20210111 test system I evaluate Nextcloud 20. The problem is that even the test system with only one user and only very few files gets ressource problems. Directly after Nextcloud login (with pm.max_children=10) or some minutes later (with pm.max_children=50), PHP-FPM gets stuck. The Nextcloud browser window is open, but idle.
I already found, that the number of active PHP-FPM processes is constantly growing. http://localhost/status currently shows 19 active processes:
pool: www process manager: dynamic start time: 14/Jan/2021:23:59:47 +0100 start since: 36467 accepted conn: 714 listen queue: 0 max listen queue: 0 listen queue len: 0 idle processes: 1 active processes: 19 total processes: 20 max active processes: 28 max children reached: 0 slow requests: 0
If I close the Nextcloud browser windows, the PHP-FPM active process count is not growing anymore, but it does also not decrease. I found a solution for this problem. The Apache <Proxy> option "enablereuse=on" causes the high number of "active" PHP-FPM worker
Bjoern Voigt wrote: processes. PHP-FPM does not close them, because Apache reuses the connections. An explaination can be found here: https://httpd.apache.org/docs/2.4/mod/mod_proxy_fcgi.html#examples I changed <Proxy "fcgi://localhost" enablereuse=on flushpackets=auto> </Proxy> to <Proxy "fcgi://localhost" enablereuse=off flushpackets=auto> </Proxy> I still do not understand, why I saw this problem first time with Nextcloud 20. Nextcloud <= 18 was running fine with the same configuration. Greetings, Björn