Re: Error: Error applying evolution: (1051, "Unknown table 'auth_message'"). Occurred from upgrading from 1.6.13 to 1.7.7.1

[Christian Hammond]

Hi Michael,

Can you check what version of Django Evolution you have installed? You should try to upgrade that if it's below 0.6.9.

Christian

On May 19, 2013, at 5:47, Michael Zhu <boot2...@gmail.com> wrote:

Dear all,

# rb-site upgrade path/to/reviewboard
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.
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: (1051, "Unknown table 'auth_message'")


If I force to start server, error message is reported on some review requests. Error log is below:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/Django-1.4.5-py2.7.egg/django/core/handlers/base.py", line 111, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
  File "/usr/lib/python2.7/site-packages/ReviewBoard-1.7.7.1-py2.7.egg/reviewboard/accounts/decorators.py", line 22, in _check
    return view_func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/ReviewBoard-1.7.7.1-py2.7.egg/reviewboard/reviews/views.py", line 538, in review_detail
    objs = list(q)
  File "/usr/lib/python2.7/site-packages/Django-1.4.5-py2.7.egg/django/db/models/query.py", line 87, in __len__
    self._result_cache.extend(self._iter)
  File "/usr/lib/python2.7/site-packages/Django-1.4.5-py2.7.egg/django/db/models/query.py", line 291, in iterator
    for row in compiler.results_iter():
  File "/usr/lib/python2.7/site-packages/Django-1.4.5-py2.7.egg/django/db/models/sql/compiler.py", line 763, in results_iter
    for rows in self.execute_sql(MULTI):
  File "/usr/lib/python2.7/site-packages/Django-1.4.5-py2.7.egg/django/db/models/sql/compiler.py", line 818, in execute_sql
    cursor.execute(sql, params)
  File "/usr/lib/python2.7/site-packages/Django-1.4.5-py2.7.egg/django/db/backends/mysql/base.py", line 114, in execute
    return self.cursor.execute(query, args)
  File "/usr/lib/python2.7/site-packages/MySQLdb/cursors.py", line 174, in execute
    self.errorhandler(self, exc, value)
  File "/usr/lib/python2.7/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
    raise errorclass, errorvalue
DatabaseError: (1054, "Unknown column 'reviews_fileattachmentcomment.extra_data' in 'field list'")


Michael

--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
---
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/groups/opt_out.
 
 

[Michael Zhu]

Dear Christian,

Version of Django Evolution is 0.6.9.

Michael

[Christian Hammond]

Hi Michael,

Can you run the following for me and show me the output:

   $ rb-site manage /path/to/site list-evolutions

It sounds like it's trying to apply an evolution due to thinking your database has something (based on a previous evolution-stored signature showing you had it), but it's not actually in the database. The auth_message table is something that was in prior versions of Django, and isn't now. The evolution we had erases it. A workaround might be to manually create a dummy auth_message table in the database.

At any point, did you do anything manual with the database? Do you know what version of Django you were using with RB 1.6.13?

Also, what prior versions of Review Board do you remember using?

Christian

-- 
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org

Beanbag, Inc. - http://www.beanbaginc.com