OK, I got the final piece of puzzle resolved. Put my solutions here for
next poor guy in the future. Note, what worked for me doesn't necessary
mean it will work for you. Take snapshot of your DB before doing it!!
Go back to my last error in last reply. It was complaining one DB was
crashed, and in fact when I click on "view diff" on the RB UI, I see a
stacktrace like:
.....
DatabaseError at /r/513130/diff/
(1054, "Unknown column 'diffviewer_diffsethistory.last_diff_updated' in 'field
list'")
....
so I decided to add that column myself according to the output from --hint.
I then ran django's syncdb command (yes, not via RB's rbsite.sh wrapper).
$ sudo manage.sh syncdb
Creating tables ...
There are unapplied evolutions for auth.
The following content types are stale and need to be deleted:
auth | message
Any objects related to these content types by a foreign key will also
be deleted. Are you sure you want to delete these content types?
If you're unsure, answer 'no'.
Type 'yes' to continue, or 'no' to cancel: yes
There are unapplied evolutions for accounts.
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for reviews.
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
Finally, I ran rbsite.sh again. It worked.
On Friday, November 8, 2013 11:15:41 PM UTC-8, humble wrote:
>
> I installed evolution 0.6.7. I have all packages up to date for this
> version of RB (I have upgraded many times before and I usually examine
> setup.cfg to find what packages to include and which version of them)
>
> I did ran rb-site mange /path/to/site evolve --hint to get list of DB
> upgrades, then I passed, as suggested by the output, --execute, however,
> that crashed my DB after a very long time.
>
> So I reverted DB to its previous snapshot. This time around, I did
> manually add the DB changes based on --hint output like:
>
> alter table accounts_profile add open_an_issue bool default
> true;
> alter table accounts_profile add timezone varchar(20) default
> 'UTC';
> alter table diffviewer_diffsethistory add last_diff_updated
> DATETIME;
> alter table reviews_fileattachmentcomment add extra_data varchar(256)
> default "";
>
> After these changes, I was able to browse the admin UI which enabled me to
> delete the "hinted version", then I dropped the columns I added above. I
> ran "rbsite upgrade" again, much better output this time but still has an
> error:
>
> Rebuilding directory structure
> Updating database. This may take a while.
>
> The log output below, including warnings and errors,
> can be ignored unless upgrade fails.
>
> ------------------ <begin log output> ------------------
> Creating tables ...
> There are unapplied evolutions for auth.
> There are unapplied evolutions for accounts.
> There are unapplied evolutions for diffviewer.
> There are unapplied evolutions for reviews.
> 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)
>
> Error: Error applying evolution: (1194, "Table 'diffviewer_diffsethistory'
> is marked as cr
> ashed and should be repaired")
>
> This is what I got so far, I'm still working on it .... I guess the worst
> case is I upgrade all version > 1.6.13 all the way up to 1.7.6 so that the
> schema changes etc are incremental and small.
>
> On Friday, November 8, 2013 5:04:30 PM UTC-8, Christian Hammond wrote:
>>
>> Can you let me know what version of django-evolution you have installed?
>>
>> Also, run these commands and show the output:
>>
>> rb-site manage /path/to/site evolve -- --hint
>> rb-site manage /path/to/site list-evolutions
>>
>> Christian
>>
>>
>> On Friday, November 8, 2013, humble wrote:
>>
>>> For the record, I'm having exactly the same problem and seeing exactly
>>> the same error.
>>>
>>> On Thursday, December 27, 2012 5:24:21 PM UTC-8, Christian Hammond wrote:
>>>>
>>>> Can you also let me know if you've upgraded Python on this machine for
>>>> 1.7, or if you're still using the same version you were using with Review
>>>> Board 1.6.13.
>>>>
>>>> Christian
>>>>
>>>> --
>>>> Christian Hammond - chi...@chipx86.com
>>>> Review Board - http://www.reviewboard.org
>>>> VMware, Inc. - http://www.vmware.com
>>>>
>>>>
>>>> On Thu, Dec 27, 2012 at 5:17 PM, Christian Hammond
>>>> <chi...@chipx86.com>wrote:
>>>>
>>>>> Did you ever attempt an upgrade before and then downgrade?
>>>>>
>>>>> I'm noticing two things in your dump:
>>>>>
>>>>> 1) Some of these things it's complaining about are already applied
>>>>> evolutions, so you shouldn't see it again.
>>>>> 2) Some of them are things that existed in 1.6.13 (the repository
>>>>> fields in particular were already there).
>>>>>
>>>>> Christian
>>>>>
>>>>> --
>>>>> Christian Hammond - chi...@chipx86.com
>>>>>
>>>>> Review Board - http://www.reviewboard.org
>>>>> VMware, Inc. - http://www.vmware.com
>>>>>
>>>>>
>>>>> On Thu, Dec 27, 2012 at 2:25 PM, jacob.j.rosales <jacob.j...@gmail.com
>>>>> > wrote:
>>>>>
>>>>> Same issue when accessing <url>/admin/
>>>>>
>>>>> 2012-12-27 14:18:54,190 - ERROR - Internal Server Error: /admin/
>>>>>
>>>>> Traceback (most recent call last):
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-
>>>>> py2.7.egg/django/core/handlers/base.py", line 89, in get_response
>>>>> response = middleware_method(request)
>>>>> File "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.
>>>>> 1-py2.7.egg/reviewboard/accounts/middleware.py", line 12, in
>>>>> process_request
>>>>> user = Profile.objects.get(user=request.user)
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-
>>>>> py2.7.egg/django/db/models/manager.py", line 131, in get
>>>>> return self.get_query_set().get(*args, **kwargs)
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-
>>>>> py2.7.egg/django/db/models/query.py", line 361, in get
>>>>> num = len(clone)
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-
>>>>> py2.7.egg/django/db/models/query.py", line 85, in __len__
>>>>> self._result_cache = list(self.iterator())
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-
>>>>> py2.7.egg/django/db/models/query.py", line 291, in iterator
>>>>> for row in compiler.results_iter():
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-
>>>>> py2.7.egg/django/db/models/sql/compiler.py", line 763, in results_iter
>>>>> for rows in self.execute_sql(MULTI):
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-
>>>>> py2.7.egg/django/db/models/sql/compiler.py", line 818, in execute_sql
>>>>> cursor.execute(sql, params)
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-
>>>>> py2.7.egg/django/db/backends/mysql/base.py", line 114, in execute
>>>>> return self.cursor.execute(query, args)
>>>>> File "/usr/lib/pymodules/python2.7/MySQLdb/cursors.py", line 166,
>>>>> in execute
>>>>> self.errorhandler(self, exc, value)
>>>>> File "/usr/lib/pymodules/python2.7/MySQLdb/connections.py", line
>>>>> 35, in defaulterrorhandler
>>>>> raise errorclass, errorvalue
>>>>> DatabaseError: (1054, "Unknown column 'accounts_profile.open_an_issue'
>>>>> in 'field list'")
>>>>>
>>>>>
>>>>> On Thursday, December 27, 2012 4:19:15 PM UTC-6, Christian Hammond
>>>>> wrote:
>>>>>
>>>>> The dashboard is inaccessible, but I'd expect you could reach /admin/
>>>>> directly.
>>>>>
>>>>> Christian
>>>>>
>>>>>
>>>>> On Dec 27, 2012, at 13:59, "jacob.j.rosales" <jacob.j...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> It looks like due to the failed upgrade I am unable to access any
>>>>> pages outside the login page
>>>>>
>>>>> 2012-12-27 13:48:48,658 - ERROR - Internal Server Error: /dashboard/
>>>>> Traceback (most recent call last):
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.
>>>>> egg/django/core/handlers/base.py", line 89, in get_response
>>>>> response = middleware_method(request)
>>>>> File "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-
>>>>> py2.7.egg/reviewboard/accounts/middleware.py", line 12, in
>>>>> process_request
>>>>> user = Profile.objects.get(user=request.user)
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.
>>>>> egg/django/db/models/manager.py", line 131, in get
>>>>> return self.get_query_set().get(*args, **kwargs)
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.
>>>>> egg/django/db/models/query.py", line 361, in get
>>>>> num = len(clone)
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.
>>>>> egg/django/db/models/query.py", line 85, in __len__
>>>>> self._result_cache = list(self.iterator())
>>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.
>>>>> egg/django/db
>>>>>
>>>>>
>>>> --
>>> 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/groups/opt_out.
>>>
>>
>>
>> --
>> --
>> Christian Hammond - chi...@chipx86.com
>> Review Board - http://www.reviewboard.org
>> Beanbag, Inc. - http://www.beanbaginc.com
>>
>>
--
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/groups/opt_out.
