Closed (fixed)
Project:
Drush
Version:
All-versions-3.0-beta1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
9 Mar 2010 at 00:46 UTC
Updated:
26 Mar 2010 at 00:10 UTC
A bit hard to tell what is going on so here is the command line and output. Couple of quick notes. It is a multisite install. I have the current civicrm installed as well.
drush --uri=http://example.com cache-clear
results in...
Fatal error: Allowed memory size of 100663296 bytes exhausted (tried to allocate 64 bytes) in /home/mydir/public_html/livesites/sites/all/modules/civicrm/packages/PEAR.php on line 872
Drush command could not be completed. So with an allowed memory size error my first thought would be to just complain to my host. However, the odd reference to PEAR.php under the modules/civicrm threw me off. Any thoughts on why drush would be trying to run code from PEAR.php here?
Comments
Comment #1
moshe weitzman commentedLook at the whole path. This is a file in civicrm.
Comment #2
winston commentedI did notice that. I first searched the issue queue to see if anyone had posted a problem using drush with civicrm, but I didn't see any.
I'll post over on the civi forum to see there.
Just curious as to why drush would be calling something in PEAR.php in a civicrm path though.
Comment #3
winston commentedIn case anyone else stumbles on this, turns out to be neither drush nor civicrm, but a host specific quirk. So anyone using hotdrupal remember that you need to use
127.0.0.1instead oflocalhostin your database connection strings in both settings.php for drupal and civicrm.settings.php. Only affects things like command line php and mysql dump operations and only on hotdrupal hosting as far as I'm aware. Sorry for the bogus issue against drush.