By tnanek on
I am having difficulty getting the install script to execute on a 6.2 Drupal install for a second site. I used the same conventions as I've done previously with 5.x, and I notice that there is no documentation on the subject for 6.x yet.
When I access the address that would've asked me my database info in 5.x, it displays an error:
The mysql error was: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2).
I am intending on using a different database than my main site, and the host is not the localhost either (also not the same as the main database).
Comments
Same issue........
I also installed Drupal 6.2 but I am unable to install feedback-5.x-1.0 on it. Please see if a new release for 6.2 could be made available. Any alternatives also will help.
You issue has nothing to do
You issue has nothing to do with this thread, please don't hijack other threads.
Drupal 5 modules will not work on D6. Check the issues queue for the module and/or http://groups.drupal.org/node/5036 to see if any work is being done on a d6 port. If not, you can start an issue for it, assist in the effort, and/or post a bounty for it.
===
"Give a man a fish and you feed him for a day.
Teach a man to fish and you feed him for a lifetime." -- Lao Tzu
"God helps those who help themselves." -- Benjamin Franklin
"Search is your best friend." -- Worldfallz
I don't think you're problem
I don't think you're problem is multisite in d6-- I'm fairly certain nothing has changed about setting up multisites. Your problem is related to the fact your db is located on a different server-- you need to figure out how to tell the d6 installer not only the db name, but the server-- i know that's not very helpful, but it might save you some time trying to tshoot multisite. If I can figure out how, i'll post back.
===
"Give a man a fish and you feed him for a day.
Teach a man to fish and you feed him for a lifetime." -- Lao Tzu
"God helps those who help themselves." -- Benjamin Franklin
"Search is your best friend." -- Worldfallz
What I've done.
I've tried editing the settings.php file to put the database access information in directly, but then I get errors that tables do not exist in the database, so clearly it skips the installer if I do that.
On my main site, I have Drupal 6 installed and that database is on a different server as well, but I actually got a chance to enter that in the installer. The fields are on the first screen of a properly working installer for database name, host and username and password. But I am not getting that. Its also not defaulting to what my main site is either, so I have no idea what do at this point.
Also, it clearly knows there is a settings.php file there, since when I do not have it there at all, it loads my default site. It doesn't seem to make any difference for the permissions of the file, so clearly its not looking at that at this point.
Okay, in manually typing in
Okay, in manually typing in the install.php file, I get to the verify requirements page, and this is the error page that comes up. I have contacted my hosting provider (servage), but they don't impress me with knowledge of drupal seeing as their first response is that "the site does not exist on your server".
There's not much I can add--
There's not much I can add-- that error message pretty much says it all-- double check all your mysql connection information in the 2nd site's settings.php file. I would probably also try installing drupal locally on the other mysql server as a test just to verify that it, in fact, works.
Also, see http://drupal.org/node/210238 (it seems there may be some differences in d6 under certain circumstances). When I did it locally, same server, I had no problems with d6 multisite.
===
"Give a man a fish and you feed him for a day.
Teach a man to fish and you feed him for a lifetime." -- Lao Tzu
"God helps those who help themselves." -- Benjamin Franklin
"Search is your best friend." -- Worldfallz
I contacted my provider and
I contacted my provider and they were much much much less than helpful, thus that was a waste of time. They never answered my question, and simply said we won't assist you with a third party install.
The things in that error message that confuse the hell out of me are: I Never got a chance to enter a database username or password, nor the location of my database (not on localhost). The server is clearly running since my other site on the same server is functional, so clearly none of the listed questions are the problem.
Right now, I've reinstalled the main site, and now I cannot get anything resembling a separate site, despite entering everything exactly the same as I had prior in a 5.x install.
I have tried editing the settings.php file directly to put the database access information in, but then all I get are error messages saying the tables do not exist. So clearly I cannot skip the install process, which is what your reply suggests. I cannot get the install process to execute at all. Thus, as far as I'm concearned, the 6.x multisite feature doesn't seem to work at all. When I go to the install.php file, with the default.settings.php file in the appropriate sites directory, it will tell me Drupal is already installed. If I make the filename of that file settings.php, I get the above error message when accessing the site (the error in the first message here when I go to the site without the install.php typed in) - atleast that was before I started from scratch with the whole install of my base site - now I just see my default site when I go to that address. I shall attempt an install with multisite within the hour on my personal localhost to test, but I do not have much hope. This post will be edited once that's done with the results.
Still having trouble with it - making the directory name for the second site seems more of a challenge on localhost for it to be accessible - I tried making an alias, but that didn't work - so I have to play with the settings files for MAMP.
LAST EDIT: I've now managed to get it working. This was prior to 6.3 coming out. I took the default.settings.php and entered the database access information for the second database (i'd imagine entering a database prefix that isn't already in use would cause the same thing) and put it in the new location (actually copied it prior, and renamed the copy to settings.php). After that, the installer works perfectly.