Install fails after completing 135 modules

What's your php memory limit set to? Should be at least 256M.

Not sure what else to suggest, other than bumping up some of the timeouts and memory. I cannot reproduce this on any of our servers here and didn't run into this during the OA2 training when we installed locally on various people's laptops.

Also, does it really fail, or does it just take a long time? The installer gets slower and slower and slower and takes a long time to enable some of the later modules. Install takes at least 15-20 minutes typically here. So you might just try waiting longer.

Bump your execution time to 1200 and after installation reduce it back to your previous value.

I'm having exactly the same problem.
php memory: 500M
max execution time: 1200
It reaches 135 steps and then after a couple of minutes all activity dies down on the server. No error messages in the apache log.

Not sure what to do to help with this since it works fine on all of systems here and works on Pantheon. It has to be something specific to your configuration so you'll need to debug the Drupal installer to try and determine what it's doing that is causing it to hang. No way for me to debug it when I can't reproduce it.

Should probably also say that you should try using the -dev version since several fixes have been made to the dependencies and modules. Or just wait for Beta 4 and try it instead.

See this: #2069029: Download link returns 404 not found.

You'll need to use git to grab the -dev and do the drush make stuff with build.sh. If you are not comfortable with that, then you'll need to wait till Beta 4.

I'll give the dev a try and report the results.

This is probably related to #2035673: Error: Maximum execution time of 240 seconds exceeded, the problem is that the max_execution_time is overwritten by node_access_rebuild

Here are my results:

• The dev build producted exactly the same problem (one step later, but the same step name).
• Patching Drupal to prevent it overwriting max_execution_time made no difference.
• By monitoring server activity during the install, it can be seen that mysql & apache stop being busy (i.e. the installation hangs) 120 seconds after step 135.

An identical problem has been reported here: community.openatrium.com/issues/node/4940 but with no reported solution.
It is possible that it is actually the browser that is timing out. (Firefox defaults to 115 seconds).

• Tried changing the browser's network.http.keep-alive.timeout, as described here: https://support.mozilla.org/en-US/questions/950497 but it made no difference.

Possible: When I had problems, I thought there might be a timeout problems and changed from firefox to chrom (on ubuntu), leaving the window visible and touching the mouse every now and again.

OK, I think I've narrowed this down a bit.

The module being installed at #135 is the Panopoly Core module. It is doing some stuff in the hook_modules_enabled that is very slow and might cause memory issues with Features. And the bigger problem is that it gets triggered for every other module installed after that.

Before #135, each module installs in about 5-6 seconds on my machine here. After #135 each module takes about 20 seconds. So something is definitely going on and I'll continue to play with some possible solutions.

OK, hopefully fixed in 99ad9c4. See Panopoly issue #1837312: Troubles Implementing Default Permissions for Panelizer for the relevant patches.