Upgrade to 2.0.2 Failed
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 upgrade on the staging server worked flawlessly; I don't know what's different here.) Is there any way to apply the evolutions that are missing using the rb-site upgrade mechanism, or will I need to resort to applying the schema manually? -- begin log output -- Creating tables ... Upgrading Review Board from 2.0 to 2.0.2 There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for hostingsvcs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) CommandError: Error applying evolution: (1054, Unknown column 'show_submitted' in 'accounts_profile') Thanks, Andrew -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Upgrade to 2.0.2 Failed
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 2.0.2, with a handful of unapplied evolutions that I would only expect if coming from 1.7.21. Was the killed upgrade from 1.7.21 to 2.0? Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 1, 2014 at 10:12:54 AM, Andrew Hills (anhills) (anhi...@cisco.com) wrote: 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 upgrade on the staging server worked flawlessly; I don't know what's different here.) Is there any way to apply the evolutions that are missing using the rb-site upgrade mechanism, or will I need to resort to applying the schema manually? -- begin log output -- Creating tables ... Upgrading Review Board from 2.0 to 2.0.2 There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for hostingsvcs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) CommandError: Error applying evolution: (1054, Unknown column 'show_submitted' in 'accounts_profile') Thanks, Andrew -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Upgrade to 2.0.2 Failed
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 database and then take it table by table. If there's a way I can hijack the rb-site upgrade process, though, I'd prefer that option. Thanks, Andrew On Jul 1, 2014, at 1:52 PM, Christian Hammond christ...@beanbaginc.commailto:christ...@beanbaginc.com wrote: 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 2.0.2, with a handful of unapplied evolutions that I would only expect if coming from 1.7.21. Was the killed upgrade from 1.7.21 to 2.0? Christian -- Christian Hammond - christ...@beanbaginc.commailto:christ...@beanbaginc.com Review Board - http://www.reviewboard.orghttp://www.reviewboard.org/ Beanbag, Inc. - http://www.beanbaginc.comhttp://www.beanbaginc.com/ On July 1, 2014 at 10:12:54 AM, Andrew Hills (anhills) (anhi...@cisco.commailto:anhi...@cisco.com) wrote: 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 upgrade on the staging server worked flawlessly; I don't know what's different here.) Is there any way to apply the evolutions that are missing using the rb-site upgrade mechanism, or will I need to resort to applying the schema manually? -- begin log output -- Creating tables ... Upgrading Review Board from 2.0 to 2.0.2 There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for hostingsvcs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) CommandError: Error applying evolution: (1054, Unknown column 'show_submitted' in 'accounts_profile') Thanks, Andrew -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.commailto:reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Upgrade to 2.0.2 Failed
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 the INSERTs from your old database, trying to restore them as best as possible under the new one. You will hit problems with missing columns, though, requiring that you hand-edit any referring to missing columns (and adjusting the data being inserted to match the equivalent columns from the table). There’s a lot of hard work to do there. We can offer one-on-one assistance with getting your existing database back in shape, but that really falls into the realm of our support contracts. We can talk about that more in private if that’s of interest. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 1, 2014 at 11:38:33 AM, Andrew Hills (anhills) (anhi...@cisco.com) wrote: 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 database and then take it table by table. If there’s a way I can hijack the rb-site upgrade process, though, I’d prefer that option. Thanks, Andrew On Jul 1, 2014, at 1:52 PM, Christian Hammond christ...@beanbaginc.com wrote: 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 2.0.2, with a handful of unapplied evolutions that I would only expect if coming from 1.7.21. Was the killed upgrade from 1.7.21 to 2.0? Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 1, 2014 at 10:12:54 AM, Andrew Hills (anhills) (anhi...@cisco.com) wrote: 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 upgrade on the staging server worked flawlessly; I don't know what's different here.) Is there any way to apply the evolutions that are missing using the rb-site upgrade mechanism, or will I need to resort to applying the schema manually? -- begin log output -- Creating tables ... Upgrading Review Board from 2.0 to 2.0.2 There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for hostingsvcs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) CommandError: Error applying evolution: (1054, Unknown column 'show_submitted' in 'accounts_profile') Thanks, Andrew -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving
Re: Upgrade to 2.0.2 Failed
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 Hammond christ...@beanbaginc.commailto:christ...@beanbaginc.com wrote: 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 the INSERTs from your old database, trying to restore them as best as possible under the new one. You will hit problems with missing columns, though, requiring that you hand-edit any referring to missing columns (and adjusting the data being inserted to match the equivalent columns from the table). There's a lot of hard work to do there. We can offer one-on-one assistance with getting your existing database back in shape, but that really falls into the realm of our support contracts. We can talk about that more in private if that's of interest. Christian -- Christian Hammond - christ...@beanbaginc.commailto:christ...@beanbaginc.com Review Board - http://www.reviewboard.orghttp://www.reviewboard.org/ Beanbag, Inc. - http://www.beanbaginc.comhttp://www.beanbaginc.com/ On July 1, 2014 at 11:38:33 AM, Andrew Hills (anhills) (anhi...@cisco.commailto:anhi...@cisco.com) wrote: 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 database and then take it table by table. If there's a way I can hijack the rb-site upgrade process, though, I'd prefer that option. Thanks, Andrew On Jul 1, 2014, at 1:52 PM, Christian Hammond christ...@beanbaginc.commailto:christ...@beanbaginc.com wrote: 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 2.0.2, with a handful of unapplied evolutions that I would only expect if coming from 1.7.21. Was the killed upgrade from 1.7.21 to 2.0? Christian -- Christian Hammond - christ...@beanbaginc.commailto:christ...@beanbaginc.com Review Board - http://www.reviewboard.orghttp://www.reviewboard.org/ Beanbag, Inc. - http://www.beanbaginc.comhttp://www.beanbaginc.com/ On July 1, 2014 at 10:12:54 AM, Andrew Hills (anhills) (anhi...@cisco.commailto:anhi...@cisco.com) wrote: 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 upgrade on the staging server worked flawlessly; I don't know what's different here.) Is there any way to apply the evolutions that are missing using the rb-site upgrade mechanism, or will I need to resort to applying the schema manually? -- begin log output -- Creating tables ... Upgrading Review Board from 2.0 to 2.0.2 There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for hostingsvcs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) CommandError: Error applying evolution: (1054, Unknown column 'show_submitted' in 'accounts_profile') Thanks, Andrew -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.commailto:reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You
Re: Upgrade to 2.0.2 Failed
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, 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 Hammond christ...@beanbaginc.com wrote: 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 the INSERTs from your old database, trying to restore them as best as possible under the new one. You will hit problems with missing columns, though, requiring that you hand-edit any referring to missing columns (and adjusting the data being inserted to match the equivalent columns from the table). There’s a lot of hard work to do there. We can offer one-on-one assistance with getting your existing database back in shape, but that really falls into the realm of our support contracts. We can talk about that more in private if that’s of interest. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 1, 2014 at 11:38:33 AM, Andrew Hills (anhills) (anhi...@cisco.com) wrote: 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 database and then take it table by table. If there’s a way I can hijack the rb-site upgrade process, though, I’d prefer that option. Thanks, Andrew On Jul 1, 2014, at 1:52 PM, Christian Hammond christ...@beanbaginc.com wrote: 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 2.0.2, with a handful of unapplied evolutions that I would only expect if coming from 1.7.21. Was the killed upgrade from 1.7.21 to 2.0? Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On July 1, 2014 at 10:12:54 AM, Andrew Hills (anhills) (anhi...@cisco.com) wrote: 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 upgrade on the staging server worked flawlessly; I don't know what's different here.) Is there any way to apply the evolutions that are missing using the rb-site upgrade mechanism, or will I need to resort to applying the schema manually? -- begin log output -- Creating tables ... Upgrading Review Board from 2.0 to 2.0.2 There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for hostingsvcs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) CommandError: Error applying evolution: (1054, Unknown column 'show_submitted' in 'accounts_profile') Thanks, Andrew -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this
