Problem/Motivation

Drupal 8 appears to be needing more memory and execution time than most web hosting companies have pre-configured in their hosting packages. All kinds of installation errors can happen if you don't have enough memory or execution time.
Like:
#2021029: During Install, Inform User that they have Insufficient Memory Rather than Server Error: AJAX HTTP Result Code: 500

The default execution time on most hosting packages is still 30 seconds, which is probably too little.

Proposed resolution

Do some measurements on PHP parameters that give a reliable environment to install Drupal 8.
Update the requirements page https://drupal.org/requirements/php or / and check during installation and warn the user, if there is not sufficient memory or execution time.

Comments

flefle’s picture

Tested with git clone of latest Drupal 8 on Apache 2.22, PHP 5.4.16, MySQL (WAMP ver. 2.4), 128MB memory_limit.
Memory shouldn't be the issue but the execution time. A quick workaround would be:

php.ini setting:
max_execution_time = 60

or PHP
ini_set('max_execution_time', 60); //1 minute

A great feature of Drupal8 would be a requirements check at installation of this setting or ini_set included.

Furter info can be found here.

Wim Leers’s picture

Calling ini_set() is evil AFAIK. Some server setups even block PHP script files containing ini_set() calls, resulting in a WSOD.

Wim Leers’s picture

Issue summary: View changes

use [#NNN] formatter to make a nice issue link

Les Lim’s picture

Issue summary: View changes

Opcode cache makes a difference for me. With APC, I can make it through the installer with memory_limit = 32M. If I try again without APC, I'll hit the memory limit.

Tested on Apache 2.2.23 with PHP 5.4.10.

nedjo’s picture

Status: Active » Closed (duplicate)

Marking as a duplicate of #2289183: Temporarily increase D8 memory limit to reflect current requirements. Although this issue is older, that one has more discussion and a patch (albeit a trivial one).

YesCT’s picture

Title: Update PHP requirements page for Drupal 8: needed memory and execution time » Update PHP requirements page for Drupal 8: execution time
Status: Closed (duplicate) » Active

The other one is doing memory. We can do execution here.

anavarre’s picture

AFAICT installer works fine with the current max_execution_time. It's been a while since this issue has been filled. Do we have any recent reports of max_execution_time being an issue, still?

Also, #3 has been discussed in the context of temporarily upgrading PHP's memory_limit in #2289183: Temporarily increase D8 memory limit to reflect current requirements.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

roshan_shah’s picture

Ran into installer issue for php 7.04 using Acquia Dev Desktop 2. Updated max_execution_time in DevDesktop\php7_0\php.ini and was able to get the site up.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Status: Active » Closed (outdated)

Eight years ago it was asked if this was still a problem. In the intervening time there has been one confirmation. That was 6 years ago on outdated versions of PHP and Drupal.

Therefor I am closing this as outdated.