It's more a Django issue. Django's settings.py has a SITE_ID variable that must be set to the proper ID. This starts at 1, as it's assumed it is an autoincrement at 1.
Review Board in general works with the assumption that IDs are going to be numeric and sequential. I have no idea how review request IDs will look otherwise. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Fri, Mar 4, 2011 at 7:05 AM, Rob Coward <r...@jive-videos.net> wrote: > Seems my hunch about the id fields was correct. I changed my config to > point to a specific node of my mysql cluster rather than the virtual ip, and > it started the autoincrement at 1 and the site created successfully. > > Wonder what would be involved in the rb-site code to check the value of the > id field inserted rather than assuming it started at '1'. > > > > Regards, > > Rob > > > > On Fri, 04 Mar 2011 10:37:59 +0000, Rob Coward wrote: > > Hi Christian, > > Thank you for your reply. I have tried this install on 2 seperate Centos > servers, using the same MySQL backend server, both with the same results. > The copy/paste below was not from the first attempt at creating the site on > this server, but a subsequent retry after first removing the /var/www/ > reviewboard.group.game.net directory. The first time I tried it, the > results were identical but there was additional output logging the creation > of the database tables. I didnt drop the database before the retries, hence > it not recreating the tables. > > This is the contents of my settings file: > > ====================================== > > # Site-specific configuration settings for Review Board > # Definitions of these settings can be found at > # http://docs.djangoproject.com/en/dev/ref/settings/ > > # Database configuration > DATABASES = { > 'default': { > 'ENGINE': 'mysql', > 'NAME': 'reviewboard', > 'USER': 'xxxxxxxxxxxxxx', > 'PASSWORD': 'xxxxxxxxxxxxxxxx', > 'HOST': 'mysql.dev.game.co.uk', > 'PORT': '', > }, > } > > # Unique secret key. Don't share this with anybody. > SECRET_KEY = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' > > # Cache backend settings. > CACHE_BACKEND = 'file:///tmp/reviewboard_cache' > > # Extra site information. > SITE_ID = 1 > SITE_ROOT = '/' > FORCE_SCRIPT_NAME = '' > DEBUG = False > ====================================== > > This particular install was not using memcached, but I have tried it > selecting memcached with the same results. > > It wouldnt surprice me if one of the ReviewBoard pre-req dependencies on > Centos is not a high enough version. The python-mysql module provided in the > Centos Repository wasnt new enough and as part of the installation I have > had to download and install a newer version. > > One thought.... the mysql server I'm connecting to has master-master > replication setup between nodes, and one side-effect of this is that > autoincrementing id columns are not sequential . Does the rb-site code make > assumptions about the next allocated value in 'id' columns ? > > > > Thanks for your help, > > Rob > > > > On Thu, 3 Mar 2011 21:26:17 -0800, Christian Hammond wrote: > > Hi Rob, > > So it looks like it managed to create the database fine, but then the > second step (populating configuration) failed because the data just put into > the database couldn't be found. > > Can you send me your conf/settings_local.py? (You can clear out the > database credentials and secret key first). > > Also, was this your very first attempt at creating this site? > > Christian > > > -- > Christian Hammond - chip...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > > On Wed, Mar 2, 2011 at 6:39 AM, RobC <r...@jive-videos.net> wrote: > >> Hi, >> I'm trying to install the latest version of ReviewBoard on a Centos5.5 >> server, using mysql on a remote server, apache and modpython, >> following the instructions on your site. However I am getting the >> following on trying to configure a site: >> >> rb-site install /var/www/reviewboard.group.game.net >> ..... >> ..... >> * Installing the site... >> Building site directories ... OK >> Building site configuration files ... OK >> Creating database ... Traceback (most recent call last): >> File "/usr/bin/rb-site", line 7, in ? >> sys.exit( >> File "/usr/lib/python2.4/site-packages/ReviewBoard-1.5.4-py2.4.egg/ >> reviewboard/cmdline/rbsite.py", line 1611, in main >> command.run() >> File "/usr/lib/python2.4/site-packages/ReviewBoard-1.5.4-py2.4.egg/ >> reviewboard/cmdline/rbsite.py", line 1177, in run >> self.show_install_status() >> File "/usr/lib/python2.4/site-packages/ReviewBoard-1.5.4-py2.4.egg/ >> reviewboard/cmdline/rbsite.py", line 1436, in show_install_status >> site.sync_database) >> File "/usr/lib/python2.4/site-packages/ReviewBoard-1.5.4-py2.4.egg/ >> reviewboard/cmdline/rbsite.py", line 703, in step >> func() >> File "/usr/lib/python2.4/site-packages/ReviewBoard-1.5.4-py2.4.egg/ >> reviewboard/cmdline/rbsite.py", line 339, in sync_database >> self.run_manage_command("syncdb", params) >> File "/usr/lib/python2.4/site-packages/ReviewBoard-1.5.4-py2.4.egg/ >> reviewboard/cmdline/rbsite.py", line 397, in run_manage_command >> execute_manager(reviewboard.settings, [__file__, cmd] + params) >> File "/usr/lib/python2.4/site-packages/Django-1.2.5-py2.4.egg/django/ >> core/management/__init__.py", line 438, in execute_manager >> utility.execute() >> File "/usr/lib/python2.4/site-packages/Django-1.2.5-py2.4.egg/django/ >> core/management/__init__.py", line 379, in execute >> self.fetch_command(subcommand).run_from_argv(self.argv) >> File "/usr/lib/python2.4/site-packages/Django-1.2.5-py2.4.egg/django/ >> core/management/base.py", line 191, in run_from_argv >> self.execute(*args, **options.__dict__) >> File "/usr/lib/python2.4/site-packages/Django-1.2.5-py2.4.egg/django/ >> core/management/base.py", line 220, in execute >> output = self.handle(*args, **options) >> File "/usr/lib/python2.4/site-packages/Django-1.2.5-py2.4.egg/django/ >> core/management/base.py", line 351, in handle >> return self.handle_noargs(**options) >> File "/usr/lib/python2.4/site-packages/Django-1.2.5-py2.4.egg/django/ >> core/management/commands/syncdb.py", line 107, in handle_noargs >> emit_post_sync_signal(created_models, verbosity, interactive, db) >> File "/usr/lib/python2.4/site-packages/Django-1.2.5-py2.4.egg/django/ >> core/management/sql.py", line 182, in emit_post_sync_signal >> interactive=interactive, db=db) >> File "/usr/lib/python2.4/site-packages/Django-1.2.5-py2.4.egg/django/ >> dispatch/dispatcher.py", line 172, in send >> response = receiver(signal=self, sender=sender, **named) >> File "/usr/lib/python2.4/site-packages/ReviewBoard-1.5.4-py2.4.egg/ >> reviewboard/admin/management/sites.py", line 22, in init_siteconfig >> site = Site.objects.get_current() >> File "/usr/lib/python2.4/site-packages/Django-1.2.5-py2.4.egg/django/ >> contrib/sites/models.py", line 25, in get_current >> current_site = self.get(pk=sid) >> File "/usr/lib/python2.4/site-packages/Django-1.2.5-py2.4.egg/django/ >> db/models/manager.py", line 132, in get >> return self.get_query_set().get(*args, **kwargs) >> File "/usr/lib/python2.4/site-packages/Django-1.2.5-py2.4.egg/django/ >> db/models/query.py", line 346, in get >> raise self.model.DoesNotExist("%s matching query does not exist." >> django.db.models.base.DoesNotExist: Site matching query does not >> exist. >> >> I can see that file get created in the webroot directory, and tables >> are created in the database, so I know file/database permissions isnt >> a problem. Can anyone give me a clue as to where to start looking for >> the problem ? >> >> Thanks, >> Rob >> >> -- >> 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 > > > > -- > 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 > > > -- > 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 > > -- > 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 > -- 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
