Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
If you got broken revisions in your node table then the update process runs into an infinite loop.
Patch forthcoming.
Comment | File | Size | Author |
---|---|---|---|
#1 | infinite_loop.patch.txt | 7.05 KB | killes@www.drop.org |
Comments
Comment #1
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedComment #2
ultraBoy CreditAttribution: ultraBoy commentedSorry, what "broken revisions" are? I have an idea about revisions, but what means "broken"?
Comment #3
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedIn 4.6 and before revisions were stored as a serialized field. If for some reason this field can't be unserialized anymore, I refer to it as being broken.
Comment #4
beginner CreditAttribution: beginner commentedok. I have just been a victim of this bug.
Before I found the patch, I completed the upgrade by skipping update#159 and starting again at #160.
I don't really care about revisions, but do you think there is some clean up I should do?
Can I patch the file and run update#159 only? (later updates have all been completed).
thanks.
Comment #5
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedCommitted to 4.7
Comment #6
drummCommitted to HEAD.
Comment #7
urbanfalcon CreditAttribution: urbanfalcon commentedHaving the same issue where the update dies at #159. I pulled a copy of the updates.inc file off CVS, too, so it should have had this patch already incorporated. I ended up having to remove my revisions in order to proceed. I would not doubt that some node revisions were serialized with errors. So the original assessment of death at #159 is still plausible for me, especially with a successful update after I emptied all revisions from the database. Unfortunately, my system has over 6000 nodes of information, so I don't know which node (or nodes) would be the culprit.
Comment #8
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedAre you sure your updates.inc has the patch? What is the cvs version at top of the file?
if you had the patch you would get watchdog erros about broken revisions.
Comment #9
urbanfalcon CreditAttribution: urbanfalcon commentedHmm. I was at http://cvs.drupal.org/viewcvs/drupal/drupal/database/updates.inc?rev=1.2... but I must have clicked the wrong "download" button because my header says:
// $Id: updates.inc,v 1.227 2006/05/12 08:50:22 dries Exp $
I'll re-download and confirm v.1.230 before attempting the final site update (I was just testing via a dev copy before). Thanks!
Jennifer
Comment #10
(not verified) CreditAttribution: commented