Re: Help, upgrading to 2.0.7 broke my server!

2014-10-15 Thread Erik Lattimore
I ran into the issue as well. Upgraded from 2.0.6 to 2.0.8 with postgres (seems to be the common theme). The steps listed by Christian Wuerdig resolved things. On Thursday, September 25, 2014 4:10:07 PM UTC-4, Christian Wuerdig wrote: I just ran into the same problem upgrading from 2.0.6 to

Re: Help, upgrading to 2.0.7 broke my server!

2014-10-15 Thread Christian Hammond
Do you have a dump of the database pre-upgrade? I need someone to provide this in order to fix the problem for good. Christian On Wednesday, October 15, 2014, Erik Lattimore erik.l...@gmail.com wrote: I ran into the issue as well. Upgraded from 2.0.6 to 2.0.8 with postgres (seems to be the

Re: Help, upgrading to 2.0.7 broke my server!

2014-09-25 Thread Christian Wuerdig
I just ran into the same problem upgrading from 2.0.6 to 2.0.8. Running postgres as well In prostgres dropping the index is achieved by: DROP index scmtools_repository_8c446842; running rb-site upgrade again after that completed successfully On Tuesday, 16 September 2014 13:44:48 UTC+12,

Re: Help, upgrading to 2.0.7 broke my server!

2014-09-25 Thread Christian Hammond
Hi Christian, Any chance you have a database backup from before the upgrade? I'd like to figure out why this is breaking in django-evolution. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On

Help, upgrading to 2.0.7 broke my server!

2014-09-15 Thread Ian
I did the easy_install -U thing to update Review Board, and then the rb-side upgrade thing to upgrade my site. I get this output though, and now I can't view anything in Review Board. Any workarounds much appreciated! $ sudo rb-site upgrade /Library/Server/Web/Data/WebApps/ReviewBoard

Re: Help, upgrading to 2.0.7 broke my server!

2014-09-15 Thread Christian Hammond
What version did you upgrade from? That looks like it may be a duplicate index. Can you run:     rb-site manage /path/to/site evolve -- --sql And show me what that says? Also, are you using MySQL? Christian -- Christian Hammond - christ...@beanbaginc.com Review Board -

Re: Help, upgrading to 2.0.7 broke my server!

2014-09-15 Thread Christian Hammond
Assuming MySQL, try connecting to the database using the mysql command line client and running this:     show indexes from scmtools_repository; It will likely have scmtools_repository_8c446842 in the list. Try doing:     alter table scmtools_repository drop index scmtools_repository_8c446842;

Re: Help, upgrading to 2.0.7 broke my server!

2014-09-15 Thread Ian
Upgraded from 2.0.6 and using PostgreSQL. $ sudo rb-site manage /Library/Server/Web/Data/WebApps/ReviewBoard evolve -- --sql Password: -- Evolve application scmtools ALTER TABLE scmtools_repository ADD COLUMN hooks_uuid varchar(32) NULL; CREATE UNIQUE INDEX scmtools_repository_8c446842 ON

Re: Help, upgrading to 2.0.7 broke my server!

2014-09-15 Thread Christian Hammond
Hmmm, it should have tried to drop the old index in that upgrade. Very odd. What version were you running before this? (I have to take off for a couple hours, but will be back.. hopefully the other instructions will have helped.) Christian -- Christian Hammond - christ...@beanbaginc.com

Re: Help, upgrading to 2.0.7 broke my server!

2014-09-15 Thread Ian
I was running 2.0.6. I'll try to figure out the PostgreSQL equivalent to drop the index and try again. Ian On Monday, September 15, 2014 6:44:48 PM UTC-7, Christian Hammond wrote: Hmmm, it should have tried to drop the old index in that upgrade. Very odd. What version were you running

Re: Help, upgrading to 2.0.7 broke my server!

2014-09-15 Thread Ian
Phew, that worked, thanks! Ian On Monday, September 15, 2014 6:45:50 PM UTC-7, Ian wrote: I was running 2.0.6. I'll try to figure out the PostgreSQL equivalent to drop the index and try again. Ian On Monday, September 15, 2014 6:44:48 PM UTC-7, Christian Hammond wrote: Hmmm, it should