Server Timeout Settings?

General Forums Installation & Upgrade
#1

I am preparing to upgrade my store and I get a message saying that the upgrade can fail because of PHP script timeout settings. It offers to run a test script, which fails. I have contacted my host, asking them to increase the max execution time so that I can run the upgrade script successfully.

My host wants to know what settings I need changed. Can someone help? Here is their question:

As we can see, your Apache timeout currently set to 240, PHP max_execution_time = 180 and mysql.connect_timeout = 60, could you please specify which exact values you want to increase

Thanks in advance for your help!

#2

max_execution_time = 3600

#3

Thank you!

#4

I had ignored this few times and was lucky :)

#5

max_execution_time has been set to 3600

However, after running the test script, it's still saying this:

Your server has wrong PHP script timeout settings. This could be due to restrictions on the PHP set_time_limit function or FastCGI "Timeout" options. We recommend you to contact your hosting provider in order to resolve this issue or contact our tech support team to perform the upgrade for you.

What now?

#6

Looks like FastCGI timeout should be also increased:

https://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html#fcgidiotimeout

#7

My host has increased max_execution_time to 5000 but no difference. Also when I asked them to increase FastCGI limit they said: That module has not been installed on your server. If you wish, we can install it for you, but please note that this installation is serverwide.


Any ideas?

#8

Go to Administration->Logs->Click Gear Icon Top Right->PHP Information and see what the values actually are for max_execution_time.

If you don't have FastCGI then don't worry about it.

#9

Go to Administration->Logs->Click Gear Icon Top Right->PHP Information and see what the values actually are for max_execution_time.

When I do this, I see two values:

Local Value: 3600

Master Value: 180

#10

That's strange. It should work.

#11

I have exactly the same problem. The server uses suPHP.

#12

I ignored the warning and went ahead with the upgrade. Both upgrades succeeded (4.3.5 > 4.3.6 then 4.3.6 > 4.3.7). This is on a test installation in a subfolder. I'll update my theme now and see if I can get this test installation working satisfactorily. If it does, then hopefully I can go through the same process with the main site and be good.

Thanks everyone for your input. I'll keep this thread updated on progress.

#13

I have tried to update the Vivashop theme to 2.6 (from 2.3) following very carefully their detailed instructions, but something has evidently gone wrong because the (test) site's a mess. Glad I didn't try this on my working site. :-)

I've contacted the theme developer. Hopefully they can shed some light.

#14

I've updated my main site from 4.3.5 to 4.3.6 but am now stuck on the upgrade from 4.3.6 to 4.3.7. The upgrade has been hung for about an hour and a half on: "compressing backup file."

I read in another thread that I can bypass that step by making my own backups and changing the upgrade process to not do the compressed backup. How do I interrupt the process that has hung? There is no "stop" option. Can I just close that browser window?

If I just close the browser window, can I start the process again or am I hosed?

#15

OK I re-did the upgrade after telling it not to do a backup and everything went fine.

EnergoThemes then updated the VivaShop theme for me and everything went fine there, too. When I did the theme update on the test site, something evidently went wrong at the point where I told it to clear the cache.

All's well that ends well.

#16

max_execution_time has been set to 3600

However, after running the test script, it's still saying this:

Your server has wrong PHP script timeout settings. This could be due to restrictions on the PHP set_time_limit function or FastCGI "Timeout" options. We recommend you to contact your hosting provider in order to resolve this issue or contact our tech support team to perform the upgrade for you.

What now?

I have exactly the same problem. The server uses suPHP.

We recommend you first to make a full backup on the Administration > Backup/Restore page in the admin panel. If the backup copy is created successfully, the upgrade process should also be performed properly.