Re: Database upgrade issues - Possible fix
;> '/usr/lib64/python2.6/lib-tk', >>>>> '/usr/lib64/python2.6/lib-old', >>>>> '/usr/lib64/python2.6/lib-dynload', >>>>> '/usr/lib64/python2.6/site-packages', >>>>> '/usr/lib64/python2.6/site-packages/gst-0.10', >>>>> '/usr/lib64/python2.6/site-packages/gtk-2.0', >>>>> '/usr/lib64/python2.6/site-packages/webkit-1.0', >>>>> '/usr/lib/python2.6/site-packages'] >>>>> >>>>> >>>>> >>>>> Maybe I should try on a fresh database. >>>>> >>>>> --Steve >>>>> >>>>> On Friday, March 1, 2013 11:26:36 AM UTC-8, Christian Hammond wrote: >>>>>> >>>>>> That's the wrong Django Evolution. Can you try downloading the one >>>>>> from that URL and just passing it directly to easy_install? >>>>>> >>>>>> Christian >>>>>> >>>>>> -- >>>>>> Christian Hammond - chi...@chipx86.com >>>>>> Review Board - http://www.reviewboard.org >>>>>> VMware, Inc. - http://www.vmware.com >>>>>> >>>>>> On Mar 1, 2013, at 11:20 AM, Steve wrote: >>>>>> >>>>>> Sorry for the long, messy output, here's what happened when I tested >>>>>> the fix. This is an attempt to upgrade a 1.5.5 database to 1.7.6. >>>>>> >>>>>> [root@crush]~/ReviewBoard# easy_install -U django_evolution -f >>>>>> http://downloads.reviewboard.org/temp/django-evolution/ >>>>>> Searching for django-evolution >>>>>> Reading http://pypi.python.org/simple/django_evolution/ >>>>>> Reading http://code.google.com/p/django-evolution/ >>>>>> Best match: django-evolution 0.6.8 >>>>>> Downloading >>>>>> http://pypi.python.org/packages/2.6/d/django_evolution/django_evolution-0.6.8-py2.6.egg#md5=7527e0ca398639c87b68969ceb1cd2d7 >>>>>> Processing django_evolution-0.6.8-py2.6.egg >>>>>> removing >>>>>> '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg' (and >>>>>> everything under it) >>>>>> creating >>>>>> /usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg >>>>>> Extracting django_evolution-0.6.8-py2.6.egg to >>>>>> /usr/lib/python2.6/site-packages >>>>>> django-evolution 0.6.8 is already the active version in >>>>>> easy-install.pth >>>>>> >>>>>> Installed >>>>>> /usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg >>>>>> Processing dependencies for django-evolution >>>>>> Finished processing dependencies for django-evolution >>>>>> Searching for -f >>>>>> Reading http://pypi.python.org/simple/-f/ >>>>>> Couldn't find index page for '-f' (maybe misspelled?) >>>>>> Scanning index of all packages (this may take a while) >>>>>> Reading http://pypi.python.org/simple/ >>>>>> C-c C-c^Cinterrupted >>>>>> >>>>>> I don't know why easy_install got confused by '-f', but I did get a >>>>>> new django_evolution, so I tried updating my broken site: >>>>>> >>>>>> [root@crush]~/ReviewBoard# cat rb-upgrade.log >>>>>> Error: Model 'reviews.FileAttachmentComment' already has a field >>>>>> named 'extra_data' >>>>>> Rebuilding directory structure >>>>>> Updating database. This may take a while. >>>>>> >>>>>> The log output below, including warnings and errors, >>>>>> can be ignored unless upgrade fails. >>>>>> >>>>>> -- -- >>>>>> Creating tables ... >>>>>> There are unapplied evolutions for auth. >>>>>> There are unapplied evolutions for accounts. >>>>>> There are unapplied evolutions for changedescs. >>>>>> There are unapplied evolutions for diffviewer. >>>>>> There are unapplied evolutions for reviews. >>>>>> There are unapplied evolutions for scmtools. >>>>>> Project
Re: Database upgrade issues - Possible fix
> -- >>>>> Christian Hammond - chi...@chipx86.com >>>>> Review Board - http://www.reviewboard.org >>>>> VMware, Inc. - http://www.vmware.com >>>>> >>>>> On Mar 1, 2013, at 11:20 AM, Steve wrote: >>>>> >>>>> Sorry for the long, messy output, here's what happened when I tested >>>>> the fix. This is an attempt to upgrade a 1.5.5 database to 1.7.6. >>>>> >>>>> [root@crush]~/ReviewBoard# easy_install -U django_evolution -f >>>>> http://downloads.reviewboard.org/temp/django-evolution/ >>>>> Searching for django-evolution >>>>> Reading http://pypi.python.org/simple/django_evolution/ >>>>> Reading http://code.google.com/p/django-evolution/ >>>>> Best match: django-evolution 0.6.8 >>>>> Downloading >>>>> http://pypi.python.org/packages/2.6/d/django_evolution/django_evolution-0.6.8-py2.6.egg#md5=7527e0ca398639c87b68969ceb1cd2d7 >>>>> Processing django_evolution-0.6.8-py2.6.egg >>>>> removing >>>>> '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg' (and >>>>> everything under it) >>>>> creating >>>>> /usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg >>>>> Extracting django_evolution-0.6.8-py2.6.egg to >>>>> /usr/lib/python2.6/site-packages >>>>> django-evolution 0.6.8 is already the active version in >>>>> easy-install.pth >>>>> >>>>> Installed >>>>> /usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg >>>>> Processing dependencies for django-evolution >>>>> Finished processing dependencies for django-evolution >>>>> Searching for -f >>>>> Reading http://pypi.python.org/simple/-f/ >>>>> Couldn't find index page for '-f' (maybe misspelled?) >>>>> Scanning index of all packages (this may take a while) >>>>> Reading http://pypi.python.org/simple/ >>>>> C-c C-c^Cinterrupted >>>>> >>>>> I don't know why easy_install got confused by '-f', but I did get a >>>>> new django_evolution, so I tried updating my broken site: >>>>> >>>>> [root@crush]~/ReviewBoard# cat rb-upgrade.log >>>>> Error: Model 'reviews.FileAttachmentComment' already has a field named >>>>> 'extra_data' >>>>> Rebuilding directory structure >>>>> Updating database. This may take a while. >>>>> >>>>> The log output below, including warnings and errors, >>>>> can be ignored unless upgrade fails. >>>>> >>>>> -- -- >>>>> Creating tables ... >>>>> There are unapplied evolutions for auth. >>>>> There are unapplied evolutions for accounts. >>>>> There are unapplied evolutions for changedescs. >>>>> There are unapplied evolutions for diffviewer. >>>>> There are unapplied evolutions for reviews. >>>>> There are unapplied evolutions for scmtools. >>>>> Project signature has changed - an evolution is required >>>>> Installing custom SQL ... >>>>> Installing indexes ... >>>>> Installed 0 object(s) from 0 fixture(s) >>>>> >>>>> Now when I log in to my site, I get this: >>>>> >>>>> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >>>>> >>>>> Request Method:GETRequest URL:https://crush/Django Version:1.4.5Exception >>>>> Type:DatabaseErrorException Value: >>>>> >>>>> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >>>>> >>>>> Exception >>>>> Location:/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py >>>>> >>>>> in defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython >>>>> Version:2.6.6Python Path: >>>>> >>>>> ['/var/www/reviewboard/conf', >>>>> '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', >>>>> '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', >>>>> '/usr/lib/python2.6/site-packages/distr
Re: Database upgrade issues - Possible fix
olution >>>> Searching for -f >>>> Reading http://pypi.python.org/simple/-f/ >>>> Couldn't find index page for '-f' (maybe misspelled?) >>>> Scanning index of all packages (this may take a while) >>>> Reading http://pypi.python.org/simple/ >>>> C-c C-c^Cinterrupted >>>> >>>> I don't know why easy_install got confused by '-f', but I did get a new >>>> django_evolution, so I tried updating my broken site: >>>> >>>> [root@crush]~/ReviewBoard# cat rb-upgrade.log >>>> Error: Model 'reviews.FileAttachmentComment' already has a field named >>>> 'extra_data' >>>> Rebuilding directory structure >>>> Updating database. This may take a while. >>>> >>>> The log output below, including warnings and errors, >>>> can be ignored unless upgrade fails. >>>> >>>> -- -- >>>> Creating tables ... >>>> There are unapplied evolutions for auth. >>>> There are unapplied evolutions for accounts. >>>> There are unapplied evolutions for changedescs. >>>> There are unapplied evolutions for diffviewer. >>>> There are unapplied evolutions for reviews. >>>> There are unapplied evolutions for scmtools. >>>> Project signature has changed - an evolution is required >>>> Installing custom SQL ... >>>> Installing indexes ... >>>> Installed 0 object(s) from 0 fixture(s) >>>> >>>> Now when I log in to my site, I get this: >>>> >>>> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >>>> >>>> Request Method:GETRequest URL:https://crush/Django Version:1.4.5Exception >>>> Type:DatabaseErrorException Value: >>>> >>>> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >>>> >>>> Exception >>>> Location:/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py >>>> >>>> in defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython >>>> Version:2.6.6Python Path: >>>> >>>> ['/var/www/reviewboard/conf', >>>> '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', >>>> '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', >>>> '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', >>>> >>>> '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', >>>> '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', >>>> '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', >>>> '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', >>>> '/usr/lib64/python26.zip', >>>> '/usr/lib64/python2.6', >>>> '/usr/lib64/python2.6/plat-linux2', >>>> '/usr/lib64/python2.6/lib-tk', >>>> '/usr/lib64/python2.6/lib-old', >>>> '/usr/lib64/python2.6/lib-dynload', >>>> '/usr/lib64/python2.6/site-
Re: Database upgrade issues - Possible fix
site: >>>> >>>> [root@crush]~/ReviewBoard# cat rb-upgrade.log >>>> Error: Model 'reviews.FileAttachmentComment' already has a field named >>>> 'extra_data' >>>> Rebuilding directory structure >>>> Updating database. This may take a while. >>>> >>>> The log output below, including warnings and errors, >>>> can be ignored unless upgrade fails. >>>> >>>> -- -- >>>> Creating tables ... >>>> There are unapplied evolutions for auth. >>>> There are unapplied evolutions for accounts. >>>> There are unapplied evolutions for changedescs. >>>> There are unapplied evolutions for diffviewer. >>>> There are unapplied evolutions for reviews. >>>> There are unapplied evolutions for scmtools. >>>> Project signature has changed - an evolution is required >>>> Installing custom SQL ... >>>> Installing indexes ... >>>> Installed 0 object(s) from 0 fixture(s) >>>> >>>> Now when I log in to my site, I get this: >>>> >>>> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >>>> Request Method:GET >>>> Request URL: https://crush/ >>>> Django Version:1.4.5 >>>> Exception Type:DatabaseError >>>> Exception Value: >>>> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >>>> Exception Location: >>>> /usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py >>>> in defaulterrorhandler, line 36 >>>> Python Executable: /usr/bin/python >>>> Python Version:2.6.6 >>>> Python Path: >>>> ['/var/www/reviewboard/conf', >>>> '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', >>>> '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', >>>> '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', >>>> >>>> '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', >>>> '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', >>>> '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', >>>> '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', >>>> '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', >>>> '/usr/lib64/python26.zip', >>>> '/usr/lib64/python2.6', >>>> '/usr/lib64/python2.6/plat-linux2', >>>> '/usr/lib64/python2.6/lib-tk', >>>> '/usr/lib64/python2.6/lib-old', >>>> '/usr/lib64/python2.6/lib-dynload', >>>> '/usr/lib64/python2.6/site-packages', >>>> '/usr/lib64/python2.6/site-packages/gst-0.10', >>>> '/usr/lib64/python2.6/site-packages/gtk-2.0', >>>> '/usr/lib64/python2.6/site-packages/webkit-1.0', >>>> '/usr/lib/python2.6/site-packages'] >>>> Server time: Fri, 1 Mar 2013 19:08:48 + >>>> >>>> >>>> I may try it again on a pristine 1.5.5 database. >>>>
Re: Database upgrade issues - Possible fix
Installed 0 object(s) from 0 fixture(s) >>> >>> Now when I log in to my site, I get this: >>> >>> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >>> >>> Request Method:GETRequest URL:https://crush/Django Version:1.4.5Exception >>> Type:DatabaseErrorException Value: >>> >>> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >>> >>> Exception >>> Location:/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py >>> >>> in defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython >>> Version:2.6.6Python Path: >>> >>> ['/var/www/reviewboard/conf', >>> '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', >>> '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', >>> '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', >>> >>> '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', >>> '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', >>> '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', >>> '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', >>> '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', >>> '/usr/lib64/python26.zip', >>> '/usr/lib64/python2.6', >>> '/usr/lib64/python2.6/plat-linux2', >>> '/usr/lib64/python2.6/lib-tk', >>> '/usr/lib64/python2.6/lib-old', >>> '/usr/lib64/python2.6/lib-dynload', >>> '/usr/lib64/python2.6/site-packages', >>> '/usr/lib64/python2.6/site-packages/gst-0.10', >>> '/usr/lib64/python2.6/site-packages/gtk-2.0', >>> '/usr/lib64/python2.6/site-packages/webkit-1.0', >>> '/usr/lib/python2.6/site-packages'] >>> >>> Server time:Fri, 1 Mar 2013 19:08:48 + >>> >>> >>> I may try it again on a pristine 1.5.5 database. >>> >>> --Steve >>> >>> On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond >>> wrote: >>>> >>>> Hi everyone, >>>> >>>> So some of you have hit database upgrade issues before when upgrading >>>> to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for >>>> some of you, but not all. >>>> >>>> I've spent a lot of time trying to figure out solutions, find the >>>> common cases, and figure out a fix. Today, I have one that should fix it >>>> for at least some of you. What I really need are volunteers to help test >>>> it. >>>> >>>> If you're having issues now, or have had issues in the past and still >>>> have a broken database dump handy, I'd appreciate your help. Heck, even if >>>> you have had no issues, and have an old database dump to test. >>>> >>>> I have a test version of Django Evolution up at >>>> http://downloads.reviewboard.org/temp/django-evolution/ >>>> >>>> This version has some new logic that tries to avoid applying database >>>> upgrades for things that are already in the databa
Re: Database upgrade issues - Possible fix
e unapplied evolutions for changedescs. >>>>> There are unapplied evolutions for diffviewer. >>>>> There are unapplied evolutions for reviews. >>>>> There are unapplied evolutions for scmtools. >>>>> Project signature has changed - an evolution is required >>>>> Installing custom SQL ... >>>>> Installing indexes ... >>>>> Installed 0 object(s) from 0 fixture(s) >>>>> >>>>> Now when I log in to my site, I get this: >>>>> >>>>> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >>>>> Request Method: GET >>>>> Request URL: https://crush/ >>>>> Django Version: 1.4.5 >>>>> Exception Type: DatabaseError >>>>> Exception Value: >>>>> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >>>>> Exception Location: >>>>> /usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py >>>>> in defaulterrorhandler, line 36 >>>>> Python Executable:/usr/bin/python >>>>> Python Version: 2.6.6 >>>>> Python Path: >>>>> ['/var/www/reviewboard/conf', >>>>> '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', >>>>> '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', >>>>> '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', >>>>> >>>>> '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', >>>>> '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', >>>>> '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', >>>>> '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', >>>>> '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', >>>>> '/usr/lib64/python26.zip', >>>>> '/usr/lib64/python2.6', >>>>> '/usr/lib64/python2.6/plat-linux2', >>>>> '/usr/lib64/python2.6/lib-tk', >>>>> '/usr/lib64/python2.6/lib-old', >>>>> '/usr/lib64/python2.6/lib-dynload', >>>>> '/usr/lib64/python2.6/site-packages', >>>>> '/usr/lib64/python2.6/site-packages/gst-0.10', >>>>> '/usr/lib64/python2.6/site-packages/gtk-2.0', >>>>> '/usr/lib64/python2.6/site-packages/webkit-1.0', >>>>> '/usr/lib/python2.6/site-packages'] >>>>> Server time: Fri, 1 Mar 2013 19:08:48 + >>>>> >>>>> >>>>> I may try it again on a pristine 1.5.5 database. >>>>> >>>>> --Steve >>>>> >>>>> On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond >>>>> wrote: >>>>>> >>>>>> Hi everyone, >>>>>> >>>>>> So some of you have hit database upgrade issues before when upgrading to >>>>>> 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for >>>>>
Re: Database upgrade issues - Possible fix
7;/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', >> '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', >> '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', >> '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', >> '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', >> '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', >> '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', >> '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', >> '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', >> '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', >> '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', >> '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', >> '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', >> '/usr/lib64/python26.zip', >> '/usr/lib64/python2.6', >> '/usr/lib64/python2.6/plat-linux2', >> '/usr/lib64/python2.6/lib-tk', >> '/usr/lib64/python2.6/lib-old', >> '/usr/lib64/python2.6/lib-dynload', >> '/usr/lib64/python2.6/site-packages', >> '/usr/lib64/python2.6/site-packages/gst-0.10', >> '/usr/lib64/python2.6/site-packages/gtk-2.0', >> '/usr/lib64/python2.6/site-packages/webkit-1.0', >> '/usr/lib/python2.6/site-packages'] >> >> Server time:Fri, 1 Mar 2013 19:08:48 + >> >> >> I may try it again on a pristine 1.5.5 database. >> >> --Steve >> >> On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond >> wrote: >>> >>> Hi everyone, >>> >>> So some of you have hit database upgrade issues before when upgrading to >>> 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for >>> some of you, but not all. >>> >>> I've spent a lot of time trying to figure out solutions, find the common >>> cases, and figure out a fix. Today, I have one that should fix it for at >>> least some of you. What I really need are volunteers to help test it. >>> >>> If you're having issues now, or have had issues in the past and still >>> have a broken database dump handy, I'd appreciate your help. Heck, even if >>> you have had no issues, and have an old database dump to test. >>> >>> I have a test version of Django Evolution up at >>> http://downloads.reviewboard.org/temp/django-evolution/ >>> >>> This version has some new logic that tries to avoid applying database >>> upgrades for things that are already in the database, which was the core >>> problem most of you hit. >>> >>> If you can give this a try, here's what I'd like you to do: >>> >>> 1) Get an installation going with your broken or pre-upgrade database. >>> >>> 2) Install django_evolution from the above URL, using: >>> >>> $ sudo easy_install -U django_evolution -f >>> http://downloads.reviewboard.org/temp/django-evolution/ >>> >>> 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) >>> >>> 4) Assuming it works, try to access the site and make sure things >>> generally work on it. >>> >>> >>> Please then reply to this post with the following information: >>> >>> 1) The complete log output. >>> >>> 2) Whether you were testing with a dump from before a past broken >>> upgrade attempt, or a dump made after that past upgrade attempt failed. >>> >>> >>> For extra credit, if you have did have a working database dump, >>> sanity-checking that you don't have any upgrade problems and that the site >>> runs would also really help me out. >>> >>> Thanks! Sooner I get some feedback, the sooner I can put this problem to >>> rest. >>> >>> - Christian >>> >>> -- >>> Christian Hammond - chi...@chipx86.com >>> Review Board - http://www.reviewboard.org >>> VMware, Inc. - http://www.vmware.com >>> >>> >> -- >> 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. >> >> >> >> >> > -- > 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. > > > > > -- 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 --- 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.
Re: Database upgrade issues - Possible fix
ges >> django-evolution 0.6.8 is already the active version in easy-install.pth >> >> Installed /usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg >> Processing dependencies for django-evolution >> Finished processing dependencies for django-evolution >> Searching for -f >> Reading http://pypi.python.org/simple/-f/ >> Couldn't find index page for '-f' (maybe misspelled?) >> Scanning index of all packages (this may take a while) >> Reading http://pypi.python.org/simple/ >> C-c C-c^Cinterrupted >> >> I don't know why easy_install got confused by '-f', but I did get a new >> django_evolution, so I tried updating my broken site: >> >> [root@crush]~/ReviewBoard# cat rb-upgrade.log >> Error: Model 'reviews.FileAttachmentComment' already has a field named >> 'extra_data' >> Rebuilding directory structure >> Updating database. This may take a while. >> >> The log output below, including warnings and errors, >> can be ignored unless upgrade fails. >> >> -- -- >> Creating tables ... >> There are unapplied evolutions for auth. >> There are unapplied evolutions for accounts. >> There are unapplied evolutions for changedescs. >> There are unapplied evolutions for diffviewer. >> There are unapplied evolutions for reviews. >> There are unapplied evolutions for scmtools. >> Project signature has changed - an evolution is required >> Installing custom SQL ... >> Installing indexes ... >> Installed 0 object(s) from 0 fixture(s) >> >> Now when I log in to my site, I get this: >> >> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >> Request Method: GET >> Request URL: https://crush/ >> Django Version: 1.4.5 >> Exception Type: DatabaseError >> Exception Value: >> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >> Exception Location: >> /usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py >> in defaulterrorhandler, line 36 >> Python Executable: /usr/bin/python >> Python Version: 2.6.6 >> Python Path: >> ['/var/www/reviewboard/conf', >> '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', >> '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', >> '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', >> >> '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', >> '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', >> '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', >> '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', >> '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', >> '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', >> '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', >> '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', >> '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', >> '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', >> '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', >> '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', >> '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', >> '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', >> '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', >> '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', >> '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', >> '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', >> '/usr/lib64/python26.zip', >> '/usr/lib64/python2.6', >> '/usr/lib64/python2.6/plat-linux2', >> '/usr/lib64/python2.6/lib-tk', >> '/usr/lib64/python2.6/lib-old', >> '/usr/lib64/python2.6/lib-dynload', >> '/usr/lib64/python2.6/site-packages', >> '/usr/lib64/python2.6/site-packages/gst-0.10', >> '/usr/lib64/python2.6/site-packages/gtk-2.0', >> '/usr/lib64/python2.6/site-packages/webkit-1.0', >> '/usr/lib/python2.6/site-packages'] >> Server ti
Re: Database upgrade issues - Possible fix
>> '/usr/lib/python2.6/site-**packages/django_evolution-0.6.**8-py2.6.egg' >> (and everything under it) >> creating /usr/lib/python2.6/site-**packages/django_evolution-0.6.** >> 8-py2.6.egg >> Extracting django_evolution-0.6.8-py2.6.**egg to /usr/lib/python2.6/site- >> **packages >> django-evolution 0.6.8 is already the active version in easy-install.pth >> >> Installed /usr/lib/python2.6/site-**packages/django_evolution-0.6.** >> 8-py2.6.egg >> Processing dependencies for django-evolution >> Finished processing dependencies for django-evolution >> Searching for -f >> Reading >> http://pypi.python.org/simple/**-f/<http://pypi.python.org/simple/-f/> >> Couldn't find index page for '-f' (maybe misspelled?) >> Scanning index of all packages (this may take a while) >> Reading http://pypi.python.org/simple/ >> C-c C-c^Cinterrupted >> >> I don't know why easy_install got confused by '-f', but I did get a new >> django_evolution, so I tried updating my broken site: >> >> [root@crush]~/ReviewBoard# cat rb-upgrade.log >> Error: Model 'reviews.**FileAttachmentComment' already has a field named >> 'extra_data' >> Rebuilding directory structure >> Updating database. This may take a while. >> >> The log output below, including warnings and errors, >> can be ignored unless upgrade fails. >> >> -- -- >> Creating tables ... >> There are unapplied evolutions for auth. >> There are unapplied evolutions for accounts. >> There are unapplied evolutions for changedescs. >> There are unapplied evolutions for diffviewer. >> There are unapplied evolutions for reviews. >> There are unapplied evolutions for scmtools. >> Project signature has changed - an evolution is required >> Installing custom SQL ... >> Installing indexes ... >> Installed 0 object(s) from 0 fixture(s) >> >> Now when I log in to my site, I get this: >> >> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >> >> Request Method:GETRequest URL:https://crush/Django Version:1.4.5Exception >> Type:DatabaseErrorException Value: >> >> (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") >> >> Exception Location:/usr/lib/python2.6/site-**packages/MySQL_python-1.2.3- >> **py2.6-linux-x86_64.egg/**MySQLdb/connections.py in >> defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython >> Version:2.6.6Python Path: >> >> ['/var/www/reviewboard/conf', >> '/usr/lib64/python2.6/site-**packages/JCC-2.14-py2.6-linux-**x86_64.egg', >> >> '/usr/lib64/python2.6/site-**packages/lucene-3.6.1-py2.6-**linux-x86_64.egg', >> '/usr/lib/python2.6/site-**packages/distribute-0.6.27-**py2.6.egg', >> >> '/usr/lib/python2.6/site-**packages/MySQL_python-1.2.3-**py2.6-linux-x86_64.egg', >> '/usr/lib/python2.6/site-**packages/recaptcha_client-1.0.**6-py2.6.egg', >> '/usr/lib/python2.6/site-**packages/python_dateutil-1.5-**py2.6.egg', >> '/usr/lib/python2.6/site-**packages/flup-1.0.3.dev_**20110405-py2.6.egg', >> '/usr/lib/python2.6/site-**packages/Pygments-1.5-py2.6.**egg', >> '/usr/lib/python2.6/site-**packages/PIL-1.1.7-py2.6-**linux-x86_64.egg', >> '/usr/lib/python2.6/site-**packages/pycrypto-2.6-py2.6-**linux-x86_64.egg', >> '/usr/lib/python2.6/site-**packages/feedparser-5.1.3-py2.**6.egg', >> '/usr/lib/python2.6/site-**packages/ReviewBoard-1.7.6-**py2.6.egg', >> '/usr/lib/python2.6/site-**packages/pytz-2012j-py2.6.egg'**, >> '/usr/lib/python2.6/site-**packages/paramiko-1.9.0-py2.6.**egg', >> '/usr/lib/python2.6/site-**packages/mimeparse-0.1.3-py2.**6.egg', >> '/usr/lib/python2.6/site-**packages/Markdown-2.2.1-py2.6.**egg', >> '/usr/lib/python2.6/site-**packages/docutils-0.10-py2.6.**egg', >> '/usr/lib/python2.6/site-**packages/django_pipeline-1.2.**24-py2.6.egg', >> '/usr/lib/python2.6/site-**packages/Djblets-0.7.11-py2.6.**egg', >> '/usr/lib/python2.6/site-**packages/Django-1.4.5-py2.6.**egg', >> '/usr/lib/python2.6/site-**packages/django_evolution-0.6.**8-py2.6.egg', >> '/usr/lib64/python26.zip', >> '/usr/lib64/python2.6', >> '/usr/lib64/python2.6/plat-**linux2', >> '/usr/lib64/python2.6/lib-tk', >&g
Re: Database upgrade issues - Possible fix
b-upgrade.log > Error: Model 'reviews.FileAttachmentComment' already has a field named > 'extra_data' > Rebuilding directory structure > Updating database. This may take a while. > > The log output below, including warnings and errors, > can be ignored unless upgrade fails. > > -- -- > Creating tables ... > There are unapplied evolutions for auth. > There are unapplied evolutions for accounts. > There are unapplied evolutions for changedescs. > There are unapplied evolutions for diffviewer. > There are unapplied evolutions for reviews. > There are unapplied evolutions for scmtools. > Project signature has changed - an evolution is required > Installing custom SQL ... > Installing indexes ... > Installed 0 object(s) from 0 fixture(s) > > Now when I log in to my site, I get this: > > (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") > > Request Method:GETRequest URL:https://crush/Django Version:1.4.5Exception > Type:DatabaseErrorException Value: > > (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") > > Exception > Location:/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py > > in defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython > Version:2.6.6Python Path: > > ['/var/www/reviewboard/conf', > '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', > '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', > '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', > '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', > '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', > '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', > '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', > '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', > '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', > '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', > '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', > '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', > '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', > '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', > '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', > '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', > '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', > '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', > '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', > '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', > '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', > '/usr/lib64/python26.zip', > '/usr/lib64/python2.6', > '/usr/lib64/python2.6/plat-linux2', > '/usr/lib64/python2.6/lib-tk', > '/usr/lib64/python2.6/lib-old', > '/usr/lib64/python2.6/lib-dynload', > '/usr/lib64/python2.6/site-packages', > '/usr/lib64/python2.6/site-packages/gst-0.10', > '/usr/lib64/python2.6/site-packages/gtk-2.0', > '/usr/lib64/python2.6/site-packages/webkit-1.0', > '/usr/lib/python2.6/site-packages'] > > Server time:Fri, 1 Mar 2013 19:08:48 + > > > I may try it again on a pristine 1.5.5 database. > > --Steve > > On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: >> >> Hi everyone, >> >> So some of you have hit database upgrade issues before when upgrading to >> 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for >> some of you, but not all. >> >> I've spent a lot of time trying to figure out solutions, find the common >> cases, and figure out a fix. Today, I have one that should fix it for at >> least some of you. What I really need are volunteers to help test it. >> >> If you're having issues now, or have had issues in the past and still >> have a broken database dump handy, I'd appreciate your help. Heck, even if >> you have had no issues, and have an old database dump to test. >> >> I have a test version of Django Evolution up at >> http://downloads.reviewboard.org/temp/django-evolution/ >> >> This version has some new
Re: Database upgrade issues - Possible fix
e-packages/docutils-0.10-py2.6.egg', > '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', > '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', > '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', > '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', > '/usr/lib64/python26.zip', > '/usr/lib64/python2.6', > '/usr/lib64/python2.6/plat-linux2', > '/usr/lib64/python2.6/lib-tk', > '/usr/lib64/python2.6/lib-old', > '/usr/lib64/python2.6/lib-dynload', > '/usr/lib64/python2.6/site-packages', > '/usr/lib64/python2.6/site-packages/gst-0.10', > '/usr/lib64/python2.6/site-packages/gtk-2.0', > '/usr/lib64/python2.6/site-packages/webkit-1.0', > '/usr/lib/python2.6/site-packages'] > Server time: Fri, 1 Mar 2013 19:08:48 + > > > I may try it again on a pristine 1.5.5 database. > > --Steve > > On Wednesday, February 27, 2013 12:16:03 AM UTC-8, Christian Hammond wrote: > Hi everyone, > > So some of you have hit database upgrade issues before when upgrading to 1.7 > (or, in some cases, 1.6). We've managed to figure out solutions for some of > you, but not all. > > I've spent a lot of time trying to figure out solutions, find the common > cases, and figure out a fix. Today, I have one that should fix it for at > least some of you. What I really need are volunteers to help test it. > > If you're having issues now, or have had issues in the past and still have a > broken database dump handy, I'd appreciate your help. Heck, even if you have > had no issues, and have an old database dump to test. > > I have a test version of Django Evolution up at > http://downloads.reviewboard.org/temp/django-evolution/ > > This version has some new logic that tries to avoid applying database > upgrades for things that are already in the database, which was the core > problem most of you hit. > > If you can give this a try, here's what I'd like you to do: > > 1) Get an installation going with your broken or pre-upgrade database. > > 2) Install django_evolution from the above URL, using: > > $ sudo easy_install -U django_evolution -f > http://downloads.reviewboard.org/temp/django-evolution/ > > 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) > > 4) Assuming it works, try to access the site and make sure things generally > work on it. > > > Please then reply to this post with the following information: > > 1) The complete log output. > > 2) Whether you were testing with a dump from before a past broken upgrade > attempt, or a dump made after that past upgrade attempt failed. > > > For extra credit, if you have did have a working database dump, > sanity-checking that you don't have any upgrade problems and that the site > runs would also really help me out. > > Thanks! Sooner I get some feedback, the sooner I can put this problem to rest. > > - Christian > > -- > Christian Hammond - chi...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > > -- > 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 > --- > 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. > > -- 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 --- 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.
Re: Database upgrade issues - Possible fix
Sorry for the long, messy output, here's what happened when I tested the fix. This is an attempt to upgrade a 1.5.5 database to 1.7.6. [root@crush]~/ReviewBoard# easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ Searching for django-evolution Reading http://pypi.python.org/simple/django_evolution/ Reading http://code.google.com/p/django-evolution/ Best match: django-evolution 0.6.8 Downloading http://pypi.python.org/packages/2.6/d/django_evolution/django_evolution-0.6.8-py2.6.egg#md5=7527e0ca398639c87b68969ceb1cd2d7 Processing django_evolution-0.6.8-py2.6.egg removing '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg' (and everything under it) creating /usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg Extracting django_evolution-0.6.8-py2.6.egg to /usr/lib/python2.6/site-packages django-evolution 0.6.8 is already the active version in easy-install.pth Installed /usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg Processing dependencies for django-evolution Finished processing dependencies for django-evolution Searching for -f Reading http://pypi.python.org/simple/-f/ Couldn't find index page for '-f' (maybe misspelled?) Scanning index of all packages (this may take a while) Reading http://pypi.python.org/simple/ C-c C-c^Cinterrupted I don't know why easy_install got confused by '-f', but I did get a new django_evolution, so I tried updating my broken site: [root@crush]~/ReviewBoard# cat rb-upgrade.log Error: Model 'reviews.FileAttachmentComment' already has a field named 'extra_data' Rebuilding directory structure Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- -- Creating tables ... There are unapplied evolutions for auth. There are unapplied evolutions for accounts. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Now when I log in to my site, I get this: (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") Request Method:GETRequest URL:https://crush/Django Version:1.4.5Exception Type:DatabaseErrorException Value: (1054, "Unknown column 'accounts_profile.is_private' in 'field list'") Exception Location:/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg/MySQLdb/connections.py in defaulterrorhandler, line 36Python Executable:/usr/bin/pythonPython Version:2.6.6Python Path: ['/var/www/reviewboard/conf', '/usr/lib64/python2.6/site-packages/JCC-2.14-py2.6-linux-x86_64.egg', '/usr/lib64/python2.6/site-packages/lucene-3.6.1-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/distribute-0.6.27-py2.6.egg', '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.6-py2.6.egg', '/usr/lib/python2.6/site-packages/pytz-2012j-py2.6.egg', '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', '/usr/lib/python2.6/site-packages/django_pipeline-1.2.24-py2.6.egg', '/usr/lib/python2.6/site-packages/Djblets-0.7.11-py2.6.egg', '/usr/lib/python2.6/site-packages/Django-1.4.5-py2.6.egg', '/usr/lib/python2.6/site-packages/django_evolution-0.6.8-py2.6.egg', '/usr/lib64/python26.zip', '/usr/lib64/python2.6', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib64/python2.6/site-packages', '/usr/lib64/python2.6/site-packages/gst-0.10', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib64/python2.6/site-packag
Re: Database upgrade issues - Possible fix
Hi Christian, I was able to upgrade now successfully! *I have tried migrating an old database(1.0) into the latest RB Server*, please find below the result of the tests. Cheers! Nachiketh *OUTPUT:* *root@nachiketh-virtual-machine:~#* easy_install -f http://downloads.reviewboard.org/temp/django-evolution/ -U django_evolution Searching for django-evolution Reading http://downloads.reviewboard.org/temp/django-evolution/ Reading http://pypi.python.org/simple/django_evolution/ Reading http://code.google.com/p/django-evolution/ Best match: django-evolution 0.6.9alpha0.dev Downloading http://downloads.reviewboard.org/temp/django-evolution/django_evolution-0.6.9alpha0.dev-py2.7.egg Processing django_evolution-0.6.9alpha0.dev-py2.7.egg creating /usr/local/lib/python2.7/dist-packages/django_evolution-0.6.9alpha0.dev-py2.7.egg Extracting django_evolution-0.6.9alpha0.dev-py2.7.egg to /usr/local/lib/python2.7/dist-packages Removing django-evolution 0.6.8 from easy-install.pth file Adding django-evolution 0.6.9alpha0.dev to easy-install.pth file Installed /usr/local/lib/python2.7/dist-packages/django_evolution-0.6.9alpha0.dev-py2.7.egg Processing dependencies for django-evolution Finished processing dependencies for django-evolution *root@nachiketh-virtual-machine:~#* rb-site upgrade /var/www/csm Rebuilding directory structure Updating database. This may take a while. The log output below, including warnings and errors, can be ignored unless upgrade fails. -- -- Creating tables ... Creating table extensions_registeredextension Creating table accounts_localsiteprofile Creating table attachments_fileattachment Creating table diffviewer_filediffdata Creating table hostingsvcs_hostingserviceaccount Creating table reviews_fileattachmentcomment Creating table site_localsite_users Creating table site_localsite_admins Creating table site_localsite There are unapplied evolutions for auth. There are unapplied evolutions for sessions. There are unapplied evolutions for accounts. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. 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) Registering new SCM Tool Plastic SCM (reviewboard.scmtools.plastic.PlasticTool) in database Registering new SCM Tool ClearCase (reviewboard.scmtools.clearcase.ClearCaseTool) in database Evolution could not be simulated, possibly due to raw SQL mutations Evolution successful. --- --- Resetting in-database caches. *Upgrade complete!* *root@nachiketh-virtual-machine:~# * On Wednesday, 27 February 2013 13:46:03 UTC+5:30, Christian Hammond wrote: > > Hi everyone, > > So some of you have hit database upgrade issues before when upgrading to > 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for > some of you, but not all. > > I've spent a lot of time trying to figure out solutions, find the common > cases, and figure out a fix. Today, I have one that should fix it for at > least some of you. What I really need are volunteers to help test it. > > If you're having issues now, or have had issues in the past and still have > a broken database dump handy, I'd appreciate your help. Heck, even if you > have had no issues, and have an old database dump to test. > > I have a test version of Django Evolution up at > http://downloads.reviewboard.org/temp/django-evolution/ > > This version has some new logic that tries to avoid applying database > upgrades for things that are already in the database, which was the core > problem most of you hit. > > If you can give this a try, here's what I'd like you to do: > > 1) Get an installation going with your broken or pre-upgrade database. > > 2) Install django_evolution from the above URL, using: > > $ sudo easy_install -U django_evolution -f > http://downloads.reviewboard.org/temp/django-evolution/ > > 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) > > 4) Assuming it works, try to access the site and make sure things > generally work on it. > > > Please then reply to this post with the following information: > > 1) The complete log output. > > 2) Whether you were testing with a dump from before a past broken upgrade > attempt, or a dump made after that past upgrade attempt failed. > > > For extra credit, if you have did have a working database dump, > sanity-checking that you don't have any upgrade problems and that the site > runs would also really help me out. > > Thanks! Sooner I get some feedback, the sooner I can put this problem to >
Database upgrade issues - Possible fix
Hi everyone, So some of you have hit database upgrade issues before when upgrading to 1.7 (or, in some cases, 1.6). We've managed to figure out solutions for some of you, but not all. I've spent a lot of time trying to figure out solutions, find the common cases, and figure out a fix. Today, I have one that should fix it for at least some of you. What I really need are volunteers to help test it. If you're having issues now, or have had issues in the past and still have a broken database dump handy, I'd appreciate your help. Heck, even if you have had no issues, and have an old database dump to test. I have a test version of Django Evolution up at http://downloads.reviewboard.org/temp/django-evolution/ This version has some new logic that tries to avoid applying database upgrades for things that are already in the database, which was the core problem most of you hit. If you can give this a try, here's what I'd like you to do: 1) Get an installation going with your broken or pre-upgrade database. 2) Install django_evolution from the above URL, using: $ sudo easy_install -U django_evolution -f http://downloads.reviewboard.org/temp/django-evolution/ 3) Attempt a Review Board upgrade (rb-site manage /path/to/site upgrade) 4) Assuming it works, try to access the site and make sure things generally work on it. Please then reply to this post with the following information: 1) The complete log output. 2) Whether you were testing with a dump from before a past broken upgrade attempt, or a dump made after that past upgrade attempt failed. For extra credit, if you have did have a working database dump, sanity-checking that you don't have any upgrade problems and that the site runs would also really help me out. Thanks! Sooner I get some feedback, the sooner I can put this problem to rest. - Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com -- 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 --- 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.
Re: Database upgrade issues
Upon further testing, it seems something has changed with this release and LDAP authentication. I was able to log into RB with a local user, however all LDAP users can not log in. Do you know what has changed with the LDAP backend authentication? The RB log shows the following message 2012-12-28 06:30:38,031 - WARNING - LDAP error: The specified object does not exist in the Directory or provided invalid credentials: (emailAddress=) -- 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: Database upgrade issues
Hi Christian, Here is what the output for the version Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53) [GCC 4.5.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from django_evolution.models import Version >>> print Version.objects.all() [, , , ] >>> I was able to successfully execute the commands in step 2 and now have a working 1.7.1 RB! A quick test does not show any issues as of yet, however I will keep an eye out for any. Thank you for your time and assistance on resolving this issue! -- 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
Database upgrade issues
Hi guys, I wanted to condense the three active threads on database upgrade issues. The things you all have in common is that you're upgrading from older versions using an older Django Evolution that all had a bug causing blank hinted schema evolutions, which could cause problems when upgrading. So for each of you still having the hinted evolution problem, can you do the following: 1) Do a full SQL backup of your database 2) Run: $ rb-site manage /path/to/site shell >>> from django_evolution.models import Version >>> print Version.objects.all() Paste that for me. Now, here's where your backup comes in. Do this: $ rb-site manage /path/to/site shell >>> from django_evolution.models import Version >>> Version.objects.exclude(evolutions__pk__gt=0).delete() Then re-do the rb-site upgrade, reload the web server, and see if that works better. Test the site, make sure you don't have any database errors, and report back. I'm hoping this fixes the problem for you. If so, I can integrate this into the upgrade process for future upgrades. (Not that you should ever hit this again, since it's fixed in django-evolution.) Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com -- 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
