Drush bootstrap problem on OS X 10.6

Hmm, I thought I had downloaded the 2.x version, but apparently not. In either case, I get the same issue with the 2.x release.

Using the loopback IP instead of localhost in settings.php worked perfectly, thanks!

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

I started having this problem shortly after I upgraded to MAMP & MAMP PRO 1.9 which allows you run PHP 5.2 OR PHP 5.3. For me the problem only started happening after I changed my version of PHP, (Even then it didn't start happening right away.)

The solution was indeed to reference the MAMP PHP.

For me, because I had MAMP set to use PHP 5.3, the exact command was

Had I set MAMP to use PHP 5.2, the exact command would have been

For folks using older version of MAMP, the exact command is probably just

Don't forget to make it executable.

I'm using OS X 10.6 and MAMP Pro, had similar problems when using drush and changed my .bash_profile as follows which seemed to fix the problem:

And drush worked fine for me for a while.

Today I tried to update my site and things didn't go so well. I ran drush up and drush was able to update the modules without printing an error. When it came to the core, it seems it updated core but when it had to update the database something went wrong...

After this I check my site and it is working, module and core seem to be updated, only I am presented with a message that I need to run updates. I update date the database from within drupal without any issues.

Why aren't the .bash_profile changes I made shown above sufficient?

fyi I tried using 127.0.0.1 but that also broke my site, so I had to change it back to localhost.

I was trying to avoid using the link approach but I guess I'll have to give it a try.

MAMP Pro 1.9
Mac OS X Snow Leopard

Thanks everyone for the info here. I'd like to add one more step, because if you ever delete MAMP, or uninstall it, you are going to lose the stock MAC OS X php executable.

On the Terminal in MAC OS (Snow Leopard), assuming you are configured to be using php 5.2 in MAMP (chg 5.2 for 5.3 if you want to use php 5.3):

1. sudo cp /usr/bin/php /usr/bin/php.stock
2. sudo ln -f /Applications/MAMP/bin/php5.2/bin/php /usr/bin/php
3. sudo chmod 755 /usr/bin/php

In your site's settings.php, set the database line to use "localhost', eg:

[tcl] is the name of my database:

$db_url = 'mysql://root:passwd@localhost/tcl';

(on line 92 or so)

This works!

Joe
http://www.hydeinteractive.com/

You don't need to unlink your system php binary to fix this.

The MAMP php directory structure changed, and the drush shell script doesn't reflect this (yet). Drush looks for a MAMP php in /Applications/MAMP/bin/php5/bin, so I just created a symlink to the new location of the MAMP php binary. I'm using 5.2, so replace with 5.3 if necessary.

Create the missing directory:

Oops I totally broke my drush command by using #11 followed by #13 ! Would really appreciate some help reverting back to the original state.
now I am getting:

drush php-eval
WD php: Missing argument 1 for drush_core_php_eval() in [error]
/Network/Servers/hal.myg5.com/Users/pooya/Sites/drush/commands/core/core.drush.inc on line 602.
Missing argument 1 for drush_core_php_eval() in [warning]
/Network/Servers/hal.myg5.com/Users/pooya/Sites/drush/commands/core/core.drush.inc on line 602.

thanks

You should definitely backup your /usr/bin/php before you follow #11 or #13 above, i.e. something like...

cp /usr/bin/php /usr/bin/php.original

If you've lost your original php, perhaps at a future mac OS update you might get it back? In the interim, why not just reinstall MAMP and use #11 or #13 above? MAMP doesn't need to be running to use the php provided.

Hi Guys,

Drush is well documented. I follow this guide from drush's readme.txt:

NOTE FOR ADVANCED USERS
- If you want to run drush with a specific version of php, rather than the
one found by the drush command, you can instead create an alias that
executes the drush.php file directly:
$ alias drush='/path/to/php/php5 /path/to/drush/drush.php'
If you do this, to allow Drush to detect the number of available columns,
you need to add the line 'export COLUMNS' to the .profile file in your
home folder.

I use MAMP PRO 1.9, and I set up this in my .bash_profile on my macbook 10.6:

# According to drush readme.txt, fix the right php version. In my case, I use MAMP PRO php 5.2 version.
alias drush='/Applications/MAMP/bin/php5.2/bin/php /usr/local/drush/drush.php'

export COLUMNS

Then everything goes fine. No need to modify /usr/bin/php.

s4j4n,

You're right, command drush up failed and I found some interesting things.

1. Using drush alias would get this error:
   
   ...snipped...
Project drupal was updated successfully. Installed version is now 6.17.
Backups were saved into the directory                                [ok]
/Users/art/sites/peco222/backup/modules/20100731001758/drupal.
The command could not be executed successfully (returned: env: php:  [error]
No such file or directory
, code: <em>127</em>)
An error occurred at function : drush_pm_post_pm_update              [error]

   I found an error report called "MAMP_php_error_log_MAMP.txt" which listed like this:
   

   [31-Jul-2010 00:22:15] PHP Warning:  PHP Startup: Unable to load dynamic library 'MAMP_extension_dir_MAMP/imap.so' - (null) in Unknown on line 0
2. So I made a linked php in /usr/bin, then I met another issue:
   
   ...snipped...
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried
to allocate 901 bytes) in
/Users/art/Sites/peco222/includes/database.mysql-common.inc on line 41

