Re: Mercurial repository access error post rb-site upgrade "Something broke! (Error 500)"

Hi Christian, Thanks for the inputs . As updated in the other thread, copying over the SECRET_KEY from older instance to newer instance helped solve the problem, though the server logs & the error in itself were misleading. -- Harish On Sunday, 31 July 2016 01:50:16 UTC+5:30, Christian

Re: Backup and Restore of Reviewboard 2.0 failing (mysqldump issues)

Hi Christian, Thanks for looking into this. As suggested by Eric, and per update in your mail, I copied over the SECRET_KEY, and restarted httpd, and now the repositories are accessible and also, the previous review requests created in the older server show up their diff's correcty, which was

Re: Mercurial repository access error post rb-site upgrade "Something broke! (Error 500)"

Hi Harish, Can you show me the entire stack trace from the reviewboard.log file? The database may have been set for UTF-8, but that doesn't mean the tables or data was converted for that. If you look at the MySQL dump, you'll see that each table specifies its encoding. By default for some

Re: Backup and Restore of Reviewboard 2.0 failing (mysqldump issues)

Ah, I see you have another thread on this. I'll respond there. Christian -- Christian Hammond President/CEO of Beanbag Makers of Review Board On Sat, Jul 30, 2016 at 1:12 PM, Christian Hammond wrote: > Hi

Re: Backup and Restore of Reviewboard 2.0 failing (mysqldump issues)

Hi Harish, I'm not sure I fully understand what problems you're hitting, but a couple notes: 1) If you're using a database that was set up on an older instance, then yes, SECRET_KEY must be copied over. If it was not, a number of things like stored database passwords or hosting service auth