Fatal error: Maximum execution time of 60 seconds exceeded in C:\wamp\www\commons\includes\file.inc on line 937

CommentFileSizeAuthor
#5 open atrium.jpg78.04 KBbienfelix

Comments

growltiger’s picture

http://drupal.org/node/454372

Try changing your max_input_time value.

Also let us know if the error is on install or on home page load, if it is replicable, etc.

oneklema’s picture

I receive this about half the time when enabling, listing, or disabling modules on Drupal 6. I do not believe I have any control over the max_input_time or max_execution_time value of php. I seem to get it more often when php5 is being used, as compared to php4. I have also recieved the error that the php is over the max memory allowed (32m).

Fatal error: Maximum execution time of 30 seconds exceeded in /home/klemata3/public_html/cms/includes/file.inc on line 937

ageller’s picture

Using the Windows stack from Acquia
On install, see the install profile screen
Click Commons
Click submit

Get this:

Fatal error: Maximum execution time of 300 seconds exceeded in C:\Users\Adam\Downloads\drupal_commons-6.x-1.2\commons\includes\file.inc on line 937

Dublin Drupaller’s picture

I've got the same error trying to install Commons. seems very memory hungry and takes a long time compared to other installation profiles.

I found upping the max_execution_time and max_memory values in p hp.ini did help...but it still takes ages.

bienfelix’s picture

StatusFileSize
new78.04 KB
wmostrey’s picture

Bienfelix,

Your issue regards Open Atrium while this is the Drupal Commons issue queue. It's best to create a separate ticket on https://community.openatrium.com.

mstef’s picture

Status: Active » Closed (cannot reproduce)

That's right - this is not a Commons issue, so I'll be closing it.

wmostrey’s picture

Status: Closed (cannot reproduce) » Active

The original issue by roseiro and all other posters is related to Commons though.

mstef’s picture

Status: Active » Postponed (maintainer needs more info)

Oh, my mistake. I didn't even bother to read up - this is a pretty old issue. Sorry I cannot provide any help as I have never used WAMP. I pretty much can't provide help for anything that started with a W.

I'm marking this issue as maintainer needs more info, because I'm fairly certain the changes in 1.3 will resolve this.

Please test with 1.3 and reopen if needed.

Danzki’s picture

I found this solution on the Open Atrium forum. It worked for me:

* Open “install.php” from the root directory of your installation
* Find the line calling “install_check_requirements” and comment it out
* Save changes
* Run install again

wmostrey’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)
ubuntu277’s picture

Version: » 7.x-3.0
Assigned: roseiro » ubuntu277
Status: Closed (fixed) » Needs work

I got similar error too:
Fatal error: Maximum execution time of 60 seconds exceeded in C:
\wamp\www\commons7\includes\database\database.inc on line 2139

In php.ini file, I made the following changes:
max_execution_time = 360
max_input_time = 360
mysql.connect_timeout = 360

but still got the same error. Any other suggestion for this error?

japerry’s picture

we force the change on install. it looks like 60 seconds isn't enough. We've upped it to 120 seconds, let me know if thats sufficient.

http://drupalcode.org/project/commons.git/commit/e863af4

keithleeds’s picture

The patch being submitted does a string compare between the current max_execution_time and a string literal of '120'. Of course '60' is greater than '120' so the test won't succeed.

Suggest the following:

  if ((int)ini_get('max_execution_time') > 0  && (int)ini_get('max_execution_time') < 120) {
    ini_set('max_execution_time', '120');

This handles the cases of '-1' and '0' safely, while dealing with the values rather than the text.

See also Issue #1929180

ezra-g’s picture

Issue tags: +Commons 7.x-3.1 radar

Adding this to our 7.x-3.1 radar.

ezra-g’s picture

Assigned: ubuntu277 » japerry
japerry’s picture

Assigned: japerry » ubuntu277
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)
Issue tags: -Commons 7.x-3.1 radar

Automatically closed -- issue fixed for 2 weeks with no activity.

davidjb89’s picture

I just downloaded Commerce Kickstart today and it was still giving me this problem.

I changed the max_execution_time values to 360 for every php.ini that I could find, but it still stopped at 30. I also tried increasing the memory and that did nothing.

Instead I just added set_time_limit(300); to the install.php file, above the line where it says require_once DRUPAL_ROOT . '/includes/install.core.inc';

This solved the problem. Not sure if it will have any unintended consequences in the future, as this is my first time using Drupal Commerce and I don't know anything about php.