I'm trying to setup a new ReviewBoard 1.6 instance and running into
some problems.  I have Python 2.7 installed, on CentOS 5.4, by way of
Python's altinstall method.  Here are the steps I'm executing.


sudo easy_install-2.7 -U ReviewBoard
# This complains about not knowing how to handle https: for getting Django.-

wget https://www.djangoproject.com/m/releases/1.3/Django-1.3.3.tar.gz
# extract, build, install goes fine

sudo easy_install-2.7 -U ReviewBoard
# Success!

$ sudo rb-site install --domain-name='reviews.sre.company.com'
--site-root='/' --media-url='media/' --db-type='mysql'
--db-name='reviewboard' --db-host='localhost' --db-user='reviewboard'
--db-pass='password' --cache-type='memcached'
--web-server-type='apache' --python-loader='wsgi' --admin-user='admin'
--admin-password='password' --admin-email='j...@company.com'
/var/www/sites/reviews.sre.company.com/
# This all works fine and I get the installed message.

$ sudo chown -R apache
/var/www/sites/reviews.sre.company.com/htdocs/media/uploaded
$ sudo chown -R apache /var/www/sites/reviews.sre.company.com/data

Copy config from conf/ dir into /etc/httpd/conf.d/ dir.  Restart
apache and memcached.  The site comes up fine but then I try import
the dump from my old site.  The old site is 1.6 and the new site is
running 1.6.13.  ReviewBoard tells me I need to upgrade.  When I run
the upgrade, this is what I get:

"""
Rebuilding directory structure
Updating database. This may take a while.
Creating tables ...
Creating table hostingsvcs_hostingserviceaccount
Traceback (most recent call last):
  File "/usr/bin/rb-site", line 8, in <module>
    load_entry_point('ReviewBoard==1.6.13', 'console_scripts', 'rb-site')()
  File 
"/usr/lib/python2.7/site-packages/ReviewBoard-1.6.13-py2.7.egg/reviewboard/cmdline/rbsite.py",
line 1745, in main
    command.run()
  File 
"/usr/lib/python2.7/site-packages/ReviewBoard-1.6.13-py2.7.egg/reviewboard/cmdline/rbsite.py",
line 1642, in run
    site.sync_database()
  File 
"/usr/lib/python2.7/site-packages/ReviewBoard-1.6.13-py2.7.egg/reviewboard/cmdline/rbsite.py",
line 346, in sync_database
    self.run_manage_command("syncdb", params)
  File 
"/usr/lib/python2.7/site-packages/ReviewBoard-1.6.13-py2.7.egg/reviewboard/cmdline/rbsite.py",
line 469, in run_manage_command
    execute_manager(reviewboard.settings, [__file__, cmd] + params)
  File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py",
line 438, in execute_manager
    utility.execute()
  File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py",
line 379, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
line 191, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
line 220, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
line 351, in handle
    return self.handle_noargs(**options)
  File 
"/usr/lib/python2.7/site-packages/django/core/management/commands/syncdb.py",
line 101, in handle_noargs
    cursor.execute(statement)
  File "/usr/lib/python2.7/site-packages/django/db/backends/mysql/base.py",
line 86, in execute
    return self.cursor.execute(query, args)
  File 
"/usr/lib/python2.7/site-packages/MySQL_python-1.2.4b4-py2.7-linux-x86_64.egg/MySQLdb/cursors.py",
line 202, in execute
  File 
"/usr/lib/python2.7/site-packages/MySQL_python-1.2.4b4-py2.7-linux-x86_64.egg/MySQLdb/connections.py",
line 36, in defaulterrorhandler
_mysql_exceptions.OperationalError: (1005, "Can't create table
'./reviewboard/#sql-4eed_51.frm' (errno: 150)")
"""

To make sure it's not a problem with credentials or permissions, I
attempted the install using the mysql root account as well and no
dice.

If I run the upgrade a second time, I get this:

"""
Updating database. This may take a while.
Creating tables ...
Upgrading Review Board from 1.6 to 1.6.13
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 ...
No fixtures found.
Evolution successful.
Resetting in-database caches.
Upgrade complete.
"""

Unfortunately, when I try and login, Apache segfaults:

"""
[Wed Oct 17 14:38:53 2012] [notice] child pid 3210 exit signal
Segmentation fault (11)
"""

Any one have any ideas?

-- 

--tucker

-- 
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

Reply via email to