PHP Fatal error: Maximum execution time of -1 seconds exceeded

php-fpmtimeout

I have a script which has a long running MySQL query and PHP returns a huge number of records as it is used to fetch raw logs for users.

I am finding it a little strange but i am getting time out after setting max_execution_time = -1.

I have also set max_input_time = -1 and memory_limit = -1 to make it work atleast for testing server.

Server has php5-fpm. Have also done multiple restarts with service php5-fpm restart.

What can be the issue here?

Best Answer

You should use "0" and not "-1".

REF: https://stackoverflow.com/questions/15776400/make-script-execution-to-unlimited

Related Solutions

Nginx – Fixing 504 Gateway Time-out Error with PHP-FPM on Test Server

I found answer on my posting on the nginx forum - http://forum.nginx.org/read.php?2,127854

The answer, in my case, is to set:

request_terminate_timeout=30s

in php-fpm config (usually /etc/php5/fpm/php-fpm.conf)

Note, you can use values other than 30s also.

I used it to match my value in main php.ini file which is:

max_execution_time = 30

Thanks All. :-)

Nginx – MySQL Execution Time Spikes

Sounds almost definitely like a peripheral issue influencing what is going on and fairly typical of running Magento in a constrained and contended environment like a VPS.

If your configuration was previously working well and you haven't changed any code or installed any extensions - then it will be an external influence, most likely an increase in traffic - but with a VPS, it is more than likely increased I/O activity.

It sounds exactly like I/O wait - simply installing a graphing tool like Munin would conclusively prove this (showing a correlating in MySQL slow queries with I/O activity/wait).

I'll refer to a few other posts on the same vain - as running Magento in a VPS always yields similar behaviour.

Best Answer

Related Solutions

Nginx – Fixing 504 Gateway Time-out Error with PHP-FPM on Test Server

Nginx – MySQL Execution Time Spikes

Related Topic