Hi all,
During an upgrade from 1.7.21 to 2.0.2, rb-site upgrade hung. I killed it, and
running it again yields the error below, and now no combination of versions
works. My last database backup is not so very old, but I'd really rather not
lose anything if it's possible to avoid it. (The
Hi Andrew,
At what point did it hang? This looks very much like the process was killed
while it was performing database migrations, which is not something you can
easily recover from without a lot of manual surgery.
You said you upgraded from 1.7.21 to 2.0.2, but that log is showing 2.0 to
Hi Christian,
Yeah, sorry, I took it through a few versions before calling for help. The
killed upgrade was 1.7.21 to 2.0.2. I'm willing to do the manual surgery--I've
got the MySQL manual open--but I don't know where to start. My first thought
was to create a new 2.0.2 installation and
Hi Andrew,
The surgery, depending on when the process was killed, would require a lot of
deep knowledge of how evolutions work, how they relate to the table changes,
and some improvisation.
If you wanted to just try to re-create the database, you could try a new
install and then dumping all
Hi all,
I just wanted to note that my issue was resolved completely and very quickly
with Christian's help; I couldn't be happier with the outcome. If you're on the
fence, you can take my word for it: support doesn't get better than this.
Thanks,
Andrew
On Jul 1, 2014, at 2:44 PM, Christian
Thanks for the kind words, Andrew! :) Glad things are working!
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On July 1, 2014 at 5:19:50 PM, Andrew Hills (anhills) (anhi...@cisco.com) wrote:
Hi all,