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

2017-06-26 Thread nick . nghiem
Thank you for the solution with the SECRET_KEY, this resolved my issue migrating ReviewBoard from FreeBSD to CentOS. On Saturday, July 30, 2016 at 9:32:37 PM UTC-4, harish varadarajan wrote: > > Hi Christian, > > Thanks for the inputs . > > As updated in the other thread, copying over the

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

2016-07-30 Thread harish varadarajan
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: Mercurial repository access error post rb-site upgrade "Something broke! (Error 500)"

2016-07-30 Thread Christian Hammond
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: Mercurial repository access error post rb-site upgrade "Something broke! (Error 500)"

2016-07-29 Thread harish varadarajan
Further, the reviewboard database was created with UTF8 character set. MariaDB [reviewboard]> show variables like "character_set_database"; ++---+ | Variable_name | Value | ++---+ | character_set_database | utf8 | The specific

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

2016-07-29 Thread harish varadarajan
Hi, I am pretty new to reviewboard and have attempted to migrate reviewboard instance across hosts and versions. Our older RB version was and the upgrade was to 2.5.6.1 Steps followed for the upgrade were (1) Dump data on the older server (mysql) (2) Drop the previously created reviewboard