By Attila on
When I'm trying to install Drupal 6.15, it hangs on the database configuration step.
In fact, I could never install drupal the way it should be, I always had to change settings.php manually to enter the database settings. But when I do that with drupal 6.15, I get an error that drupal is already installed and that I should empty the database to restart the installation. But the database is completely empty.
It doesn't really matter which host I use, I've already tried with Hosting2Go, Mans Media and USB Webserver (kinda XAMPP-thing).
Does anybody know what I'm doing wrong?
Comments
Copy default.settings.php
Likely Installing Drupal (6.x) Database setup fails to proceed. No error. from the Troubleshooting FAQ.
That's not the problem. I get
That's not the problem. I get this error message:
have you created the user first ?
Have you created user named alengyel_admin in mysql database before trying to install drupal ?
Yes I did. :)
Yes I did. :)
Exact same issue here with 6.15
Yes, I made sure to duplicate the settings.php file, *not* change the name.
Yes, I enabled write permissions to it as well as the "files" directory.
Yes, I've installed Drupal many times without this issue, up to and including 6.14 (on the same server as this new install).
Yes, I have the MySQL database and username created already and typed in properly.
Am attempting to install 6.14 instead; if that works under the same circumstances, it definitely sounds like it's 6.15-specific.
ARRRGH!! Never mind...
OK, I'm an idiot; I installed the database on the wrong server!!!
Feeling foolish. Install of 6.15 just went through perfectly. Never mind...
Thanks for the follow-up!
Thanks for the follow-up!
Sounds like a mistake I'd of made. ;0)
Thanks!
Problem solved.
None of the suggested things worked here
But one very weird solution did:
I got the same problem (DB Setup hanging without errors) and temporary switching from FCGID to SUPHP Apache modules helped me get past the "loop" while none of the other solutions helped (cPanel EasyApache). I also use mod_cache/mod_disk_cache and eAccelerator. It's possible that the combination of everything results in this behaviour, I'm not sure tho. Disabling mod_cache or eAccelerator didn't help tho, I had to switch modules.
If nothing works and you know what you're doing, try this. Good luck. :-)