After quite a while of getting along very well with Drush, I'm having very frustrating weirdness.

ben@server:/sites/example/www/sites/all/modules$ ./drush/drush.php pm update

Update information last refreshed: Mon, 06/23/2008 - 15:05

Update status information on all installed and enabled Drupal modules:
Name Installed version Recommended version Status
---- ----------------- ------------------- ------

drush: No updates available.

Yet ./drush/drush.php pm install page_title (or other module) works.

On another site, same server, same setup, with a definitely working settings.php, drush gives the Drupal is not installed errors screen on pm update or install.

Anyone have any idea what's going on, how to debug, or if a quart of whiskey will help?

Thanks,

benjamin, Agaric Design Collective

Comments

mlncn’s picture

mlncn commented

I svn deleted google_analytics from sites/all/modules and then drush pm installed it. Then I found and deleted an older google_analytics 1.3 which was in a google_analytics_1_3 extra level of folder in the sites/default/modules directory.

And for that site drush pm update, with SVN integration complete, started working again.

moshe weitzman’s picture

moshe weitzman commented

On the "other" site, try drush help command since that is simpler. try passing the -l option. note that your PHP for web requests is a different from the CLI PHP and might be using a different php.ini and thus have different config.

mlncn’s picture

mlncn commented
Status: Active » Closed (fixed)

I did try the -c path fix mentioned in this thread, and the later mentioned changing localhost to 127.0.0.1

ben@server:/sites/saveournet/www/sites/all/modules$ ./drush/drush.php -l http://saveournet.ca.agariclabs.com -v help

Neither helps, though it is reading the settings.php I'm looking at.... but the site I'm looking at is not, or changing my changing the username also just now would have broken it. Sorry for disturbing everyone, I picked a bad control site. It got pulled out of the system on the test server in a failed attempt to allow volunteers to mess with it by FTP, I remember now.

The update not working was really weird though, does the drupal.org side of that go down sometimes?