Closed (fixed)
Project:
Drupal Commons
Version:
7.x-3.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
21 Jan 2011 at 18:02 UTC
Updated:
3 Jan 2014 at 02:58 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
growltiger commentedhttp://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.
Comment #2
oneklema commentedI 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
Comment #3
ageller commentedUsing 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 937Comment #4
Dublin Drupaller commentedI'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.
Comment #5
bienfelix commentedComment #6
wmostrey commentedBienfelix,
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.
Comment #7
mstef commentedThat's right - this is not a Commons issue, so I'll be closing it.
Comment #8
wmostrey commentedThe original issue by roseiro and all other posters is related to Commons though.
Comment #9
mstef commentedOh, 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.
Comment #10
Danzki commentedI 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
Comment #11
wmostrey commentedComment #12
ubuntu277 commentedI 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?
Comment #13
japerrywe 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
Comment #14
keithleeds commentedThe 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:
This handles the cases of '-1' and '0' safely, while dealing with the values rather than the text.
See also Issue #1929180
Comment #15
ezra-g commentedAdding this to our 7.x-3.1 radar.
Comment #16
ezra-g commentedComment #17
japerryFixed based on #14, here:
http://drupalcode.org/project/commons.git/commit/2f761d3
Comment #20
davidjb89 commentedI just downloaded Commerce Kickstart today and it was still giving me this problem.
I changed the
max_execution_timevalues 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 saysrequire_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.