"An error occurred at function : drush_pm_info" - Using Drush with XAMPP on OSX

Just had the same problem.

The issue is the 'Update Status' module is disabled on your system.

To get this working;
$ drush enable update

Just had the same problem.

The issue is the 'Update Status' module is disabled on your system.

To get this working;
$ drush enable update

I have the same issue as first post. My Update Status was already enabled, so this was not a solution for me. Something else is going on for other people (including me).

Much like the first post I am using a weird environment (web server is NGINX)

Same error here, too, on a shared host with Linux. Some more infos:
- Drupal 6.13 out of the box, English, no modules added, update status enabled, only with user 1
- drush status works fine

Here the result of drush -d info (running with debugging info):

The result of drush status:

Hope this helps in finding the error.

I also am running into the same problem. I am running on a Westhost vps.
Output from status:

PHP configuration : /etc/php.ini
Drupal Root : /home/jimmy-nash/www
Drupal version : 6.13
Site Path : sites/default
Site URI : http://default
Database Driver : mysqli
Database Hostname : localhost
Database Username : drupal
Database Name : drupal
Database Password : xxx
Database : Connected
Drupal Bootstrap : Successful
Drupal User : Anonymous

Output from drush -d info

$ drush -d info
Drush bootstrap phase : _drush_bootstrap_drupal_root() [0.083 sec] [bootstrap]
Initialized Drupal 6.13 root directory at /home/jimmy-nash/www [0.33 sec] [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_site() [0.334 sec] [bootstrap]
Initialized Drupal site default at sites/default [0.439 sec] [notice]
Drush bootstrap phase : _drush_bootstrap_drupal_configuration() [0.501 sec] [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_database() [1.088 sec] [bootstrap]
Successfully connected to the Drupal database. [1.089 sec] [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_full() [1.124 sec] [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drupal_login() [6.44 sec] [bootstrap]
Found command: info [6.443 sec] [bootstrap]
Including version specific file : /usr/home/jimmy-nash/drush/commands/pm/update_info/drupal_6.inc [6.444 sec] [notice]
No information available. [6.468 sec] [error]
An error occurred at function : drush_pm_info [6.468 sec] [error]
Command dispatch complete [6.468 sec] [notice]

It seems to be affecting the update command as well as I am unable to run that successfully either. I assume if it can't run info it can't run update correctly either. Running update without arguments does return correct version information from drupal.org. Running it with a project argument return the same as running it without. It updates information, then shows all modules status, then says "No code updates available" [ok]

I can try and provide more details if anyone is looking into this.

Thanks!

This is the same as #539704: Provide warning message when project name not provided for drush info

Explanation and patch there^^

j0rd - "I figured out this is PEBKAC (problem exists between keyboard and chair) error."

I don't think this explanation solves much of the various problems expressed in this thread...
several of the error messages being produced have nothing at all to do with "drush_pm_info"
...but you do make a good point, in regard to "drush_pm_info"

the error that I'm getting is:
An error occurred at function : drush_pm_enable

This has nothing to do with "drush_pm_info"

changing 'localhost' to '127.0.0.1' in my db_url setting in settings.php fixed my issues running drush.

#12 helped me realize this.

environment is shared webhosting on LAMP.
could do everything else necessary on cli but not run drush. kept getting error:
SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) [warning]

i had tried specifying port 3306 on the db_url thinking this would force a tcp connection... but since when does the obvious work like it should. ;)

as shared hosting environments are more common than not- this is worthy of making it's way into the documentation if not into the code to try these alternatives. my environ is cpanel based LAMP which i'd guess has some standards to it... thus i can only imagine lots of others in shared hosting environments will experience the same.

This is another "yay, this thread helped me too!!" comment.

I also had to change localhost to 127.0.0.1 in Drupals /sites/default/settings.php file.

I was getting an error (warning):
SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) [warning]

when trying to run "drush status"

Changing the localhost to 127... worked for me too! Sweet.

mamp runs its own mysql, but mysql looks for its configuration at /etc/my.cnf regardless. osx comes with a my.cnf preinstalled there but it's tailored for the mysql that ships with the os. if you want to use mamp-appropriate settings when running mamp's mysql, then you need to update /etc/my.cnf. Look in /Applications/MAMP/Library/share/mysql and pick one of the my-*.cnf files you see in there, maybe my-large.cnf. Then use that to replace /etc/my.cnf.

Actually you should be able to put it in /Applications/MAMP/db/mysql/my.cnf according to the comments at the top of the file, but I haven't tried that.

The key bit of the configuration is the socket:

socket = /Applications/MAMP/tmp/mysql/mysql.sock

changing to 127.0.0.1 worked here too! thanks

Just went through this. Yes, changing from localhost to 127.0.0.1 is the fix - but the extra tweak I needed to make was to reset the port assignments in MAMP for the Mac. Drush could not connect to MySQL with the default high port assignment in MAMP. I just reset things to the "normal" ports: MySQL: 3306, Apache: 80.