Increasing the max execution time

apache-2.4mpm-eventubuntu-14.04

Mine is Ubuntu 14 and I've enabled fpm-event with Apache.

apachectl -V | grep -i mpm shows:

Server MPM:     event

It seems those pages which take more than 30 seconds to execute I'm getting this error:

Internal Server Error The server encountered an internal error or
misconfiguration and was unable to complete your request.

Where should I change the configuration to increase it to day 45 seconds?

In the apache error log I can see:

[Tue Apr 03 16:14:44.259133 2018] [fastcgi:error] [pid 28646:tid
140666243819264] [client 103.52.51.21:60161] FastCGI: comm with server
"/usr/lib/cgi-bin/php5-fcgi" aborted: idle timeout (30 sec), referer:
http://www.example.com/google-analytics-charts/verify

Actually it is Drupal site which can be extremely slow.

Best Answer

Probably this solution helps you: https://stackoverflow.com/questions/40360922/increase-php-fpm-idle-timeout-setting

You can change idle-timeout in your apache config to extend it (cannot be 0):

FastCgiExternalServer /usr/lib/cgi-bin/php7-fcgi -socket /run/php/php7.0-fpm.sock -idle-timeout 1800 -pass-header Authorization

Related Solutions

The meaning of “AH00485: scoreboard is full, not at MaxRequestWorkers”

We had the same problem on Apache 2.4.6. After monitoring the server and adjusting the setting for several hours it appears to us that Apache may have a bug. What appears to happen is that the server processes occasionally goes into the G state (Gracefully finishing) and restarts to accept new requests, that's normal. What is not normal is that for some reason this can take up to a few minutes to restart. If you only have a few server process running and they all go into the G state at the same time then your scoreboard fills up and you won't be able to server any more requests.

What we did was increase the number of servers so there is a less of a chance that they will all go into the G state at the same time. Also make sure you allocate at least 25 threads (MaxRequestWorkers) for each server process because that appears to be the default (i.e. if 5 Servers x 25 ThreadsPerChild = 125 MaxRequestWorkers). You can change ThreadsPerChild if you like, we left it at default. If you don't allocate enough threads the additional servers will not start. We left MinSpareThreads at the default value which is 25 and the default for MaxSpareThreads which is 75. If you do modify these settings, the value for MaxSpareThreads must be greater than or equal to the sum of MinSpareThreads and ThreadsPerChild. Also MaxRequestWorkers must be equal to or less than the ServerLimit.

Here is what worked for us but it might not be the best configuration for you.

StartServers 3
MinSpareServers 5
MaxSpareServers 10
ServerLimit 250
MaxRequestWorkers 250
MaxConnectionsPerChild 1000
KeepAlive Off

Edit: This is a confirmed bug in httpd's mpm_event module which might not be fixable through configuration.
The linked bugtracker entry has a presumed patch and more discussion about how to fix this until a new version of the event module is officially released.

FastCGI: “comm with server aborted: read failed” only for one specific file

If PHP is failing only on specific source files, the most probable reason is that some PHP code accelerator (opcode cache) like Xcache, APC or eAccelerator has issues with the file. This can be due to bugs in the accelerator or in PHP itself.

You can try to run your script via PHP command-line interface (php-cli command) as PHP CLI doesn't use any accelerators.

Best Answer

Related Solutions

The meaning of “AH00485: scoreboard is full, not at MaxRequestWorkers”

FastCGI: “comm with server aborted: read failed” only for one specific file

Related Topic