I am completely new to Drush but I believe I have closely followed the readme.txt file for installation and usage. I am on Mac OS X, 10.7.2.
My executable Drush directory is in /usr/bin and I can run the drush command there or anywhere else fine. I also created a .bashrc file in my ~ home folder with the code:
PATH=$PATH:/usr/bin/drush
So when I run Drush within my site I get a few lines of errors (mysql) and then page.tpl.php procceeds to print followed by:
Drush command terminated abnormally due to an unrecoverable error. [error]
I am attaching the transcript from when I ran Drush within my site. Note that the code from the command line says the site is offline but it's not, i can get to it and see it fine in MAMP Pro.
Since I am so new to this, it seems a bit like a needle in a haystack trying to find out what's causing this but I hope something here will ring a bell so I can fix this. Note that this is a brand new clean install of OS X Lion that I am on so I don't believe there was any old files causing any conflicts or other issues.
Thanks.
Comment | File | Size | Author |
---|---|---|---|
error.txt | 4.52 KB | Danny Englander |
Comments
Comment #1
Danny EnglanderI decided to try running the Drush command in another local site on my machine and the command ran as expected with no errors. So that leads me to believe there is an issue with the particular site I mention above. My guess is something to do with the mysql error at the top of my error.txt file from the command line but I just don't know why this is happening.
Comment #2
Danny EnglanderI am closing this for now as I am now pretty sure there is a database error on my local site that I need to fix. It seems that drush can pick up on that so probably a good safeguard.
Comment #3
Danny EnglanderUpdate - it turns out The fix was to point mysql to MAMP, apparently an issue with MAMP 2.
see this:
http://drupal.org/files/mamp-sql-docs.patch
The commands are:
Also see this issue:
http://drupal.org/node/630322
Comment #4
Danny EnglanderChanging title
Comment #5
PixelClever CreditAttribution: PixelClever commented#3 Fixed my issue as well.