Closed (outdated)
Project:
Drupal core
Version:
7.x-dev
Component:
install system
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 Aug 2011 at 15:31 UTC
Updated:
30 Nov 2011 at 21:15 UTC
Jump to comment: Most recent
Comments
Comment #1
btopro commented1. Did you install alpha 4 (you marked this 3).
2. Did you install this where you previously had a drupal site setup in the database. It needs to be an empty database that you install into because Alphas can't be upgraded.
This may be related to the previous issue you posted. Also if you look in the .htaccess file included there are a few lines that attempt to force the server to allow for more memory to be used, remove them and it might help in alleviating errors on install
Comment #2
petermayerla commented1. Did you install alpha 4 (you marked this 3).
Yes I did
2. Did you install this where you previously had a drupal site setup in the database. It needs to be an empty database that you install into because Alphas can't be upgraded.
It is an empty database.
This may be related to the previous issue you posted. Also if you look in the .htaccess file included there are a few lines that attempt to force the server to allow for more memory to be used, remove them and it might help in alleviating errors on install
I looked into the file but I'm not sure about it
Comment #3
btopro commentedtake the lines out of the htaccess file that refer to php there's about 3 of them near the beginning of the file. It's also possible that you don't have enough memory set to install it. I'm building distros off of a less favorable method of creating them (Seedling) and will be building legit distribution / install profile files in future releases to make installation more compatible with environments.
Comment #4
petermayerla commentedok I did that.
didn't make any difference.
so what I get twice (first when I need to insert my sql database and user and second on the next step when I need to insert the administration passwort and sitename) is a Fatal error: Maximum execution time of 30 seconds exceeded in D:\DrupalXAMPP\xampp\htdocs\elms_icms\includes\database.mysqli.inc on line 114.
The first time I can reload the page and it will continue. But the second time it doesn't work and I even get the hint in case of reloading the page the data will be send again which causes the "Table 'actions' already exists" message.
So my questions is why do I get this timeout message? I think this is what causes trouble at the moment.
Thanks,
Peter
Comment #5
petermayerla commentedOK. Problem solved.
this timeout period can be extended by going into the php.ini file and enlarge the "time out execution settings"
thanks for your help anyway.
Comment #6
btopro commentedcool, I was just about to suggest that. This is a common drupal problem but the reason it's currently happening in ELMS is cause of the funky install script. Hopefully in the future it'll have a progressbar that prevents it from timing out in this way (at least during setup).
Comment #7
goldcrusaider commentedI have the EXACT problem as above. 1st I got the database timed out before completing installation. Your discussion was helpful I went to the php.ini and changed the time. However the second part of the problem as discussed above still exist for me. I am getting the error "Table variable already exist" just after config the site. I can not complete set up any idea how I can get rid of the error?
Details:Installing Drupal 7 on a windows laptop w/xamp
Already tried:
reinstalling Xamp and Drupal 3 times
Comment #8
btopro commented"Details:Installing Drupal 7 on a windows laptop w/xamp"
This is a drupal 6 distribution. Try using Acquia Dev Desktop. After installing it there's a way to install additional sites off of whatever you want. Download ELMS and install it that way. I've had less issues and not needed to configure any settings files in order to get it to work right off the bat when doing it the Dev desktop way.
Comment #9
btopro commentedComment #10
goldcrusaider commentedOk I have tried:
Wamp installation and could not get Druapl up and running on that either.
Xamp server and I have now done 7 re-installs
Aquia Drupal install that also was a NO go.
Druplal Bitnami Stack install that was a nightmare.
So I don't think I will try any new installation packages.
2 months down the road, I dont have a working Drupal instal and I still get one common error over and over: "Fatal Error and Warning: Table 'actions' already exist" I think I need some advice how to fix this and what do I need to check in my data base....Any help is much appreciated.
PS. Yes I have uninstalled the Data base a bunch of times just to start fresh
Comment #11
goldcrusaider commentedDrupal Version 7.1 w/Rocketlauncher theme from Rocket Theme
Comment #12
btopro commentedThis sounds like an issue installing drupal in general and not specific to ELMS. We're not running off of Drupal 7 so that could also be part of the problem. Have you seen the README.txt that ships with ELMS about error reporting, max execution time, and other ways of getting around potential installation of such a large platform install?
Comment #13
goldcrusaider commentedBtopro
I am so sorry I did not see that this posting was related to ELMS. I did not mean to hijack your post. I simply had the same error message. I did read all of the read me txt. I always do. I did adjust the max execution time to 120 and it had no effect. I did get the time out error. The latest install Im getting "Fatal Error and Warning: Table 'actions' already exists."
I even pay someone to help me get a clean install right now. Do you know anyone?
Comment #14
btopro commentedno worries, just didn't want to compound the issue. I'm going to mark this fixed from the previous version (of elms) but you may want to make a new issue for the drupal project in general as I'm not sure what would cause that in Drupal 7. Try installing the Acquia Dev desktop installer after removing everything from your system related to WAMP/XAMPP and what not.
Comment #15
pau1_m commentedsubscribing
Comment #16
btopro commentedmoving this over to the drupal core issue queue as this is not related to elms as identified by OP