- Server operating system version
- Ubuntu 20.04
- Plesk version and microupdate number
- 18.0.51
Seem to have a few problems where it appears that despite all websites being set to their own Dedicated PHP-FPM application served by Apache, when one of the sites locks, it seems to lock all the other websites and we get
Error: upstream timed out (110: Connection timed out) while SSL handshaking to upstream.
This issue occurs in the logs of several of our domains at the same time, I am unable to find a direct root cause. Closest I have found is that one site uses a GuzzleHttp/Curl/HttpClient to read from a remote API, but it appears that sometimes, that connection times out and the PHP-FPM module stays open and sleeping in the background such that we get the error to increase the pm_max_children - which already sits at 100 for the affected website.
Never had this problem on a previous host (Azure App Service).
So I guess how can we prevent PHP-FPM from "Sleeping" in the background and time out safely and correctly in the event of a script failure so that it doesn't lock resources elsewhere?
Error: upstream timed out (110: Connection timed out) while SSL handshaking to upstream.
This issue occurs in the logs of several of our domains at the same time, I am unable to find a direct root cause. Closest I have found is that one site uses a GuzzleHttp/Curl/HttpClient to read from a remote API, but it appears that sometimes, that connection times out and the PHP-FPM module stays open and sleeping in the background such that we get the error to increase the pm_max_children - which already sits at 100 for the affected website.
Never had this problem on a previous host (Azure App Service).
So I guess how can we prevent PHP-FPM from "Sleeping" in the background and time out safely and correctly in the event of a script failure so that it doesn't lock resources elsewhere?