I think the new drush is somehow interfering with the $GLOBALS['db_url'] variable between loading it in settings.php and its use in database.mysql.inc.
Admittedly, in my D6.10 setup, I've customized the $db_url in settings.php by appending a query-string that passes SSL file location parameters. What I don't understand is why the query-string is not passing through cleanly to database.mysql.inc, where it is interpretted. This worked perfectly before the alpha2 upgrade. Also, the "drush sql cli" command logs in to the database correctly.
My guess is the new drush only loads expected parameters from $db_url, and then passes that off to the database files.
Is this something that can be adjusted in drushrc.php?

Comments

dsw9742’s picture

Category: support » bug
moshe weitzman’s picture

Status: Active » Postponed (maintainer needs more info)
ar-jan’s picture

Status: Postponed (maintainer needs more info) » Active

I have the same problem (I think, unless this is another issue). I'm using the 6.x-2.0-alpha2 on Drupal 6.10 (before I was using the old 1.2).
When I do drush -l mysite.local status I get this warning:

SQLSTATE[28000] [1045] Access denied for user 'admin'@'localhost' (using password: YES)

Edit: using the latest HEAD version I no longer have this error (although I get some other weird things going on now).

dsw9742’s picture

So after some more digging, I think the issue lies somewhere in how Drush makes db connections. I had assumed it used Drupal's settings and .inc files, but it appears that is no longer the case.
I am using D6-10.
Currently, I have modified the db_connect function in database.mysqli.inc in order to make a SSL connection from my web server to by database server:
$connection->ssl_set($key,$cert,$ca,$capath,$cipher);
How does one accomplish this in Drush? I'm just clueless at the moment, as it works completely independent of Drupal.

moshe weitzman’s picture

Category: bug » support
Status: Active » Fixed

See drush_valid_db_credentials(). Otherwise, we use drupal's db_conect().

Status: Fixed » Closed (fixed)

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