Does the request_terminate_timeout
in the PHP-FPM Pool Definitions overwrite the max_execution_time
in php.ini file?
max_execution_time is set to 60 which is too low. A minimum execution time of 150 seconds is recommended to give the migration process the best chance of succeeding.
max_execution_time int. This sets the maximum time in seconds a script is allowed to run before it is terminated by the parser. This helps prevent poorly written scripts from tying up the server. The default setting is 30 . When running PHP from the command line the default setting is 0 .
How to increase max execution time in NGINX? Open your nginx. conf file and add the following directive within the http block: fastcgi_read_timeout 60s; This should be greater than or equal to the value set in max_execution_time .
The configuration file is /etc/php- fpm.
Apparently the're both doing the same thing at different levels. max_execution_time is honored by PHP itself and request_terminate_timeout is handled by the FPM process control mechanism. So whichever is set to the lowest value will kick in first. Also Apache has the idle-timeout parameter that it observes and will give up on the PHP process after that time.
Also
maximum execution time is not affected by system calls, stream operations etc.
so you need to take that into account as well.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With