Closed (cannot reproduce)
Project:
Drush
Version:
All-versions-3.0
Component:
PM (dl, en, up ...)
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
14 Jun 2010 at 11:07 UTC
Updated:
29 Mar 2012 at 13:16 UTC
The server in question uses a unique socket for MySQL, and Drupal itself uses mysqli to connect but the php.ini file has mysqli.default_socket and mysql.default_socket both set. I tried switching Drupal to connect via mysql and that also works. This from CLI also works:
mysql -uuser -ppass user_dbname
but when I run drush this is what I see:
$ drush status --uri=http://mysite.com/
SQLSTATE[00000] [1045] Access denied for user: 'user@localhost' (Using password: YES) [warning]
Drupal version : 6.17
Site URI : http://mysite.com/
Database driver : mysql
Database hostname : localhost
Database username : user
Database name : user_dbname
Default theme : garland
Administration theme : garland
PHP configuration : /home/mysite/www/www/php.ini
Drush version : All-versions-3.0
Drush configuration :
Drupal root : /home/mysite/www/www
Site path : sites/mysite.com
Everything seems correct to me. I confirmed that my php.ini is being loaded:
$ php --ini
Configuration File (php.ini) Path: .:/etc
Loaded Configuration File: /home/mysite/www/www/php.ini
Scan for additional .ini files in: (none)
Additional .ini files parsed: (none)
But drush can't connect. Is there something that I am not seeing here?
Comments
Comment #1
moshe weitzman commentedCan you try one of the scripts in Drupal 7 like run-tests.sh or drupal.sh. If you can get one of those working for you, but can't get drush working, then we have a drush bug. For drupal 6, you could test with the run-tests.sh that ships with simpletest module in contrib.
Comment #2
hershel commentedThank for your response. It's a Drupal 6 site. I made a fresh install of Drupal 6 with no changes made whatsoever beyond the initial install.
drush dlworks so I used that to download simpletest and then I moved the .sh script into /scripts and ran it:Seems to me that that is enough to indicate that run-tests.sh is actually executing correctly because it would appear that this code was run:
at line 36. Just to make it 1000% certain I added a few lines of code:
Here are the results, including drush:
Let me know what else I can do to help debug this. Thanks.
Comment #3
jhr commentedticket is almost 2 years old on a version no longer supported