by Ross Manson.
Problem was scripts timing out AFTER installation. Enabling debugging in config-dist.php showed no errors, but once installation was done - but prior to completing initial admin settings - I set debugging to "on" in config.php by adding lines as per http://docs.moodle.org/27/en/Debugging
This showed max execution time exceeded on script execution.
Then, BEFORE completing initial admin settings, I set max execution time in php.ini to very large number (it's a development environment so not an issue.) I chose 9999 seconds instead of the default 30.
Tried this on an install that failed yesterday, and it doesn't seem to retrieve the situation - the damage seems to be done. So, to make the package work (on a moderately powerful, lots of memory, Win 7 machine) unzip to a folder, then in the file server/php/php.ini, set line 458 to read:
max_execution_time = 999
Maybe the package need to be modified.
This showed max execution time exceeded on script execution.
Then, BEFORE completing initial admin settings, I set max execution time in php.ini to very large number (it's a development environment so not an issue.) I chose 9999 seconds instead of the default 30.
Tried this on an install that failed yesterday, and it doesn't seem to retrieve the situation - the damage seems to be done. So, to make the package work (on a moderately powerful, lots of memory, Win 7 machine) unzip to a folder, then in the file server/php/php.ini, set line 458 to read:
max_execution_time = 999
Maybe the package need to be modified.