An error occurred at function : drush_pm_post_pm_update              [error]
   
   Interestingly, it didn't use the php.ini I set in MAMP PRO 1.9. I checked the manual of MAMP PRO and found that:

   The configuration files are generated from the settings made within MAMP PRO. MAMP PRO uses templates for this purpose where further configuration options are included. You can edit these templates from the menu item File > Edit template. Here, you have access to options which are not accessible from the MAMP PRO user interface.

   That meant there's no chance to employee the php.ini used in MAMP PRO.

3. After using php -i to check what php.ini it used, I found it's /Applications/MAMP/conf/php5.2. So I copied php.ini template in MAMP PRO to /Applications/MAMP/conf/php5.2/php.ini.
   Then, everything worked.

Thanks for your information.

#7 worked for me, after much frustration. Read it carefully, especially the bit about making the php executable.

I think I've solved my problem. Some how the remote server's db information ended up in my local settings.php, which was causing drush to try and connect to a non-existent database. I ended up completely removing settings.php from my repo because it really shouldn't be there anyway.

#2 didn't work for me, but #7 did.

Thanks Zach for #7!
Worked great.

@#13

#13 worked great and it doesn't alter your system's php at all..

I just think the last line should read :

since we are trying to make the symlink executable right?

the antnerve method worked for me - thanx

#13 & #34 are on the right track but have minor typos...

The correct sequence for MAMP 2.0 (#13) is:

Create the missing directory:
sudo mkdir -p /Applications/MAMP/bin/php5/bin

Symlink to the proper binary (#34 in reverse order):
sudo ln -s /Applications/MAMP/bin/php/php5.2.17/bin/php /Applications/MAMP/bin/php5/bin/php

Make sure you can execute it (#31):
sudo chmod a+x /Applications/MAMP/bin/php5/bin/php

For MAMP 1.9, change line 2 to
sudo ln -s /Applications/MAMP/bin/php5.2/bin/php /Applications/MAMP/bin/php5/bin/php

@xtfer: Thanks for correcting me.

I confirm that all the steps in #35 are working correctly for MAMP 2.0.1.

Cheers!

@altrugon: Upgrading to Drush 4.5 alone did not solve the issue, at least not when moving from MAMP 2.0.1 to 2.0.3. I still had to use #35 life saving tricks.

confirm that the symbolic link as explained above works for mamp 2.0.3 and osx 10.7.1:

sudo ln -f /Applications/MAMP/bin/php/php5.3.6/bin/php /usr/bin/php

Thankyou
Drush now works. Running Lion with MAMP 2

I created a patch for drush here.
Notice that you have to configure the mysql-socket under settings.php as a unix_socket
http://drupal.org/node/1420312

great! thx ZACH! i am using php 5.2 but the directory-name is php5 (not php5.2 as in your example). when TERMINAL told me that there was no directory like the one specified in my first try i only had to correct the path and all worked perfectly. after a day of desparate work the problem finally was solved! thx again!