Drush not connecting to database

This is the full output of the script, without the PHP tags obviously....

I assume that you have no problems connecting to the database with the regular drupal installation.

I had a similar problem, the solution was that I had to point command line PHP to the php.ini file used by the apache php to enable database support.
This is done with the -c attribute

the path to the php.ini can be found allmost at the top running the command php -i, or alternatively making a simple php page that looks like this:

This might help solve this problem, but I did not get exactly the same error you have. My error was that php claimed I had not activated any database modules.

http://www.raincitystudios.com/blogs-and-pods/steve-krueger/how-use-drus...

Just saw this, and confirms the same thing Vidar mentioned. I haven't tried it yet, but I am sure this is what the problem is. Maybe I'll try to cook up something to add to the docs for this.

Automatically closed -- issue fixed for two weeks with no activity.

Having the same issue with 6.x-1.x-dev

mysql is running fine for my site.

Figured out the solution to this problem - I needed to update my settings.php to set the host for mysql to 127.0.0.1 instead of localhost to be able to access mysql from command line.

I had this same problem with version 5.

I am running MAMP on OS X so there was more than one version of php on my machine and the one I wanted was not in my path.

The solution was to specify the MAMP version of php in the alias. the line in .bash_profile looked like this:

alias drush='/Applications/MAMP/bin/php5/bin/php ~/Documents/websites/public_html/drupal-5.7/sites/all/modules/drush/drush.php -r ~/Documents/websites/public_html/drupal-5.7'

and i used the -l switch to specify the site.

MAMPIf using MMAP, your socket file is not where mysql expects so that could be an issue as well. This is basically a local config problem, not drush.

I think the issue now is about how to properly document this.

Potentially not... I have a very similar problem, but with a different MySQL error. NO idea what's causing this. This is on a *nix server in a shared hosting environment, and Drush works in this exact account with a D5 setup.

I get:

... stuff...

I have no idea where this is coming from, as I've never used, attempted to use, or even typed "mysqli" before in my life, afaik.

You don't have to type mysqli - Drupal detects that for you and uses it if available. So, you need to go to the settings.php that is in effect for this drush request and edit the line starting with $db_url and use mysql instead of mysqli

This whole thread comes down to people not configuring their command line php properly which is really easy to do. Unfortunately, fixing this out of scope for this module. It does not help that MAMP and maybe others do some non-standard stuff.

WOW. I wouldn't have thought of that in a month. I'm confused why I don't have this same problem with D5 tho - is the default connection string not the same? I have run a D5 install in exactly the same account, without this problem. Also, the rest of the site works just fine with the string like that, which seems weird...

At the *very* least, I think a mention of this deserves an entry in the README? The command line php stuff might be "really easy", but there is not a centralised place for these weird caveats, so people don't know about them. I asked half a dozen times about this on IRC with no useful response (not for want of people trying). Perhaps this is something that needs to be addressed?

Many thanks.

Many providers give you what is known as a "jail shell"

When in this shell you can't use localhost as you don't have direct access to the MySQL socket. This is why you need to use a hostname of 127.0.0.1 so MySQL is accessed via TCP instead of trying to access via the socket.

Steve
HotDrupal - Drupal Friendly Hosting

Another issue for me that was PHP/MySQL/MAMP related was that in setting.php, I don't have to specify the port that MySQL is running on for Drupal to work. I do have to specify it for drush to work, however. So I had to specify :8889 in my $db_url.

Thanks. the localhost change to 127... did it for me.
Could this be placed in the documentation under troubleshooting? This would have saved me hours of looking online.

For the record, #2 didn't work for me, if I reference the same php.ini in my MAMP installation my CLI php fails.

I used phpinfo() on the command line to find out where the php.ini file was. I then configured the mysql and mysqli socket config as per my MAMP php.ini.

Replacing 'localhost' by '127.0.0.1' in my settings.php file worked.

Replacing 'localhost' by '127.0.0.1' in my settings.php file also worked for me.

I am on OS X running the local apache build. On my OS X Servers I do not have the same issue with drush and the web environment. If anyone has an idea on how to have the OS X environment use localhost, I would appreciate it. I think it may have something to do with mysql treating localhost as a socket connect vs. TCP. Not sure though.

ok, I finally found my issue above. To fix the OS X environment (for me at least) and avoid changing db connection strings in settings.php to 127.0.0.1, set the default socket connections for mysql in the php.ini that your CLI php is reading. Mine was in /etc/php.ini.

I found the tip here: http://drupal.org/node/383848

Perfect!

@ moshe weitzman #12

This whole thread comes down to people not configuring their command line php properly which is really easy to do. Unfortunately, fixing this out of scope for this module. It does not help that MAMP and maybe others do some non-standard stuff.

It not just about configuring their command line properly, as this thread shows. The explanation from HotDrupal.com in #14 is very good:

Many providers give you what is known as a "jail shell"

When in this shell you can't use localhost as you don't have direct access to the MySQL socket. This is why you need to use a hostname of 127.0.0.1 so MySQL is accessed via TCP instead of trying to access via the socket.

It's not Drush problem that you can't connect to localhost in a shared hosting environment with jail shell, but it would help tremendously if these kind of errors where documented somewhere under troubleshooting for Drush.

I think a lot of those who are new to Drush are not that experienced with this and would be helped by simple lines like if you get this error, try to replace 'localhost' with '127.0.0.1' in settings.php.

Even better would be if there was some way to configure Drush to use 127.0.0.1 instead of localhost, so you don't have to mess with settings.php (maybe there already is a way?).

I was really excited to finally find a fix for this, but alas, changing localhost to 127.0.0.1 did not work for me. Here's what it DID do though:

Changed the error I got from that /sock stuff to:

Access denied for user '....'@'127.0.0.1' (using password; YES)

Before I made the change from localhost, the website worked fine but CLI didn't, and after I made the change, I got this same new error from both web and cli.

For reference, changed:
$db_url = 'mysqli://my_username:my_password@localhost/my_dbname';
to
$db_url = 'mysqli://my_username:my_password@127.0.0.1/my_dbname';

Any ideas? I reallllly wanna use Drush :)

@MadtownLems

Try adding 127.0.0.1 as an allowed host for your database user.

Symptoms:

I couldn't even connect with mysql -h 127.0.0.1 ... , even though I was certain the info was correct.

At first, I was getting the "can't connect using socket ..." error.

Adding -h 127.0.0.1 eliminated that error, but then I got "access denied for user..." error.

Specifying 127.0.0.1 as an allowed host in addition to changing the host in settings.php fixed everything.

I still think it would be a great help for many people if the module instructions included this info about localhost vs 127.0.0.1 in settings.php.