Closed (fixed)
Project:
Drush
Component:
PM (dl, en, up ...)
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
23 Jun 2010 at 23:51 UTC
Updated:
10 Dec 2010 at 16:03 UTC
Jump to comment: Most recent file
As you can see below "drush up" began just fine, then started to error just before drush_pm_updatecode.
Any suggestions would be appreciated.
Refreshing update status information ...
Done.
Update information last refreshed: June 23, 2010 - 2:24pm
Update status information on all installed and enabled Drupal projects:
Name Installed Proposed Status
version version
Administration menu 6.x-1.5 6.x-1.5 Up to date
Admin Role 6.x-1.2 6.x-1.2 Up to date
Advanced help 6.x-1.2 6.x-1.2 Up to date
Backup and Migrate 6.x-1.2 6.x-1.3 Update available
Better Formats 6.x-1.2 6.x-1.2 Up to date
Drupal 6.15 6.17 SECURITY UPDATE available
404 Blocks 6.x-1.1 6.x-1.2 Update available
Block Theme 6.x-1.0-beta1 6.x-1.0-beta1 Up to date
Content Construction Kit 6.x-2.6 6.x-2.7 SECURITY UPDATE available
(CCK)
Chaos tool suite 6.x-1.3 6.x-1.6 SECURITY UPDATE available
Custom Breadcrumbs 6.x-2.0-beta2 6.x-2.0-beta3 Update available
Date 6.x-2.4 6.x-2.4 Up to date
FileField 6.x-3.2 6.x-3.5 SECURITY UPDATE available
Global Redirect 6.x-1.2 6.x-1.2 Up to date
Google Analytics 6.x-2.2 6.x-2.2 Up to date
ImageAPI 6.x-1.6 6.x-1.8 Update available
ImageCache 6.x-2.0-beta10 6.x-2.0-beta10 Up to date
ImageField 6.x-3.2 6.x-3.3 SECURITY UPDATE available
IMCE 6.x-1.3 6.x-1.4 Update available
IMCE Wysiwyg bridge 6.x-1.0 6.x-1.1 Update available
Insert View 6.x-1.0 6.x-2.x-dev Update available
jQuery Update 6.x-2.x-dev 6.x-2.0-alpha1 Update available
Link 6.x-2.9 6.x-2.9 Up to date
Link checker 6.x-2.4 6.x-2.4 Up to date
Menu Attributes 6.x-1.4 6.x-1.4 Up to date
Menu Breadcrumb 6.x-1.3 6.x-1.3 Up to date
Menu CSS Names 6.x-1.1 6.x-1.1 Up to date
Nodewords 6.x-1.11 6.x-1.11 Up to date
Panels 6.x-3.3 6.x-3.5 SECURITY UPDATE available
Path redirect 6.x-1.0-beta6 6.x-1.0-beta6 Up to date
Pathauto 6.x-1.x-dev 6.x-1.3 Update available
Permission Select 6.x-1.8 6.x-1.8 Up to date
Poormanscron 6.x-2.2 6.x-2.2 Up to date
Slider 6.x-1.4 6.x-1.4 Up to date
Tabs (jQuery UI tabs) 6.x-1.3 6.x-1.3 Up to date
Token 6.x-1.12 6.x-1.13 Update available
Vertical Tabs 6.x-1.0-rc1 6.x-1.0-rc1 Up to date
Views 6.x-2.8 6.x-2.11 SECURITY UPDATE available
Views attach 6.x-2.2 6.x-2.2 Up to date
Views Bulk Operations (VBO) 6.x-1.9 6.x-1.9 Up to date
Views Slideshow 6.x-2.1 6.x-2.2 Update available
Views Tabs 6.x-1.0-beta1 6.x-1.0-beta1 Up to date
Webform 6.x-2.9 6.x-2.9 Up to date
Webform2Sugar: Capture 6.x-3.0-beta2 6.x-3.0-beta2 Up to date
webform result as new leads
in SugarCRM
Workflow 6.x-1.3 6.x-1.4 SECURITY UPDATE available
Wysiwyg 6.x-2.0 6.x-2.1 Update available
Genesis 6.x-2.4 6.x-2.4 Up to date
NOTE: A code update for the Drupal core is available.
Drupal core will be updated after all of the non-core modules are updated.
Code updates will be made to the following projects:
Backup and Migrate [backup_migrate-6.x-1.3], 404 Blocks [blocks404-6.x-1.2], Content Construction Kit (CCK) [cck-6.x-2.7], Chaos tool suite [ctools-6.x-1.6], Custom Breadcrumbs [custom_breadcrumbs-6.x-2.0-beta3], FileField [filefield-6.x-3.5], ImageAPI [imageapi-6.x-1.8], ImageField [imagefield-6.x-3.3], IMCE [imce-6.x-1.4], IMCE Wysiwyg bridge [imce_wysiwyg-6.x-1.1], Insert View [insert_view-6.x-2.x-dev], jQuery Update [jquery_update-6.x-2.0-alpha1], Panels [panels-6.x-3.5], Pathauto [pathauto-6.x-1.3], Token [token-6.x-1.13], Views [views-6.x-2.11], Views Slideshow [views_slideshow-6.x-2.2], Workflow [workflow-6.x-1.4], Wysiwyg [wysiwyg-6.x-2.1]
Note: Updated projects can potentially break your site. It is NOT recommended to update production sites without prior testing.
Note: A backup of your package will be stored to backups directory if it is not managed by a supported version control system.
Note: If you have made any modifications to any file that belongs to one of these projects, you will have to migrate those modifications after updating.
Project backup_migrate was updated successfully. Installed version is now 6.x-1.3.
Backups were saved into the directory [ok]
/var/www/html/backup/modules/20100623152801/backup_migrate.
Project blocks404 was updated successfully. Installed version is now 6.x-1.2.
Backups were saved into the directory [ok]
/var/www/html/backup/modules/20100623152801/blocks404.
Project cck was updated successfully. Installed version is now 6.x-2.7.
Backups were saved into the directory [ok]
/var/www/html/backup/modules/20100623152801/cck.
Project ctools was updated successfully. Installed version is now 6.x-1.6.
Backups were saved into the directory [ok]
/var/www/html/backup/modules/20100623152801/ctools.
Project custom_breadcrumbs was updated successfully. Installed version is now 6.x-2.0-be ta3.
Backups were saved into the directory [ok]
/var/www/html/backup/modules/20100623152801/custom_breadcrumbs.
Project filefield was updated successfully. Installed version is now 6.x-3.5.
Backups were saved into the directory [ok]
/var/www/html/backup/modules/20100623152801/filefield.
Project imageapi was updated successfully. Installed version is now 6.x-1.8.
Backups were saved into the directory [ok]
/var/www/html/backup/modules/20100623152801/imageapi.
Project imagefield was updated successfully. Installed version is now 6.x-3.3.
Backups were saved into the directory [ok]
/var/www/html/backup/modules/20100623152801/imagefield.
Project imce was updated successfully. Installed version is now 6.x-1.4.
Backups were saved into the directory [ok]
/var/www/html/backup/modules/20100623152801/imce.
Project imce_wysiwyg was updated successfully. Installed version is now 6.x-1.1.
Backups were saved into the directory [ok]
/var/www/html/backup/modules/20100623152801/imce_wysiwyg.
Project insert_view was updated successfully. Installed version is now 6.x-2.x-dev.
Backups were saved into the directory [ok]
/var/www/html/backup/modules/20100623152801/insert_view.
The jquery_update directory could not be found within the modules directory [error]
at /var/www/html/sites, perhaps the project is enabled but has been deleted
from disk.
An error occurred at function : drush_pm_updatecode [error]
WD php: [error]
rename(/var/www/html/backup/modules/20100623152801/insert_view,/var/www/html/sites/all/modules/insert_view):
Directory not empty in /root/drush/includes/drush.inc on line 595.
Could not restore backup and rollback from failed upgrade. You will need to [error]
resolve manually.
WD php: [error]
rename(/var/www/html/backup/modules/20100623152801/imce_wysiwyg,/var/www/html/sites/all/modules/imce_wysiwyg):
Directory not empty in /root/drush/includes/drush.inc on line 595.
Could not restore backup and rollback from failed upgrade. You will need to [error]
resolve manually.
WD php: [error]
rename(/var/www/html/backup/modules/20100623152801/imce,/var/www/html/sites/all/modules/imce):
Directory not empty in /root/drush/includes/drush.inc on line 595.
Could not restore backup and rollback from failed upgrade. You will need to [error]
resolve manually.
WD php: [error]
rename(/var/www/html/backup/modules/20100623152801/imagefield,/var/www/html/sites/all/modules/imagefield):
Directory not empty in /root/drush/includes/drush.inc on line 595.
Could not restore backup and rollback from failed upgrade. You will need to [error]
resolve manually.
WD php: [error]
rename(/var/www/html/backup/modules/20100623152801/imageapi,/var/www/html/sites/all/modules/imageapi):
Directory not empty in /root/drush/includes/drush.inc on line 595.
Could not restore backup and rollback from failed upgrade. You will need to [error]
resolve manually.
WD php: [error]
rename(/var/www/html/backup/modules/20100623152801/filefield,/var/www/html/sites/all/modules/filefield):
Directory not empty in /root/drush/includes/drush.inc on line 595.
Could not restore backup and rollback from failed upgrade. You will need to [error]
resolve manually.
WD php: [error]
rename(/var/www/html/backup/modules/20100623152801/custom_breadcrumbs,/var/www/html/sites/all/modules/custom_breadcrumbs):
Directory not empty in /root/drush/includes/drush.inc on line 595.
Could not restore backup and rollback from failed upgrade. You will need to [error]
resolve manually.
WD php: [error]
rename(/var/www/html/backup/modules/20100623152801/ctools,/var/www/html/sites/all/modules/ctools):
Directory not empty in /root/drush/includes/drush.inc on line 595.
Could not restore backup and rollback from failed upgrade. You will need to [error]
resolve manually.
WD php: [error]
rename(/var/www/html/backup/modules/20100623152801/cck,/var/www/html/sites/all/modules/cck):
Directory not empty in /root/drush/includes/drush.inc on line 595.
Could not restore backup and rollback from failed upgrade. You will need to [error]
resolve manually.
WD php: [error]
rename(/var/www/html/backup/modules/20100623152801/blocks404,/var/www/html/sites/all/modules/blocks404):
Directory not empty in /root/drush/includes/drush.inc on line 595.
Could not restore backup and rollback from failed upgrade. You will need to [error]
resolve manually.
WD php: [error]
rename(/var/www/html/backup/modules/20100623152801/backup_migrate,/var/www/html/sites/all/modules/backup_migrate):
Directory not empty in /root/drush/includes/drush.inc on line 595.
Could not restore backup and rollback from failed upgrade. You will need to [error]
resolve manually.
WD php: array_merge(): Argument #2 is not an array in [error]
/root/drush/commands/pm/updatecode.pm.inc on line 210.
An error occurred at function : drush_pm_update [error]
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | drush-836198.patch | 2.97 KB | jonhattan |
| #4 | drush-836198.patch | 2.61 KB | jonhattan |
Comments
Comment #1
stkrzysiak commentedI'm experiencing the same issue. Drush works just fine on my 4 other drupal sites on the same server but fails with one. The one in question is archaic, in fact it's one of my first drupal sites. I am inclined this error is happening due to something wrong I did as a n00b. I will work on this today and update if I find a fix.
Comment #2
stkrzysiak commentedNote sure what I did to fix it, but here are steps I took
1)I checked & removed potentially hidden CVS files(git, svn for git: find . -type d -name .git -exec rm -rf '{}' +), this didn't seem to do anything which i expected(didn't version control this site, but was bit before by copying over a version controlled module from another site).
2)Moved the modules/backup folder to tmp. i did this several times, didn't seem to fix anything.
3)Manually downloaded a handful of modules that needed an update using drush dl. These downloads succeeded, but yet drush told me they still needed updates. It seemed like drush had cached version data?
4)I started tracing out where the projects array was created in drush. In particular, I was curious why drush told me a module path was invalid even though it existed. While doing this and finally getting to the point where the module update candidates were created, I noticed drush was no longer telling me I needed to update any modules! A few echo statements and var _dumps were the only php interaction and yet something seemed to have clicked.
Everything is working fine now. I wish I had a quick fix for others, but perhaps my steps/process will help somehow.
Comment #3
jonhattanI think of two things: something wrong with symlinks or, as of the report in #0 having jquery_update inside other project's folder, that was already moved out to backup.
Comment #4
jonhattanI've hit this also today. In my case I was doing some testing to updatecode by updating and then downloading older version of projects and running again upc.
Didn't trace that it in deep but found a problem: update_status cache is invalid once you've updated any project, and drush doesn't clear that cache.
So this patch is at least part of the fix.
Comment #5
moshe weitzman commentedLooks reasonable to me.
Comment #6
jonhattanOn a second look at this now I think we need to invalidate this cache always, before running the command: we don't know if a project's code was updated by hand or drush dl and the cache has not been refreshed.
Comment #7
moshe weitzman commentedOK. We should probably remove pm-refesh, no?
Comment #8
jonhattanAfter a walk on update module I've found a `killer feature`: update_project_cache() selectively clear caches based on the page you're visiting.
#4 discarded. Attached patch make pm-updatecode show the same as the update status page.
Comment #9
jonhattanAbove patch also fixes pm-refresh for D7 (it was calling other function).
We do not invalidate the remote xml cached data. So pm-refresh is still necesary. What we gain here is that the updatecode table is in sync with the status of the modules (enabled,disabled,changed-updated on disk).
Comment #10
jonhattanChanging title according to #4 and below. Will commit as it doesn't hurt but introduce some fixes.
Comment #11
jonhattanComment #13
AdrianB commentedI got hit by this today, using Drush 4.0-rc3. Don't know if it's a one time issue (this is the first time I used Drush 4).