It looks like your table charsets aren't set properly in MySQL. I'd go in with the MySQL client and set them all to utf-8.
-David > On Jun 27, 2014, at 12:08 PM, sagar <[email protected]> wrote: > > There are three log files for apache: > > other_vhosts_access.log: > >> codereview.nyab-tds:80 149.244.179.118 - - [27/Jun/2014:19:03:44 +0000] "-" >> 408 0 "-" "-" >> codereview.nyab-tds:80 149.244.178.251 - - [27/Jun/2014:19:03:54 +0000] "GET >> /dashboard/ HTTP/1.1" 200 4318 "http://codereview.nyab-tds/dashboard/"; >> "Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0" >> codereview.nyab-tds:80 149.244.179.84 - - [27/Jun/2014:19:04:00 +0000] "-" >> 408 0 "-" "-" >> codereview.nyab-tds:80 149.244.179.96 - - [27/Jun/2014:19:04:10 +0000] "GET >> /api/review-requests/1280/last-update/?api_format=json HTTP/1.1" 304 273 >> "http://dfws0237.corp.knorr-bremse.com/r/1280/"; "Mozilla/5.0 (X11; Linux >> x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.132 >> Safari/537.36" > > access.log is blank > > error.log: > >> Error opening file for reading: Permission denied >> [Fri Jun 27 18:07:41 2014] [error] >> /usr/local/lib/python2.7/dist-packages/Django-1.4.8-py2.7.egg/django/db/backends/mysql/base.py:114: >> Warning: Incorrect string value: '\\xE2\\x88\\x92 (1...' for column >> 'description' at row 1 >> [Fri Jun 27 18:07:41 2014] [error] return self.cursor.execute(query, args) > > > >> On Friday, 27 June 2014 12:25:08 UTC-5, David Trowbridge wrote: >> What about the apache error logs? >> >> -David >> >>> On Jun 27, 2014, at 8:24 AM, sagar <[email protected]> wrote: >>> >>> Hi! >>> >>> We are currently on 1.7.14 and I am looking to upgrade us to 2.0.2. >>> >>> I've tried 3 paths to upgrade (all following the RB instructions - upgrade >>> RB, upgrade site, restart apache and memcached): >>> >>> 1.7.14 -> 2.0.2 >>> >>> 1.7.14 -> 1.7.26 -> 2.0.2 >>> >>> 1.7.14 -> 2.0.1 -> 2.0.2 >>> >>> I didn't go from 1.7.14 to 1.7.26 to 2.0.1 because of the schema change >>> issue; figured it was probably not a good idea. >>> >>> The upgrade seems to be successful each time. However, the moment I try to >>> go to the site, I get the following error: >>> >>> >>> Something broke! (Error 500) >>> >>> It appears something broke when you tried to go to here. This is either a >>> bug in Review Board or a server configuration error. Please report this to >>> your administrator." >>> >>> >>> I tried looking at the server log but there was nothing there (last entry >>> was review related). I deleted the old log to see if one would get created, >>> but no joy. Not sure how to debug this. >>> >>> Has anyone had this issue, and any ideas what I could to upgrade >>> successfully? >>> >>> The rb-site upgrade output for path 1 (1.7.14 -> 2.0.2) is below: >>> >>> ------------- <begin log output> ----------- >>> >>> Creating tables ... >>> Upgrading Review Board from 1.7.14 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. >>> There are unapplied evolutions for site. >>> Adding baseline version for new models >>> Project signature has changed - an evolution is required >>> Installing custom SQL ... >>> Installing indexes ... >>> Installed 0 object(s) from 0 fixture(s) >>> Evolution successful. >>> ------------- <end log output> ----------- >>> >>> Resetting in-database caches >>> Upgrade complete! >>> >>> >>> >>> -- >>> 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 [email protected]. >>> 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
