Re: Issue upgrading from 1.7.14 to 2.0.2
The my.cnf settings affect new databases and tables. You'll also need to run some commands in the console to change the existing tables. -David On Mon, Jun 30, 2014 at 1:50 PM, sagar wrote: > > So I changed my.cnf and set the default character set to utf8. > > the apache log still shows: > > codereviewtest.nyab-tds:80 127.0.0.1 - - [30/Jun/2014:20:01:32 +] "GET > /admin/ HTTP/1.1" 500 551 "-" "Mozilla/5.0 (X11; Ubuntu; Linux i686; > rv:24.0) Gecko/20100101 Firefox/24.0" > > On Monday, 30 June 2014 14:39:49 UTC-5, sagar wrote: > >> I hadn't change anything in mysql, so that's weird. >> I'll try this and post in a bit. >> >> On Friday, 27 June 2014 15:01:43 UTC-5, David Trowbridge wrote: >> >>> 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 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 +] "-" 408 0 "-" "-" codereview.nyab-tds:80 149.244.178.251 - - [27/Jun/2014:19:03:54 +] "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 +] "-" 408 0 "-" "-" codereview.nyab-tds:80 149.244.179.96 - - [27/Jun/2014:19:04:10 +] "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 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: - --- 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. - --- 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 an
Re: Issue upgrading from 1.7.14 to 2.0.2
So I changed my.cnf and set the default character set to utf8. the apache log still shows: codereviewtest.nyab-tds:80 127.0.0.1 - - [30/Jun/2014:20:01:32 +] "GET /admin/ HTTP/1.1" 500 551 "-" "Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0" On Monday, 30 June 2014 14:39:49 UTC-5, sagar wrote: > I hadn't change anything in mysql, so that's weird. > I'll try this and post in a bit. > > On Friday, 27 June 2014 15:01:43 UTC-5, David Trowbridge wrote: > >> 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 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 +] >>> "-" 408 0 "-" "-" >>> codereview.nyab-tds:80 149.244.178.251 - - [27/Jun/2014:19:03:54 +] >>> "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 +] >>> "-" 408 0 "-" "-" >>> codereview.nyab-tds:80 149.244.179.96 - - [27/Jun/2014:19:04:10 +] >>> "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 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: >>> >>> - --- >>> >>> 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. >>> - --- >>> >>> 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 reviewboard...@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://rbco
Re: Issue upgrading from 1.7.14 to 2.0.2
I hadn't change anything in mysql, so that's weird. I'll try this and post in a bit. On Friday, 27 June 2014 15:01:43 UTC-5, David Trowbridge wrote: > 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 > > 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 +] >> "-" 408 0 "-" "-" >> codereview.nyab-tds:80 149.244.178.251 - - [27/Jun/2014:19:03:54 +] >> "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 +] >> "-" 408 0 "-" "-" >> codereview.nyab-tds:80 149.244.179.96 - - [27/Jun/2014:19:04:10 +] >> "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 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: >> >> - --- >> >> 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. >> - --- >> >> 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 reviewboard...@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...@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 R
Re: Issue upgrading from 1.7.14 to 2.0.2
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 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 +] "-" >> 408 0 "-" "-" >> codereview.nyab-tds:80 149.244.178.251 - - [27/Jun/2014:19:03:54 +] "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 +] "-" >> 408 0 "-" "-" >> codereview.nyab-tds:80 149.244.179.96 - - [27/Jun/2014:19:04:10 +] "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 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: >>> >>> - --- >>> >>> 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. >>> - --- >>> >>> 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 reviewboard...@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 kn
Re: Issue upgrading from 1.7.14 to 2.0.2
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 +] "-" > 408 0 "-" "-" > codereview.nyab-tds:80 149.244.178.251 - - [27/Jun/2014:19:03:54 +] > "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 +] "-" > 408 0 "-" "-" > codereview.nyab-tds:80 149.244.179.96 - - [27/Jun/2014:19:04:10 +] > "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 > > 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: > > - --- > > 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. > - --- > > 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 reviewboard...@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: Issue upgrading from 1.7.14 to 2.0.2
What about the apache error logs? -David > On Jun 27, 2014, at 8:24 AM, sagar 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: > > - --- > > 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. > - --- > > 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 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.
Issue upgrading from 1.7.14 to 2.0.2
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: - --- 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. - --- 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 reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue Upgrading.
The thing to check, then, is that you don't have multiple versions of Python with different versions of Review Board installed. Search the filesystem for ReviewBoard*.egg, and see what directories you find. Look at the Python directories they're in. Make sure they're all the Python version you expect. It's possible that on the command line you're using easy_install with one version and Apache is using another. If that's not it, try deleting the old version of Review Board and repeating your install. Look closely for installation errors at the end. Christan -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Mon, Feb 14, 2011 at 10:51 AM, Sapna Vempati wrote: > Hi Christian, > > We used "easy_install -U ReviewBoard" > > Thanks, > Sapna > > > On Sat, Feb 12, 2011 at 12:33 AM, Christian Hammond > wrote: > >> Hi Sapna, >> >> Review Board is going to show the version of the Review Board code being >> run in the Python interpreter for your site. This should be the latest >> version. If it's showing 1.0.x, then it sounds like either Review Board >> 1.5.x wasn't installed, or it's installed in some non-standard location >> somehow. >> >> Did you perform the upgrade with 'easy_install -U ReviewBoard', or just >> 'rb-site upgrade'? >> >> >> Christian >> >> -- >> Christian Hammond - chip...@chipx86.com >> Review Board - http://www.reviewboard.org >> VMware, Inc. - http://www.vmware.com >> >> >> On Fri, Feb 11, 2011 at 4:17 PM, Sapna Vempati wrote: >> >>> Thanks Christian. >>> >>> If the errors are just warnings, the issue is that we don't see a >>> complete installation and upgrade. The RB servers still shows as 1.0.X. >>> and not 1.5.3. >>> >>> Do you know how I could locate: cmemcache on the file system ? >>> >>> Thanks, >>> Sapna >>> >>> >>> On Fri, Feb 11, 2011 at 12:39 PM, Christian Hammond >> > wrote: >>> Hi Sapna, Going back to 1.5.1 from 1.5.3 unfortunately means removing the old version from the filesystem manually. At that point you can do: easy_install -U ReviewBoard==1.5.1 However, this won't fix the errors below. Those appear to me to be harmless. Are you hitting any real problems with the site? The mcm_storage_add errors appear to be from the old cmemcache libraries. If you can locate these on the filesystem and remove them, they should go away, as Django will fall back on the new libraries we now install along with Review Board. The current release of RBTools should be compatible with everything from 1.0.x to 1.5.3. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Fri, Feb 11, 2011 at 11:21 AM, Sapna Vempati >>> > wrote: > Hi Christian, > > Using the below command for upgrade, upgrades to the latest version > (1.5.3) by default. Is there a way we can upgrade to an older version we > prefer ? Like for example, we want to do install to RB1.5.1. Is it > possible > ? > > easy_install -U ReviewBoard > > Also, from the release notes, looks like this version has a newer > RBTools. Is this compatible with older RB versions ? > > When we try to upgrade using the above command, we got the below error, > so that's the reason we want to go back to older version to see if that > works. > > #[root@mob-rb-test /]# rb-site --debug upgrade > > > > > > > > /opt/lampp/htdocs/reviewboard > Rebuilding directory structure > > > > > > > > Updating database. This may take a while. > [NOTICE@1297389237.811425] mcm_storage_cmd():3334: unable > to store value: add > > > > > > > > [NOTICE@1297389237.845006] mcm_storage_cmd():3334: unable > to store value: add > > > > > > > > > [NOTICE@1297389237.866137] mcm_storage_cmd():3334: unable > to store value: add > [NOTICE@1297389237.900860] mcm_storage_cmd():3334: unable > to store value: add > > > > > > > > [NOTICE@1297389237.934480] mcm_storage_cmd():3334: unable > to store value: add > [NOTICE@1297389237.967112] mcm_storage_cmd():3334: unable > to store value: add > > > > > > > > > [NOTICE@1297389238.012221] mcm_storage_cmd():3334: unable > to store value: add > [NOTICE@1297389238.048986] mcm_storage_cmd():3334: unable > to store value: add > > > > > > > > > [NOTICE@1297389238.104145] mcm_storage_cmd():3334: unable
Re: Issue Upgrading.
Hi Christian, We used "easy_install -U ReviewBoard" Thanks, Sapna On Sat, Feb 12, 2011 at 12:33 AM, Christian Hammond wrote: > Hi Sapna, > > Review Board is going to show the version of the Review Board code being > run in the Python interpreter for your site. This should be the latest > version. If it's showing 1.0.x, then it sounds like either Review Board > 1.5.x wasn't installed, or it's installed in some non-standard location > somehow. > > Did you perform the upgrade with 'easy_install -U ReviewBoard', or just > 'rb-site upgrade'? > > > Christian > > -- > Christian Hammond - chip...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > > On Fri, Feb 11, 2011 at 4:17 PM, Sapna Vempati wrote: > >> Thanks Christian. >> >> If the errors are just warnings, the issue is that we don't see a complete >> installation and upgrade. The RB servers still shows as 1.0.X. and not >> 1.5.3. >> >> Do you know how I could locate: cmemcache on the file system ? >> >> Thanks, >> Sapna >> >> >> On Fri, Feb 11, 2011 at 12:39 PM, Christian Hammond >> wrote: >> >>> Hi Sapna, >>> >>> Going back to 1.5.1 from 1.5.3 unfortunately means removing the old >>> version from the filesystem manually. At that point you can do: >>> >>> easy_install -U ReviewBoard==1.5.1 >>> >>> However, this won't fix the errors below. Those appear to me to be >>> harmless. Are you hitting any real problems with the site? >>> >>> The mcm_storage_add errors appear to be from the old cmemcache libraries. >>> If you can locate these on the filesystem and remove them, they should go >>> away, as Django will fall back on the new libraries we now install along >>> with Review Board. >>> >>> The current release of RBTools should be compatible with everything from >>> 1.0.x to 1.5.3. >>> >>> Christian >>> >>> -- >>> Christian Hammond - chip...@chipx86.com >>> Review Board - http://www.reviewboard.org >>> VMware, Inc. - http://www.vmware.com >>> >>> >>> On Fri, Feb 11, 2011 at 11:21 AM, Sapna Vempati >>> wrote: >>> Hi Christian, Using the below command for upgrade, upgrades to the latest version (1.5.3) by default. Is there a way we can upgrade to an older version we prefer ? Like for example, we want to do install to RB1.5.1. Is it possible ? easy_install -U ReviewBoard Also, from the release notes, looks like this version has a newer RBTools. Is this compatible with older RB versions ? When we try to upgrade using the above command, we got the below error, so that's the reason we want to go back to older version to see if that works. #[root@mob-rb-test /]# rb-site --debug upgrade /opt/lampp/htdocs/reviewboard Rebuilding directory structure Updating database. This may take a while. [NOTICE@1297389237.811425] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389237.845006] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389237.866137] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389237.900860] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389237.934480] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389237.967112] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.012221] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.048986] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.104145] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.224780] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.273282] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.320729] mcm_storage_cmd():3334: unable to store value: add No fixtures found. /opt/lampp/lib/python2.5/site- packages/pycrypto-2.3-py2.5-linux-i686.egg/Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This application uses RandomPool, which is BROKEN in older releases. See http://www.pycrypto.org/randpool-broken RandomPool_DeprecationWarning) No evolution required. Upgrade complete. Thanks, Sapna -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/d
Re: Issue Upgrading.
Hi Sapna, Review Board is going to show the version of the Review Board code being run in the Python interpreter for your site. This should be the latest version. If it's showing 1.0.x, then it sounds like either Review Board 1.5.x wasn't installed, or it's installed in some non-standard location somehow. Did you perform the upgrade with 'easy_install -U ReviewBoard', or just 'rb-site upgrade'? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Fri, Feb 11, 2011 at 4:17 PM, Sapna Vempati wrote: > Thanks Christian. > > If the errors are just warnings, the issue is that we don't see a complete > installation and upgrade. The RB servers still shows as 1.0.X. and not > 1.5.3. > > Do you know how I could locate: cmemcache on the file system ? > > Thanks, > Sapna > > > On Fri, Feb 11, 2011 at 12:39 PM, Christian Hammond > wrote: > >> Hi Sapna, >> >> Going back to 1.5.1 from 1.5.3 unfortunately means removing the old >> version from the filesystem manually. At that point you can do: >> >> easy_install -U ReviewBoard==1.5.1 >> >> However, this won't fix the errors below. Those appear to me to be >> harmless. Are you hitting any real problems with the site? >> >> The mcm_storage_add errors appear to be from the old cmemcache libraries. >> If you can locate these on the filesystem and remove them, they should go >> away, as Django will fall back on the new libraries we now install along >> with Review Board. >> >> The current release of RBTools should be compatible with everything from >> 1.0.x to 1.5.3. >> >> Christian >> >> -- >> Christian Hammond - chip...@chipx86.com >> Review Board - http://www.reviewboard.org >> VMware, Inc. - http://www.vmware.com >> >> >> On Fri, Feb 11, 2011 at 11:21 AM, Sapna Vempati >> wrote: >> >>> Hi Christian, >>> >>> Using the below command for upgrade, upgrades to the latest version >>> (1.5.3) by default. Is there a way we can upgrade to an older version we >>> prefer ? Like for example, we want to do install to RB1.5.1. Is it possible >>> ? >>> >>> easy_install -U ReviewBoard >>> >>> Also, from the release notes, looks like this version has a newer >>> RBTools. Is this compatible with older RB versions ? >>> >>> When we try to upgrade using the above command, we got the below error, >>> so that's the reason we want to go back to older version to see if that >>> works. >>> >>> #[root@mob-rb-test /]# rb-site --debug upgrade >>> >>> >>> >>> >>> /opt/lampp/htdocs/reviewboard >>> Rebuilding directory structure >>> >>> >>> >>> >>> Updating database. This may take a while. >>> [NOTICE@1297389237.811425] mcm_storage_cmd():3334: unable to >>> store value: add >>> >>> >>> >>> >>> [NOTICE@1297389237.845006] mcm_storage_cmd():3334: unable to >>> store value: add >>> >>> >>> >>> >>> >>> [NOTICE@1297389237.866137] mcm_storage_cmd():3334: unable to >>> store value: add >>> [NOTICE@1297389237.900860] mcm_storage_cmd():3334: unable to >>> store value: add >>> >>> >>> >>> >>> [NOTICE@1297389237.934480] mcm_storage_cmd():3334: unable to >>> store value: add >>> [NOTICE@1297389237.967112] mcm_storage_cmd():3334: unable to >>> store value: add >>> >>> >>> >>> >>> >>> [NOTICE@1297389238.012221] mcm_storage_cmd():3334: unable to >>> store value: add >>> [NOTICE@1297389238.048986] mcm_storage_cmd():3334: unable to >>> store value: add >>> >>> >>> >>> >>> >>> [NOTICE@1297389238.104145] mcm_storage_cmd():3334: unable to >>> store value: add >>> >>> >>> >>> >>> [NOTICE@1297389238.224780] mcm_storage_cmd():3334: unable to >>> store value: add >>> >>> >>> >>> >>> [NOTICE@1297389238.273282] mcm_storage_cmd():3334: unable to >>> store value: add >>> >>> >>> >>> >>> [NOTICE@1297389238.320729] mcm_storage_cmd():3334: unable to >>> store value: add >>> >>>No fixtures found. >>> /opt/lampp/lib/python2.5/site-packages/pycrypto-2.3-py2.5- >>> linux-i686.egg/Crypto/Util/randpool.py:40: >>> RandomPool_DeprecationWarning: This application uses RandomPool, which is >>> BROKEN in older releases. See http://www.pycrypto.org/randpool-broken >>> >>> RandomPool_DeprecationWarning) >>> >>>No evolution required. >>>Upgrade complete. >>> Thanks, >>> Sapna >>> >>> -- >>> Want to help the Review Board project? Donate today at >>> http://www.reviewboard.org/donate/ >>> Happy user? Let us know at http://www.reviewboard.org/users/ >>> -~--~~~~--~~--~--~--- >>> To unsubscribe from this group, send email to >>> reviewboard+unsubscr...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/reviewboard?hl=en >> >> >> -- >> Want to help the Review Boa
Re: Issue Upgrading.
Thanks Christian. If the errors are just warnings, the issue is that we don't see a complete installation and upgrade. The RB servers still shows as 1.0.X. and not 1.5.3. Do you know how I could locate: cmemcache on the file system ? Thanks, Sapna On Fri, Feb 11, 2011 at 12:39 PM, Christian Hammond wrote: > Hi Sapna, > > Going back to 1.5.1 from 1.5.3 unfortunately means removing the old version > from the filesystem manually. At that point you can do: > > easy_install -U ReviewBoard==1.5.1 > > However, this won't fix the errors below. Those appear to me to be > harmless. Are you hitting any real problems with the site? > > The mcm_storage_add errors appear to be from the old cmemcache libraries. > If you can locate these on the filesystem and remove them, they should go > away, as Django will fall back on the new libraries we now install along > with Review Board. > > The current release of RBTools should be compatible with everything from > 1.0.x to 1.5.3. > > Christian > > -- > Christian Hammond - chip...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > > On Fri, Feb 11, 2011 at 11:21 AM, Sapna Vempati wrote: > >> Hi Christian, >> >> Using the below command for upgrade, upgrades to the latest version >> (1.5.3) by default. Is there a way we can upgrade to an older version we >> prefer ? Like for example, we want to do install to RB1.5.1. Is it possible >> ? >> >> easy_install -U ReviewBoard >> >> Also, from the release notes, looks like this version has a newer RBTools. >> Is this compatible with older RB versions ? >> >> When we try to upgrade using the above command, we got the below error, so >> that's the reason we want to go back to older version to see if that works. >> >> #[root@mob-rb-test /]# rb-site --debug upgrade >> >> >> /opt/lampp/htdocs/reviewboard >> Rebuilding directory structure >> >> >> Updating database. This may take a while. >> [NOTICE@1297389237.811425] mcm_storage_cmd():3334: unable to >> store value: add >> >> >> [NOTICE@1297389237.845006] mcm_storage_cmd():3334: unable to >> store value: add >> >> >> >> [NOTICE@1297389237.866137] mcm_storage_cmd():3334: unable to >> store value: add >> [NOTICE@1297389237.900860] mcm_storage_cmd():3334: unable to >> store value: add >> >> >> [NOTICE@1297389237.934480] mcm_storage_cmd():3334: unable to >> store value: add >> [NOTICE@1297389237.967112] mcm_storage_cmd():3334: unable to >> store value: add >> >> >> >> [NOTICE@1297389238.012221] mcm_storage_cmd():3334: unable to >> store value: add >> [NOTICE@1297389238.048986] mcm_storage_cmd():3334: unable to >> store value: add >> >> >> >> [NOTICE@1297389238.104145] mcm_storage_cmd():3334: unable to >> store value: add >> >> >> [NOTICE@1297389238.224780] mcm_storage_cmd():3334: unable to >> store value: add >> >> >> [NOTICE@1297389238.273282] mcm_storage_cmd():3334: unable to >> store value: add >> >> >> [NOTICE@1297389238.320729] mcm_storage_cmd():3334: unable to >> store value: add >> >>No fixtures found. >> /opt/lampp/lib/python2.5/site-packages/pycrypto-2.3-py2.5- >> linux-i686.egg/Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: >> This application uses RandomPool, which is BROKEN in older releases. See >> http://www.pycrypto.org/randpool-broken >> >> RandomPool_DeprecationWarning) >> >>No evolution required. >>Upgrade complete. >> Thanks, >> Sapna >> >> -- >> Want to help the Review Board project? Donate today at >> http://www.reviewboard.org/donate/ >> Happy user? Let us know at http://www.reviewboard.org/users/ >> -~--~~~~--~~--~--~--- >> To unsubscribe from this group, send email to >> reviewboard+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/reviewboard?hl=en > > > -- > Want to help the Review Board project? Donate today at > http://www.reviewboard.org/donate/ > Happy user? Let us know at http://www.reviewboard.org/users/ > -~--~~~~--~~--~--~--- > To unsubscribe from this group, send email to > reviewboard+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Issue Upgrading.
Hi Sapna, Going back to 1.5.1 from 1.5.3 unfortunately means removing the old version from the filesystem manually. At that point you can do: easy_install -U ReviewBoard==1.5.1 However, this won't fix the errors below. Those appear to me to be harmless. Are you hitting any real problems with the site? The mcm_storage_add errors appear to be from the old cmemcache libraries. If you can locate these on the filesystem and remove them, they should go away, as Django will fall back on the new libraries we now install along with Review Board. The current release of RBTools should be compatible with everything from 1.0.x to 1.5.3. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Fri, Feb 11, 2011 at 11:21 AM, Sapna Vempati wrote: > Hi Christian, > > Using the below command for upgrade, upgrades to the latest version (1.5.3) > by default. Is there a way we can upgrade to an older version we prefer ? > Like for example, we want to do install to RB1.5.1. Is it possible ? > > easy_install -U ReviewBoard > > Also, from the release notes, looks like this version has a newer RBTools. > Is this compatible with older RB versions ? > > When we try to upgrade using the above command, we got the below error, so > that's the reason we want to go back to older version to see if that works. > > #[root@mob-rb-test /]# rb-site --debug upgrade > > /opt/lampp/htdocs/reviewboard > Rebuilding directory structure > > Updating database. This may take a while. > [NOTICE@1297389237.811425] mcm_storage_cmd():3334: unable to > store value: add > > [NOTICE@1297389237.845006] mcm_storage_cmd():3334: unable to > store value: add > > > [NOTICE@1297389237.866137] mcm_storage_cmd():3334: unable to > store value: add > [NOTICE@1297389237.900860] mcm_storage_cmd():3334: unable to > store value: add > > [NOTICE@1297389237.934480] mcm_storage_cmd():3334: unable to > store value: add > [NOTICE@1297389237.967112] mcm_storage_cmd():3334: unable to > store value: add > > > [NOTICE@1297389238.012221] mcm_storage_cmd():3334: unable to > store value: add > [NOTICE@1297389238.048986] mcm_storage_cmd():3334: unable to > store value: add > > > [NOTICE@1297389238.104145] mcm_storage_cmd():3334: unable to > store value: add > > [NOTICE@1297389238.224780] mcm_storage_cmd():3334: unable to > store value: add > > [NOTICE@1297389238.273282] mcm_storage_cmd():3334: unable to > store value: add > > [NOTICE@1297389238.320729] mcm_storage_cmd():3334: unable to > store value: add > >No fixtures found. > /opt/lampp/lib/python2.5/site-packages/pycrypto-2.3-py2.5- > linux-i686.egg/Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: > This application uses RandomPool, which is BROKEN in older releases. See > http://www.pycrypto.org/randpool-broken > > RandomPool_DeprecationWarning) > >No evolution required. >Upgrade complete. > Thanks, > Sapna > > -- > Want to help the Review Board project? Donate today at > http://www.reviewboard.org/donate/ > Happy user? Let us know at http://www.reviewboard.org/users/ > -~--~~~~--~~--~--~--- > To unsubscribe from this group, send email to > reviewboard+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Issue Upgrading.
Hi Christian, Using the below command for upgrade, upgrades to the latest version (1.5.3) by default. Is there a way we can upgrade to an older version we prefer ? Like for example, we want to do install to RB1.5.1. Is it possible ? easy_install -U ReviewBoard Also, from the release notes, looks like this version has a newer RBTools. Is this compatible with older RB versions ? When we try to upgrade using the above command, we got the below error, so that's the reason we want to go back to older version to see if that works. #[root@mob-rb-test /]# rb-site --debug upgrade /opt/lampp/htdocs/reviewboard Rebuilding directory structure Updating database. This may take a while. [NOTICE@1297389237.811425] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389237.845006] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389237.866137] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389237.900860] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389237.934480] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389237.967112] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.012221] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.048986] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.104145] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.224780] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.273282] mcm_storage_cmd():3334: unable to store value: add [NOTICE@1297389238.320729] mcm_storage_cmd():3334: unable to store value: add No fixtures found. /opt/lampp/lib/python2.5/site-packages/pycrypto-2.3-py2.5- linux-i686.egg/Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This application uses RandomPool, which is BROKEN in older releases. See http://www.pycrypto.org/randpool-broken RandomPool_DeprecationWarning) No evolution required. Upgrade complete. Thanks, Sapna -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
