PHP-FPM execution timed out exceeds set value

jsparks

Member
Sep 16, 2015
8
0
51
Halifax
cPanel Access Level
Root Administrator
Hello,

I'm running into an issue whereby PHP-FPM and subsequently apache crashes randomly. Taking a look back at the logs during this time, it appears php-fpm child processes are timing out and terminating (this floods the log file). During this time, all new http requests are blocked and all hosted websites appear down. What's interesting is I have request_terminate_timeout set to 120s however, the actual timeout exceeded in the log file is substantially higher ~1200s.

Before I paste the log files, I want to give some context - there's been no real traffic changes on my dedicated server and no major configuration changes except for cPanel updates (running v100.0.11).


php-fpm request_terminate_timeout value set through YAML (verified exists in individual site configurations).

YAML Config Value: /var/cpanel/ApachePHPFPM/system_pool_defaults.yaml
Code:
request_terminate_timeout: { name 'request_terminate_timeout', value: 120s }
Validated site configuration: /opt/cpanel/ea-php74/root/etc/php-fpm.d/$domain.conf
Code:
request_terminate_timeout = 120s
(redacted) Snippit of php-fpm errors from log file:
Code:
[02-Mar-2022 18:47:53] WARNING:  child 30482, script  (request: "GET /index.php") execution timed out (1017.757771 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 30402, script  (request: "GET /index.php") execution timed out (1048.658533 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 30076, script  (request: "GET /index.php") execution timed out (1089.332900 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 29887, script  (request: "GET /index.php") execution timed out (1128.119808 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 29404, script  (request: "GET /index.php") execution timed out (1207.747682 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 29402, script  (request: "GET /index.php") execution timed out (1208.542452 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 29348, script  (request: "GET /index.php") execution timed out (1216.387380 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 29299, script  (request: "GET /index.php") execution timed out (1228.222588 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 29289, script  (request: "GET /index.php") execution timed out (1229.913525 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 29216, script  (request: "GET /index.php") execution timed out (1244.194179 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 29213, script  (request: "GET /index.php") execution timed out (1245.316041 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 29207, script  (request: "GET /index.php") execution timed out (1248.565571 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 29170, script  (request: "GET /index.php") execution timed out (1251.835676 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 29026, script  (request: "GET /index.php") execution timed out (1269.423194 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 28975, script  (request: "GET /index.php") execution timed out (1280.469817 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 28900, script  (request: "GET /index.php") execution timed out (1298.902007 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 28850, script  (request: "GET /index.php") execution timed out (1309.603339 sec), terminating
[02-Mar-2022 18:47:53] WARNING:  child 28602, script  (request: "GET /index.php") execution timed out (1325.273842 sec), terminating
This happens for about 30-40 minutes continuously before recovering.

Any feedback is appreciated.

Thank you
 
Last edited by a moderator:

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
10,360
1,632
363
cPanel Access Level
Root Administrator
Hey there! I'm not sure I'm going to have too many helpful thoughts based on that output alone. These types of issues are often specific to the server environment so it would be best to open a ticket with our support team directly so we can examine this. If you are able to create a ticket, please post the number here so I can follow along and make sure this thread stays updated with our findings.