Closed (fixed)
Project:
Drush
Component:
PM (dl, en, up ...)
Priority:
Major
Category:
Support request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
15 Apr 2012 at 14:19 UTC
Updated:
3 Sep 2019 at 10:52 UTC
Jump to comment: Most recent
Comments
Comment #1
svdoord commentedI have the same problem. Any news on this?
(repeat ad infinitum)
Comment #2
Anonymous (not verified) commentedSame problem, drush up is looping forever in Drush 5 on my server. I'm using it with the -l flag for a multisite install if that matters.
Comment #3
moshe weitzman commentedIf anyone is willing, it would be helpful if you could create a site-archive and post it here. You would have to sanitize the database and filesystem if you have any private data there.
Also, use updatecode and then updatedb. Those are the 2 steps that update command does and it would help isolate the problem if more if we know where the problem is.
Comment #4
Anonymous (not verified) commentedHere is the output of updatecode. It happens at that step:
drushclp upc -v admin_menu
Initialized Drupal 7.12 root directory at [notice]
/home/web/actonweb/acton-drupal7
Initialized Drupal site www.clpress.com at sites/clpress.com [notice]
Loading release_info engine. [notice]
Loading version_control engine. [notice]
Loading package_handler engine. [notice]
Executing: wget --version
php /home/web/actonweb/drush/drush.php --backend=2 --verbose [notice]
--root=/home/web/actonweb/acton-drupal7 --uri=http://www.clpress.com
batch-process 59 59 2>&1
php /home/web/actonweb/drush/drush.php --backend=2 --verbose [notice]
--root=/home/web/actonweb/acton-drupal7 --uri=http://www.clpress.com
batch-process 59 59 2>&1
... to eternity with the last php line.
I thought it might be that my server's php command is 5.2.1 while I run the virtualhost at 5.2.16, but when I aliased php to the 5.2.16 version it didn't make a difference.
Comment #5
jonhattanplease post the debug output:
drush -d upc.Perhaps you're hitting #1420372: Modules being checked for updates multiple times..? See comment #2 there.
Comment #6
datarazor commentedHi there, I get the exact same issue. Here is the result of my output:
This last line then loops forever, just gaining in MB with each loop... ad infinitude.
I tried to follow:
http://drupal.org/node/1420372
http://drupal.org/node/1387034
http://drupal.org/node/1352102
But none of the solutions given (or workarounds) help.
Deleted queues table, ran drush cc all, ran drush pm-refresh, restarted my apache and mysql server, nothing improves the situation. I should add that drush works fine on drupal 6 sites, but on drupal 7 sites, it just loops for ever (aka hangs) and doesn't ever do anything.
Additional info:
Was attempting to use:
drush up drupal
to go from Drupal 7.12 to 7.14.
Thanks for any help you can offer.
Comment #7
sam mooreSame problem here.
On drush pm-update, it seems to do the code updates, but stall at the DB update. just sits there forever.
I finally killed the drush process and ran the updates from the Drupal admin interface, and that was successful.
Would be glad to post a sample site if that would help - I have something in development that's fairly innocuous...?
Comment #8
moshe weitzman commentedAs I posted in #3, a site-archive posted here would be most appreciated. Also, please try with latest dev snapshot of Drush and not just with 5.1
Comment #9
moshe weitzman commentedI just went through the scenario posted here and could not reproduce the bug using current drush from git master
- download drupal-7.12
- install 7.12
- updatecode to 7.14
- updatedb
That sequence ran fine.
Comment #10
sam mooreSadly, the site's way too big to upload - just noticed the 3MB limit.
I could pop it on a server somewhere for you if you like - drop me a note at info at resonetrics dot com if that would help..
Comment #11
moshe weitzman commentedYes, that would help. Please upload it and post the URL here. That way, many people can work on the fix.
Comment #12
sam moorehttp://dl.dropbox.com/u/78569432/bluec_db.sql.zip and
http://dl.dropbox.com/u/78569432/bluec.tar.gz
I hacked some users out of the SQL - the current superuser is called "superuser" and its password is "Strang3l0v3" - hope I didn't break the SQL in the process.
Anyway post again if you need more info on the site.
It is up to date, so you may want to roll back a db update or two...
Comment #13
moshe weitzman commentedThanks. I just got this running but I don't see how to reproduce a problem. i temporarily added a new update function and updatedb handled it fine.
Comment #14
sam mooreWell I'm mystified. I've been seeing this for a few update rounds now, just figured it was something on my VPS.
I'll see if I can get it to happen on my local MAMP setup. Not today though, sorry...
PS just in general, thanks for a lovely piece of kit. It really does help a lot.
Comment #15
sam mooreMoshe, could you give some idea of the most critical bits of tech in the environment that drush relies on? I'd like to try comparing my VPS vs. local environments, and don't know where to look for significant differences.
So particular libraries? PHP version? Anything like that.
Comment #16
ebenfarnworth commentedSubscribing
Comment #17
Anonymous (not verified) commentedMy problem was actually that Drush was using an older PHP version on the server. When I configured the DRUSH_PHP variable to the one the sites use things seemed to start working. The other PHP didn't have PDO.
Comment #18
Anonymous (not verified) commentedAha. My .bash_profile file had an "export PATH" that didn't exist. I updated this to the correct php directory and all is working with drush 5.2.
Comment #19
sam mooreJust a quick update on this - updated drush to 5.2 and things are back to normal now.
Comment #20
moshe weitzman commented