Ok after some research on the mysql DB it looks like I'm running out of disk space on my mysql instance so now i'll have to go back and work on that. Most likely everything will work once that's fixed.
On Tuesday, August 22, 2017 at 10:17:52 AM UTC-7, Sean Smith wrote: > > Scratch that last question I just noticed the debug option, retrying the > migration using that. > > On Tuesday, August 22, 2017 at 10:15:16 AM UTC-7, Sean Smith wrote: >> >> Hey Christian, >> >> Sorry for the delay on my response, it took a while to get the test DB >> set back up because I got pulled onto other stuff, however it was using >> MyISAM so I replaced it with InnoDB and the migration is going a-lot >> smoother in that there aren't errors/stack traces, however I started it on >> Friday and it is still going right now according to rb-site. However >> running "show full processlist" on mysql shows that nothing is going on, so >> it's as if it hung part way thru applying changes for diffviewer. Is there >> any way to get more logging output during the migration given that the logs >> directory is empty? >> >> mysql> show full processlist; >> >> +----+------+-----------+------+---------+------+-------+-----------------------+ >> | Id | User | Host | db | Command | Time | State | Info >> | >> >> +----+------+-----------+------+---------+------+-------+-----------------------+ >> | 7 | root | localhost | NULL | Query | 0 | init | show full >> processlist | >> >> +----+------+-----------+------+---------+------+-------+-----------------------+ >> 1 row in set (0.00 sec) >> >> >> Thanks, >> Sean >> >> On Wednesday, August 16, 2017 at 12:57:58 PM UTC-7, Christian Hammond >> wrote: >>> >>> Hi Sean, >>> >>> This isn't normal, and upgrades from 1.7 to 2.5 should work smoothly. >>> >>> Something to check is the table formats. Older MySQL versions defaulted >>> to MyISAM, while newer ones default to InnoDB. This can be a source of >>> problems when upgrading and establishing foreign key relations. I'm used to >>> seeing a very different error in this case, but it's worth checking for. >>> >>> If you open your SQL database dump (assuming you made one via >>> mysqldump), you should be able to grep around for MYISAM. If you see those, >>> try changing them to INNODB and re-import the dump. >>> >>> If it's not that, I'll have other things for you to try. >>> >>> Christian >>> >>> >>> On Wed, Aug 16, 2017 at 11:29 Sean Smith <[email protected]> wrote: >>> >>>> I tested the migration from 1.7.28 to 2.0.30 and that went fine, >>>> however going from 2.0.30 to 2.5.13.1 I hit the same errors as above >>>> >>>> -- >>>> Supercharge your Review Board with Power Pack: >>>> https://www.reviewboard.org/powerpack/ >>>> Want us to host Review Board for you? Check out RBCommons: >>>> https://rbcommons.com/ >>>> Happy user? Let us know! https://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 [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> -- >>> Christian Hammond >>> President/CEO of Beanbag >>> Makers of Review Board >>> >> -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://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 [email protected]. For more options, visit https://groups.google.com/d/optout.
