Re: Site Migration Issues from 1.5.2 to 1.7.14
Hi Kevin,
Can I know how you performed these steps.
5. Upgrade failed with a 1050 (or similar) error because it couldn't access
some table. So I temporarily overrode django's default database handler to
use mysql + client configs in my.cnf (only a single site will reside on
this VM) via django's conf/global_settings.py, I then ran
'./reviewboard/manage.py syncdb'.
6. syncdb also failed, so I dropped all my tables and re-ran the syncdb.
regards
Bhaskar
On Friday, 14 March 2014 23:20:27 UTC+5:30, Kevin Phillips wrote:
All;
I'm having some issues performing a site migration of RB 1.5.2 to 1.7.14
from an EOL server to a VM. Here are the steps I preformed:
1. Took SQL dump of reviewboard database and restored on new system
2. Took copy of application web root and copied to new system
3. Configured memcached on new system.
3. Installed Reviewboard==1.7.14 Django==1.4.10 python-memcached
MySQL-python + deps via easy_install (Python 2.7.3)
4. Preformed a rb-site upgrade of application web root.
5. Upgrade failed with a 1050 (or similar) error because it couldn't
access some table. So I temporarily overrode django's default database
handler to use mysql + client configs in my.cnf (only a single site will
reside on this VM) via django's conf/global_settings.py, I then ran
'./reviewboard/manage.py syncdb'.
6. syncdb also failed, so I dropped all my tables and re-ran the syncdb.
7. The second syncdb after dropping my tables worked, then I re-ran the
rb-site upgrade
8. The second rb-site upgrade was successful but prompted me to modify my
apache vhost config and validate the site settings.
9. I actioned the changes and restarted the web server.
After this I get the error 500 page but I get a mod_python stack trace
(yes I know mod_python is simply in there for legacy purposes, but the old
site ran it and I cannot figure out how to cut-over to mod_wsgi).
STACKTRACE:
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] mod_python
(pid=2342, interpreter='reviewboard_review_vmem_com',
phase='PythonHandler', handler='django.core.handlers.modpython'):
Application error, referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] ServerName:
'reviewboard.sub.domain', referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] DocumentRoot:
'/var/www/review.vmem.com/htdocs', referer:
http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] URI: '/review/',
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Location:
'/review/', referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Directory: None,
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Filename:
'/var/www/review.vmem.com/htdocs/review', referer:
http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] PathInfo: '/',
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Traceback (most
recent call last):, referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] File
/usr/lib/python2.7/dist-packages/mod_python/importer.py, line 1537, in
HandlerDispatch\ndefault=default_handler, arg=req,
silent=hlist.silent), referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] File
/usr/lib/python2.7/dist-packages/mod_python/importer.py, line 1202, in
_process_target\nmodule = import_module(module_name, path=path),
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] File
/usr/lib/python2.7/dist-packages/mod_python/importer.py, line 304, in
import_module\nreturn __import__(module_name, {}, {}, ['*']), referer:
http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] ImportError: No
module named django.core.handlers.modpython, referer:
http://reviewboard.sub.domain/review/
VHOST CONFIG
VirtualHost *:80
ServerName reviewboard.sub.domain
DocumentRoot /var/www/reviewboard/htdocs
# Error handlers
ErrorDocument 500 /errordocs/500.html
# Serve django pages
Location /review/
PythonPath ['/var/www/reviewboard/conf'] + sys.path
SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings
SetEnv PYTHON_EGG_CACHE /var/www/reviewboard/tmp/egg_cache
SetHandler mod_python
PythonHandler django.core.handlers.modpython
PythonAutoReload Off
PythonDebug Off
# Used to run multiple mod_python sites in the same apache
PythonInterpreter reviewboard_reviewboard
/Location
# Serve static without running it through mod_python
# Required for upgrade from Reviewboard 1.5.2 to 1.7.14
Location /review/static
SetHandler None
/Location
Re: Error: Error applying evolution: (1051, Unknown table 'auth_message')
Hi Kevin, I did what you said but I am on same page. Can you please provide the procedure to do migration. regards bahskar On Wed, Mar 19, 2014 at 12:38 AM, Kevin Phillips kevin.grenville.phill...@gmail.com wrote: Your database dump appears incomplete. Try dumping with --max_allowed_packet=512M (large packet to avoid truncation). Check your 1.5.X db and verify the table exists in production and in the backup. Also verify all your tables are InnoDB instead of MYISAM, you can make manual modification to the table engine without much recourse. Take a look at my thread, I just migrated 1.5.2 to 1.7.14 on the same platform as you. KP On Tuesday, March 18, 2014 2:31:44 AM UTC-7, Bhaskar Roy wrote: Hi Christian, I am trying migration on new server and not in current production box. 1. On new server I installed ubuntu 12.04/mysql 5.5/RB 1.7.14 1. I took backup of SQL and copied to new server and done rb-site upgrade. Copied the databse to new server and tired . I get error messages as listed above. regards Bhaskar On Thu, Mar 13, 2014 at 12:53 AM, Christian Hammond chi...@chipx86.comwrote: Hi, First, did you back up your database? Second, can you verify the version of Review Board you've upgraded to, and also verify the version of django-evolution installed? (These should be in your Python's site-packages directory). You shouldn't do *any* hand-modifying of the database of any sort, or you'll cause further issues in the upgrade process. Our stuff expects to own the full schema of the database. Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Wed, Mar 12, 2014 at 3:23 AM, Bhaskar Roy bhaska...@gmail.comwrote: Hi Christian, I am getting following error while doing site upgrade from 1.5 to Latest 1.7. Even created auth_message tablein MySqL DB. /usr/bin/python /usr/local/bin/rb-site upgrade /var/www/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 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. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Evolution could not be simulated, possibly due to raw SQL mutations Error: Error applying evolution: (1051, Unknown table 'auth_message') Regards bhaskar -- 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...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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/d/optout. -- 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/d/optout.
There was no repository found at the specified path (HTTP 400, API Error 205)
I have setup rbt post as a custom tool in P4 with these arguments:
C:\Python27\Scripts\rbt.exe post --server http://[domain]:[port]/[path]/ -d
--username=user --password=pass %C
The output shows the diff of the files in my changelist but it ends up
giving me this error:
Making HTTP GET request to
http://[domain]:[port]/[path]/api/review-requests/
Making HTTP POST request to http://[domain]:[port]/[path]
/api/review-requests/
Got API Error 205 (HTTP code 400): There was no repository found at the
specified path
Error data: {u'stat': u'fail', u'err': {u'msg': u'There was no
repository found at the specified path', u'code': 205}}
Traceback (most recent call last):
File C:\Python27\Scripts\rbt-script.py, line 9, in module
load_entry_point('rbtools==0.6alpha0.dev', 'console_scripts', 'rbt')()
File
C:\Python27\lib\site-packages\rbtools-0.6alpha0.dev-py2.7.egg\rbtools\commands\main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
C:\Python27\lib\site-packages\rbtools-0.6alpha0.dev-py2.7.egg\rbtools\commands\__init__.py,
line 422, in run_from_argv
exit_code = self.main(*args) or 0
File
C:\Python27\lib\site-packages\rbtools-0.6alpha0.dev-py2.7.egg\rbtools\commands\post.py,
line 769, in main
submit_as=self.options.submit_as)
File
C:\Python27\lib\site-packages\rbtools-0.6alpha0.dev-py2.7.egg\rbtools\commands\post.py,
line 503, in post_request
raise CommandError(Error creating review request: %s % e)
rbtools.commands.CommandError: Error creating review request: There was no
repository found at the specified path (HTTP 400, API Error 205)
However, it creates a review draft in the UI with my username but no files
in it.
I cannot find any .reviewboardrc files, so I guess everything needs to be
passed as an argument to the script.
My review board instalaltion is here http://[domain]:[port]/[path]
/dashboard/.
Any ideas where I'm going wrong?
Thank you.
--
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/d/optout.
Re: Site Installation Failing with database error.
Hi Christian,
i am getting below error. How can i resolve.
Installed /usr/local/lib/python2.7/dist-packages/ReviewBoard-1.5.1-py2.7.egg
Reading http://downloads.reviewboard.org/mirror/
Processing dependencies for ReviewBoard==1.5.1
error: Installed distribution Django 1.3.3 conflicts with requirement
Django=1.4.8,1.5
I manually installed Django 1.3.3 using easy_install
regards
Bhaskar
On Friday, 31 August 2012 04:55:36 UTC+5:30, Christian Hammond wrote:
Hi,
You'll need to remove Django 1.4 and downgrade to 1.3.3. Only the upcoming
Review Board 1.7 betas support Django 1.4.
I assume you're upgrading to the latest 1.6, and not 1.7 beta?
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Aug 30, 2012 at 2:53 PM, CudaPrime cuda...@gmail.comjavascript:
wrote:
Hi all, any help would be appreciated here. I'm a complete noob to Review
Board and it's installation. That said I've been tasked with upgrading our
current 1.5.5 installation to the most current.
I've created a test machine and loaded CentOS 6.3, installed the
dependencies I know about from the installation documentation, and finally
succeeded in getting ReviewBoard installed, at least I'm pretty sure it's
installed.
When I attempt to run rb-site install /var/www/reviewboard
I get this;
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/conf/__init__.py:75:
DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use
STATIC_URL instead.
use STATIC_URL instead., DeprecationWarning)
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/cache/__init__.py:82:
DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES
instead.
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 8, in module
load_entry_point('ReviewBoard==1.5.5', 'console_scripts', 'rb-site')()
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 1611, in main
command.run()
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 1177, in run
self.show_install_status()
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 1436, in show_install_status
site.sync_database)
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 703, in step
func()
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 339, in sync_database
self.run_manage_command(syncdb, params)
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 397, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/__init__.py,
line 459, in execute_manager
utility.execute()
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/__init__.py,
line 382, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/base.py,
line 196, in run_from_argv
self.execute(*args, **options.__dict__)
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/base.py,
line 232, in execute
output = self.handle(*args, **options)
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/base.py,
line 371, in handle
return self.handle_noargs(**options)
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/commands/syncdb.py,
line 57, in handle_noargs
cursor = connection.cursor()
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/db/backends/dummy/base.py,
line 15, in complain
raise ImproperlyConfigured(settings.DATABASES is improperly
configured.
django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
improperly configured. Please supply the ENGINE value. Check settings
documentation for more details.
It appears that django can't properly access mySQL to create it's
database, I've checked and rechecked and I can access the database via
command line, so I'm not sure why the site installion would be having a
problem.
Thanks in advance for any help!
--
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
Re: There was no repository found at the specified path (HTTP 400, API Error 205)
Hi David,
The .reviewboardrc file is one you create. You'll want to place that in the
root of the repository and commit it.
If the Path field in the repository entry on Review Board doesn't perfectly
match what you have locally, you'll need to set 'REPOSITORY = ...' in
.reviewboardrc to match the Name field of the repository. We generally
recommend this anyway.
You can also just use 'rbt setup-repo' to get this going.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Wed, Mar 19, 2014 at 8:35 AM, David Saltares Márquez
david.salta...@gmail.com wrote:
I have setup rbt post as a custom tool in P4 with these arguments:
C:\Python27\Scripts\rbt.exe post --server http://[domain]:[port]/[path]/ -d
--username=user --password=pass %C
The output shows the diff of the files in my changelist but it ends up
giving me this error:
Making HTTP GET request to http://
[domain]:[port]/[path]/api/review-requests/
Making HTTP POST request to http://[domain]:[port]/[path]
/api/review-requests/
Got API Error 205 (HTTP code 400): There was no repository found at
the specified path
Error data: {u'stat': u'fail', u'err': {u'msg': u'There was no
repository found at the specified path', u'code': 205}}
Traceback (most recent call last):
File C:\Python27\Scripts\rbt-script.py, line 9, in module
load_entry_point('rbtools==0.6alpha0.dev', 'console_scripts', 'rbt')()
File
C:\Python27\lib\site-packages\rbtools-0.6alpha0.dev-py2.7.egg\rbtools\commands\main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
C:\Python27\lib\site-packages\rbtools-0.6alpha0.dev-py2.7.egg\rbtools\commands\__init__.py,
line 422, in run_from_argv
exit_code = self.main(*args) or 0
File
C:\Python27\lib\site-packages\rbtools-0.6alpha0.dev-py2.7.egg\rbtools\commands\post.py,
line 769, in main
submit_as=self.options.submit_as)
File
C:\Python27\lib\site-packages\rbtools-0.6alpha0.dev-py2.7.egg\rbtools\commands\post.py,
line 503, in post_request
raise CommandError(Error creating review request: %s % e)
rbtools.commands.CommandError: Error creating review request: There was no
repository found at the specified path (HTTP 400, API Error 205)
However, it creates a review draft in the UI with my username but no files
in it.
I cannot find any .reviewboardrc files, so I guess everything needs to be
passed as an argument to the script.
My review board instalaltion is here http://[domain]:[port]/[path]
/dashboard/.
Any ideas where I'm going wrong?
Thank you.
--
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/d/optout.
--
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/d/optout.
Re: Site Installation Failing with database error.
It looks like you're trying to downgrade. You are not going to have luck
with that without getting rid of every dependency that the newer version of
Review Board required (and the ones that those required).
I assumed you were attempting the upgrade on a different server?
This is really not the thread for this though. It's best that you keep the
discussions on the single thread.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Wed, Mar 19, 2014 at 11:44 AM, Bhaskar Roy bhaskar.p@gmail.comwrote:
Hi Christian,
i am getting below error. How can i resolve.
Installed
/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.5.1-py2.7.egg
Reading http://downloads.reviewboard.org/mirror/
Processing dependencies for ReviewBoard==1.5.1
error: Installed distribution Django 1.3.3 conflicts with requirement
Django=1.4.8,1.5
I manually installed Django 1.3.3 using easy_install
regards
Bhaskar
On Friday, 31 August 2012 04:55:36 UTC+5:30, Christian Hammond wrote:
Hi,
You'll need to remove Django 1.4 and downgrade to 1.3.3. Only the
upcoming Review Board 1.7 betas support Django 1.4.
I assume you're upgrading to the latest 1.6, and not 1.7 beta?
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Aug 30, 2012 at 2:53 PM, CudaPrime cuda...@gmail.com wrote:
Hi all, any help would be appreciated here. I'm a complete noob to
Review Board and it's installation. That said I've been tasked with
upgrading our current 1.5.5 installation to the most current.
I've created a test machine and loaded CentOS 6.3, installed the
dependencies I know about from the installation documentation, and finally
succeeded in getting ReviewBoard installed, at least I'm pretty sure it's
installed.
When I attempt to run rb-site install /var/www/reviewboard
I get this;
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/conf/__init__.py:75: DeprecationWarning: The
ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead.
use STATIC_URL instead., DeprecationWarning)
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/cache/__init__.py:82: DeprecationWarning:
settings.CACHE_* is deprecated; use settings.CACHES instead.
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 8, in module
load_entry_point('ReviewBoard==1.5.5', 'console_scripts',
'rb-site')()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1611, in main
command.run()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1177, in run
self.show_install_status()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1436, in
show_install_status
site.sync_database)
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 703, in step
func()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 339, in sync_database
self.run_manage_command(syncdb, params)
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 397, in
run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/__init__.py, line 459, in execute_manager
utility.execute()
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/__init__.py, line 382, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/base.py, line 196, in run_from_argv
self.execute(*args, **options.__dict__)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/base.py, line 232, in execute
output = self.handle(*args, **options)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/base.py, line 371, in handle
return self.handle_noargs(**options)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/commands/syncdb.py, line 57, in
handle_noargs
cursor = connection.cursor()
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/db/backends/dummy/base.py, line 15, in complain
raise ImproperlyConfigured(settings.DATABASES is improperly
configured.
django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
improperly configured. Please supply the ENGINE value. Check settings
Re: Site Migration Issues from 1.5.2 to 1.7.14
The 1050 error from django was due to changes in to configuration file
format. Instead of using the format:
DATABASE_ENGINE = '',
DATABASE_NAME='',
.
.
.
The devs changed the format to:
DATABASES = {
'default' : {
'ENGINE': 'django.db.backends,mysql',
'NAME': '',
'USER': '',
'PASSWORD': '',
'HOST': '',
},
}
The caches format has changed similarly.
# Cache backend settings.
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION': 'localhost:11211',
},
}
Have you verified the integrity of your dump? If so, you should not have to
drop your tables just convert them all to InnoDB. If you don't convert your
tables you will see sql errors when the upgrade script attempts to create
primary keys in the database.
KP
On Wednesday, March 19, 2014 3:09:29 AM UTC-7, Bhaskar Roy wrote:
Hi Kevin,
Can I know how you performed these steps.
5. Upgrade failed with a 1050 (or similar) error because it couldn't
access some table. So I temporarily overrode django's default database
handler to use mysql + client configs in my.cnf (only a single site will
reside on this VM) via django's conf/global_settings.py, I then ran
'./reviewboard/manage.py syncdb'.
6. syncdb also failed, so I dropped all my tables and re-ran the syncdb.
regards
Bhaskar
On Friday, 14 March 2014 23:20:27 UTC+5:30, Kevin Phillips wrote:
All;
I'm having some issues performing a site migration of RB 1.5.2 to 1.7.14
from an EOL server to a VM. Here are the steps I preformed:
1. Took SQL dump of reviewboard database and restored on new system
2. Took copy of application web root and copied to new system
3. Configured memcached on new system.
3. Installed Reviewboard==1.7.14 Django==1.4.10 python-memcached
MySQL-python + deps via easy_install (Python 2.7.3)
4. Preformed a rb-site upgrade of application web root.
5. Upgrade failed with a 1050 (or similar) error because it couldn't
access some table. So I temporarily overrode django's default database
handler to use mysql + client configs in my.cnf (only a single site will
reside on this VM) via django's conf/global_settings.py, I then ran
'./reviewboard/manage.py syncdb'.
6. syncdb also failed, so I dropped all my tables and re-ran the syncdb.
7. The second syncdb after dropping my tables worked, then I re-ran the
rb-site upgrade
8. The second rb-site upgrade was successful but prompted me to modify my
apache vhost config and validate the site settings.
9. I actioned the changes and restarted the web server.
After this I get the error 500 page but I get a mod_python stack trace
(yes I know mod_python is simply in there for legacy purposes, but the old
site ran it and I cannot figure out how to cut-over to mod_wsgi).
STACKTRACE:
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] mod_python
(pid=2342, interpreter='reviewboard_review_vmem_com',
phase='PythonHandler', handler='django.core.handlers.modpython'):
Application error, referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] ServerName:
'reviewboard.sub.domain', referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] DocumentRoot:
'/var/www/review.vmem.com/htdocs', referer:
http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] URI: '/review/',
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Location:
'/review/', referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Directory: None,
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Filename:
'/var/www/review.vmem.com/htdocs/review', referer:
http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] PathInfo: '/',
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] Traceback (most
recent call last):, referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] File
/usr/lib/python2.7/dist-packages/mod_python/importer.py, line 1537, in
HandlerDispatch\ndefault=default_handler, arg=req,
silent=hlist.silent), referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] File
/usr/lib/python2.7/dist-packages/mod_python/importer.py, line 1202, in
_process_target\nmodule = import_module(module_name, path=path),
referer: http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client 10.12.21.48] File
/usr/lib/python2.7/dist-packages/mod_python/importer.py, line 304, in
import_module\nreturn __import__(module_name, {}, {}, ['*']), referer:
http://reviewboard.sub.domain/review/
[Fri Mar 14 09:48:18 2014] [error] [client
Re: Error: Error applying evolution: (1051, Unknown table 'auth_message')
admin@remotehost1:~$ export REVIEWBOARD_DB_NAME=review admin@remotehost1:~$ mysqldump -u backup -p --max_allowed_packet=512M $REVIEWBOARD_DB_NAME /tmp/reviewboard-`date`.sql admin@remotehost1:~$ scp /tmp/reviewboard-`date`.sql admin@remotehost2:/tmp/ admin@remotehost1:~$ scp -r /var/www/reviewboard-1.5.2 admin@remotehost2:/var/www/reviewboard-1.7.14 admin@remotehost2:~$ sudo apt-get install mysql-server libmysqlclient-dev memcached ntpd apache2 libapach2-mod-wsgi libapache2-mod-python admin@remotehost2:~$ sudo easy_install Reviewboard==1.7.14 Django==1.4.10 python-memcached MySQL-Python admin@remotehost2:~$ sudo easy_install -m Reviewboard==1.7.14 admin@remotehost2:~$ sudo cp /var/www/reviewboard-1.7.14/conf/settings_local.py /home/admin admin@remotehost2:~$ vim /home/admin/settings_local.py (make the mentioned changes from my thread) admin@remotehost2:~$ sudo cp /home/admin/settings_local.py /usr/local/lib/python2.7/dist-packages/Reviewboard-1.7.14-py2.7.egg/reviewboard/ admin@remotehost2:~$ mysql -u root -p mysql create database review; mysql create user 'review'@'localhost' identified by 'password'; mysql grant all on review.* to 'review'@'localhost'; admin@remotehost2:~$ mysql --max_allowed_packet=128M -u review -p review /tmp/reviewboard-`date`.sql admin@remotehost2:~$ mysql -u root -p review mysql show table status mysql alter table `table_name` engine='InnoDB'; (there are definitely faster ways, but I can't spoon feed you everything...) admin@remotehost2:~$ sudo rb-site --version (confirm you are at 1.7.14) admin@remotehost2:~$ sudo rb-site upgrade /var/www/reviewboard-1.7.14 For Apache, you will need to add: Location /review/static SetHandler None /Location Alias /review/static /var/www/reviewboard-1.7.14/htdocs/statichttp://review.company.com/htdocs/static For lighttpd: alias.url = ( ... /review/static = /var/www/review.company.com/htdocs/static, ... ) url.rewrite-once = ( ... ^(/review/static/.*)$ = $1, ... ) Once you have made these changes, type the following to resolve this: $ rb-site manage /var/www/r http://review.company.com/eviewboard-1.7.14 resolve-check static-media Make the changes... admin@remotehost2:~$ ln -s /var/www/reviewboard-1.7.14 /var/www/review admin@remotehost2:~$ rb-site manage /var/www/reviewboard-1.7.14 resolve-check static-media And for good measure... admin@remotehost2:~$ rb-site manage /var/www/reviewboard-1.7.14 syncdb Hope that helps, KP On Wednesday, March 19, 2014 3:11:13 AM UTC-7, Bhaskar Roy wrote: Hi Kevin, I did what you said but I am on same page. Can you please provide the procedure to do migration. regards bahskar On Wed, Mar 19, 2014 at 12:38 AM, Kevin Phillips kevin.grenvi...@gmail.com javascript: wrote: Your database dump appears incomplete. Try dumping with --max_allowed_packet=512M (large packet to avoid truncation). Check your 1.5.X db and verify the table exists in production and in the backup. Also verify all your tables are InnoDB instead of MYISAM, you can make manual modification to the table engine without much recourse. Take a look at my thread, I just migrated 1.5.2 to 1.7.14 on the same platform as you. KP On Tuesday, March 18, 2014 2:31:44 AM UTC-7, Bhaskar Roy wrote: Hi Christian, I am trying migration on new server and not in current production box. 1. On new server I installed ubuntu 12.04/mysql 5.5/RB 1.7.14 1. I took backup of SQL and copied to new server and done rb-site upgrade. Copied the databse to new server and tired . I get error messages as listed above. regards Bhaskar On Thu, Mar 13, 2014 at 12:53 AM, Christian Hammond chi...@chipx86.comwrote: Hi, First, did you back up your database? Second, can you verify the version of Review Board you've upgraded to, and also verify the version of django-evolution installed? (These should be in your Python's site-packages directory). You shouldn't do *any* hand-modifying of the database of any sort, or you'll cause further issues in the upgrade process. Our stuff expects to own the full schema of the database. Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Wed, Mar 12, 2014 at 3:23 AM, Bhaskar Roy bhaska...@gmail.comwrote: Hi Christian, I am getting following error while doing site upgrade from 1.5 to Latest 1.7. Even created auth_message tablein MySqL DB. /usr/bin/python /usr/local/bin/rb-site upgrade /var/www/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 sessions. There are unapplied evolutions
Re: Site Installation Failing with database error.
Christian;
Could he not just modify his settings_local.py to reflect to updates to the
file format. The specific errors are for CACHES and DATABASES which are
defined in that file. I understand Django-1.4 is not supposed to be
supported.
KP
On Thursday, August 30, 2012 4:25:36 PM UTC-7, Christian Hammond wrote:
Hi,
You'll need to remove Django 1.4 and downgrade to 1.3.3. Only the upcoming
Review Board 1.7 betas support Django 1.4.
I assume you're upgrading to the latest 1.6, and not 1.7 beta?
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Aug 30, 2012 at 2:53 PM, CudaPrime cuda...@gmail.comjavascript:
wrote:
Hi all, any help would be appreciated here. I'm a complete noob to Review
Board and it's installation. That said I've been tasked with upgrading our
current 1.5.5 installation to the most current.
I've created a test machine and loaded CentOS 6.3, installed the
dependencies I know about from the installation documentation, and finally
succeeded in getting ReviewBoard installed, at least I'm pretty sure it's
installed.
When I attempt to run rb-site install /var/www/reviewboard
I get this;
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/conf/__init__.py:75:
DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use
STATIC_URL instead.
use STATIC_URL instead., DeprecationWarning)
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/cache/__init__.py:82:
DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES
instead.
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 8, in module
load_entry_point('ReviewBoard==1.5.5', 'console_scripts', 'rb-site')()
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 1611, in main
command.run()
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 1177, in run
self.show_install_status()
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 1436, in show_install_status
site.sync_database)
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 703, in step
func()
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 339, in sync_database
self.run_manage_command(syncdb, params)
File
/usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-py2.6.egg/reviewboard/cmdline/rbsite.py,
line 397, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/__init__.py,
line 459, in execute_manager
utility.execute()
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/__init__.py,
line 382, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/base.py,
line 196, in run_from_argv
self.execute(*args, **options.__dict__)
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/base.py,
line 232, in execute
output = self.handle(*args, **options)
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/base.py,
line 371, in handle
return self.handle_noargs(**options)
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/core/management/commands/syncdb.py,
line 57, in handle_noargs
cursor = connection.cursor()
File
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.egg/django/db/backends/dummy/base.py,
line 15, in complain
raise ImproperlyConfigured(settings.DATABASES is improperly
configured.
django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
improperly configured. Please supply the ENGINE value. Check settings
documentation for more details.
It appears that django can't properly access mySQL to create it's
database, I've checked and rechecked and I can access the database via
command line, so I'm not sure why the site installion would be having a
problem.
Thanks in advance for any help!
--
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 javascript:
For more options, visit this group at
Re: Site Installation Failing with database error.
Review Board 1.5 will flat-out fail with Django 1.4. Django goes through
deprecation processes in their releases, and we're using a number of things
in RB 1.5 that are gone in Django 1.4, and other things that have changed.
Updating settings_local.py wouldn't be sufficient.
This is also true with our versions of Djblets, and some other dependencies
we use.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Wed, Mar 19, 2014 at 3:20 PM, Kevin Phillips
kevin.grenville.phill...@gmail.com wrote:
Christian;
Could he not just modify his settings_local.py to reflect to updates to
the file format. The specific errors are for CACHES and DATABASES which are
defined in that file. I understand Django-1.4 is not supposed to be
supported.
KP
On Thursday, August 30, 2012 4:25:36 PM UTC-7, Christian Hammond wrote:
Hi,
You'll need to remove Django 1.4 and downgrade to 1.3.3. Only the
upcoming Review Board 1.7 betas support Django 1.4.
I assume you're upgrading to the latest 1.6, and not 1.7 beta?
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Aug 30, 2012 at 2:53 PM, CudaPrime cuda...@gmail.com wrote:
Hi all, any help would be appreciated here. I'm a complete noob to
Review Board and it's installation. That said I've been tasked with
upgrading our current 1.5.5 installation to the most current.
I've created a test machine and loaded CentOS 6.3, installed the
dependencies I know about from the installation documentation, and finally
succeeded in getting ReviewBoard installed, at least I'm pretty sure it's
installed.
When I attempt to run rb-site install /var/www/reviewboard
I get this;
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/conf/__init__.py:75: DeprecationWarning: The
ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead.
use STATIC_URL instead., DeprecationWarning)
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/cache/__init__.py:82: DeprecationWarning:
settings.CACHE_* is deprecated; use settings.CACHES instead.
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 8, in module
load_entry_point('ReviewBoard==1.5.5', 'console_scripts',
'rb-site')()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1611, in main
command.run()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1177, in run
self.show_install_status()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1436, in
show_install_status
site.sync_database)
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 703, in step
func()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 339, in sync_database
self.run_manage_command(syncdb, params)
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 397, in
run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/__init__.py, line 459, in execute_manager
utility.execute()
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/__init__.py, line 382, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/base.py, line 196, in run_from_argv
self.execute(*args, **options.__dict__)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/base.py, line 232, in execute
output = self.handle(*args, **options)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/base.py, line 371, in handle
return self.handle_noargs(**options)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/commands/syncdb.py, line 57, in
handle_noargs
cursor = connection.cursor()
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/db/backends/dummy/base.py, line 15, in complain
raise ImproperlyConfigured(settings.DATABASES is improperly
configured.
django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
improperly configured. Please supply the ENGINE value. Check settings
documentation for more details.
It appears that django can't properly access mySQL to create it's
database, I've checked and rechecked and I can access the
Re: Site Installation Failing with database error.
Doh, I should have realized. Thanks for filling me in.
KP
On Wednesday, March 19, 2014 4:30:01 PM UTC-7, Christian Hammond wrote:
Review Board 1.5 will flat-out fail with Django 1.4. Django goes through
deprecation processes in their releases, and we're using a number of things
in RB 1.5 that are gone in Django 1.4, and other things that have changed.
Updating settings_local.py wouldn't be sufficient.
This is also true with our versions of Djblets, and some other
dependencies we use.
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On Wed, Mar 19, 2014 at 3:20 PM, Kevin Phillips
kevin.grenvi...@gmail.comjavascript:
wrote:
Christian;
Could he not just modify his settings_local.py to reflect to updates to
the file format. The specific errors are for CACHES and DATABASES which are
defined in that file. I understand Django-1.4 is not supposed to be
supported.
KP
On Thursday, August 30, 2012 4:25:36 PM UTC-7, Christian Hammond wrote:
Hi,
You'll need to remove Django 1.4 and downgrade to 1.3.3. Only the
upcoming Review Board 1.7 betas support Django 1.4.
I assume you're upgrading to the latest 1.6, and not 1.7 beta?
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Aug 30, 2012 at 2:53 PM, CudaPrime cuda...@gmail.com wrote:
Hi all, any help would be appreciated here. I'm a complete noob to
Review Board and it's installation. That said I've been tasked with
upgrading our current 1.5.5 installation to the most current.
I've created a test machine and loaded CentOS 6.3, installed the
dependencies I know about from the installation documentation, and finally
succeeded in getting ReviewBoard installed, at least I'm pretty sure it's
installed.
When I attempt to run rb-site install /var/www/reviewboard
I get this;
* Installing the site...
Building site directories ... OK
Building site configuration files ... OK
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/conf/__init__.py:75: DeprecationWarning: The
ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead.
use STATIC_URL instead., DeprecationWarning)
/usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/cache/__init__.py:82: DeprecationWarning:
settings.CACHE_* is deprecated; use settings.CACHES instead.
DeprecationWarning
Creating database ... Traceback (most recent call last):
File /usr/bin/rb-site, line 8, in module
load_entry_point('ReviewBoard==1.5.5', 'console_scripts',
'rb-site')()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1611, in main
command.run()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1177, in run
self.show_install_status()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 1436, in
show_install_status
site.sync_database)
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 703, in step
func()
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 339, in sync_database
self.run_manage_command(syncdb, params)
File /usr/lib/python2.6/site-packages/ReviewBoard-1.5.5-
py2.6.egg/reviewboard/cmdline/rbsite.py, line 397, in
run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/__init__.py, line 459, in execute_manager
utility.execute()
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/__init__.py, line 382, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/base.py, line 196, in run_from_argv
self.execute(*args, **options.__dict__)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/base.py, line 232, in execute
output = self.handle(*args, **options)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/base.py, line 371, in handle
return self.handle_noargs(**options)
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/core/management/commands/syncdb.py, line 57, in
handle_noargs
cursor = connection.cursor()
File /usr/lib/python2.6/site-packages/Django-1.4.1-py2.6.
egg/django/db/backends/dummy/base.py, line 15, in complain
raise ImproperlyConfigured(settings.DATABASES is improperly
configured.
django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
improperly configured. Please supply the
Unable to drop issue
Hi, One user raised an issue during a particular review and he was not able to drop that issue. Is it because this can be done by the admin only? I am admin and I was able to see the options: Fixed and Drop, but he could not. I am using RB 1.7.21. Thx for your help guys -- 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/d/optout.
Re: Unable to drop issue
In 1.7.x, only the owner of the review request (and admins) can drop an issue. I'm 2.0, the person who filed the issue will be able to drop it (or reopen it). Christian On Wednesday, March 19, 2014, MoonWalker daniel.cabrera...@gmail.com wrote: Hi, One user raised an issue during a particular review and he was not able to drop that issue. Is it because this can be done by the admin only? I am admin and I was able to see the options: Fixed and Drop, but he could not. I am using RB 1.7.21. Thx for your help guys -- 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.comjavascript:_e(%7B%7D,'cvml','reviewboard%2bunsubscr...@googlegroups.com'); . For more options, visit https://groups.google.com/d/optout. -- -- Christian Hammond - chip...@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/d/optout.
Using Powerpack
Hi, I have installed the trial license of ReviewBoard power pack. How to create a pdf document review using this power pack? I am not able to see anything specific to the power pack within the Reviewboard site. Please provide guidance. Regards, Dhananjay. -- 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/d/optout.
Re: Unable to drop issue
Thanks for the info. and looking forward to switch to 2.0 once passes the beta stage. On Thursday, March 20, 2014 2:31:03 PM UTC+11, Christian Hammond wrote: In 1.7.x, only the owner of the review request (and admins) can drop an issue. I'm 2.0, the person who filed the issue will be able to drop it (or reopen it). Christian On Wednesday, March 19, 2014, MoonWalker daniel.c...@gmail.comjavascript: wrote: Hi, One user raised an issue during a particular review and he was not able to drop that issue. Is it because this can be done by the admin only? I am admin and I was able to see the options: Fixed and Drop, but he could not. I am using RB 1.7.21. Thx for your help guys -- 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/d/optout. -- -- Christian Hammond - chi...@chipx86.com javascript: 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/d/optout.
Re: Error: Error applying evolution: (1051, Unknown table 'auth_message')
Hi Kevin,
What changes I need to make for the points mentioned below line?
admin@remotehost2:~$ sudo cp
/var/www/reviewboard-1.7.14/conf/settings_local.py /home/admin
admin@remotehost2:~$ vim /home/admin/settings_local.py (make the mentioned
changes from my thread
My current settings file looks like this.
# 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': 'django.db.backends.mysql',
'NAME': 'reviewboard',
'USER': 'root',
'PASSWORD': 'password',
'HOST': 'localhost',
},
}
# Unique secret key. Don't share this with anybody.
SECRET_KEY = 'ic%zzz9a#p_m#1=lip_5_1mkidljkgh89090t@s93fku#kdh@c'
# Cache backend settings.
CACHE_BACKEND = 'memcached://localhost:11211/'
# Extra site information.
SITE_ID = 1
SITE_ROOT = '/'
FORCE_SCRIPT_NAME = ''
DEBUG = True
On Thu, Mar 20, 2014 at 3:48 AM, Kevin Phillips
kevin.grenville.phill...@gmail.com wrote:
admin@remotehost1:~$ export REVIEWBOARD_DB_NAME=review
admin@remotehost1:~$ mysqldump -u backup -p --max_allowed_packet=512M
$REVIEWBOARD_DB_NAME /tmp/reviewboard-`date`.sql
admin@remotehost1:~$ scp /tmp/reviewboard-`date`.sql admin@remotehost2
:/tmp/
admin@remotehost1:~$ scp -r /var/www/reviewboard-1.5.2 admin@remotehost2
:/var/www/reviewboard-1.7.14
admin@remotehost2:~$ sudo apt-get install mysql-server libmysqlclient-dev
memcached ntpd apache2 libapach2-mod-wsgi libapache2-mod-python
admin@remotehost2:~$ sudo easy_install Reviewboard==1.7.14 Django==1.4.10
python-memcached MySQL-Python
admin@remotehost2:~$ sudo easy_install -m Reviewboard==1.7.14
admin@remotehost2:~$ sudo cp
/var/www/reviewboard-1.7.14/conf/settings_local.py /home/admin
admin@remotehost2:~$ vim /home/admin/settings_local.py (make the
mentioned changes from my thread)
admin@remotehost2:~$ sudo cp /home/admin/settings_local.py
/usr/local/lib/python2.7/dist-packages/Reviewboard-1.7.14-py2.7.egg/reviewboard/
admin@remotehost2:~$ mysql -u root -p
mysql create database review;
mysql create user 'review'@'localhost' identified by 'password';
mysql grant all on review.* to 'review'@'localhost';
admin@remotehost2:~$ mysql --max_allowed_packet=128M -u review -p review
/tmp/reviewboard-`date`.sql
admin@remotehost2:~$ mysql -u root -p review
mysql show table status
mysql alter table `table_name` engine='InnoDB'; (there are definitely
faster ways, but I can't spoon feed you everything...)
admin@remotehost2:~$ sudo rb-site --version (confirm you are at 1.7.14)
admin@remotehost2:~$ sudo rb-site upgrade /var/www/reviewboard-1.7.14
For Apache, you will need to add:
Location /review/static
SetHandler None
/Location
Alias /review/static
/var/www/reviewboard-1.7.14/htdocs/statichttp://review.company.com/htdocs/static
For lighttpd:
alias.url = (
...
/review/static = /var/www/review.company.com/htdocs/static,
...
)
url.rewrite-once = (
...
^(/review/static/.*)$ = $1,
...
)
Once you have made these changes, type the following
to resolve this:
$ rb-site manage /var/www/r http://review.company.com/eviewboard-1.7.14
resolve-check
static-media
Make the changes...
admin@remotehost2:~$ ln -s /var/www/reviewboard-1.7.14 /var/www/review
admin@remotehost2:~$ rb-site manage /var/www/reviewboard-1.7.14
resolve-check static-media
And for good measure...
admin@remotehost2:~$ rb-site manage /var/www/reviewboard-1.7.14 syncdb
Hope that helps,
KP
On Wednesday, March 19, 2014 3:11:13 AM UTC-7, Bhaskar Roy wrote:
Hi Kevin,
I did what you said but I am on same page.
Can you please provide the procedure to do migration.
regards
bahskar
On Wed, Mar 19, 2014 at 12:38 AM, Kevin Phillips kevin.grenvi...@
gmail.com wrote:
Your database dump appears incomplete. Try dumping with
--max_allowed_packet=512M (large packet to avoid truncation). Check your
1.5.X db and verify the table exists in production and in the backup. Also
verify all your tables are InnoDB instead of MYISAM, you can make manual
modification to the table engine without much recourse.
Take a look at my thread, I just migrated 1.5.2 to 1.7.14 on the same
platform as you.
KP
On Tuesday, March 18, 2014 2:31:44 AM UTC-7, Bhaskar Roy wrote:
Hi Christian,
I am trying migration on new server and not in current production box.
1. On new server I installed ubuntu 12.04/mysql 5.5/RB 1.7.14
1. I took backup of SQL and copied to new server and done rb-site
upgrade.
Copied the databse to new server and tired . I get error messages as
listed above.
regards
Bhaskar
On Thu, Mar 13, 2014 at 12:53 AM, Christian Hammond chi...@chipx86.com
wrote:
Hi,
First, did you back up your database?
Second, can you verify the version of Review Board you've upgraded to,
Re: Issue 3292 in reviewboard: submitting review request ends up with error 500
Comment #2 on issue 3292 by alemar.o...@gmail.com: submitting review request ends up with error 500 http://code.google.com/p/reviewboard/issues/detail?id=3292 Thanks for your comments, I will take it up with our server admin. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Issue 3294 in reviewboard: provide DELETE for http://reviews.example.com/api/session/
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3294 by dam...@pernixdata.com: provide DELETE for http://reviews.example.com/api/session/ http://code.google.com/p/reviewboard/issues/detail?id=3294 What version are you running? 1.7.14 What's the URL of the page containing the problem? DELETE http://reviews.example.com/api/session/ What steps will reproduce the problem? 1. use DELETE method for http://reviews.example.com/api/session/ 2. 3. What is the expected output? What do you see instead? I get: 405 Method Not Allowed this is the documented behavior - http://www.reviewboard.org/docs/manual/dev/webapi/2.0/authenticating/#logging-out But since the defaults are persistent cookies backed by a database, I would like to have a way to delete sessions; proper logout workflow for my use case. What operating system are you using? What browser? CentOS 6.5 / Chrome Please provide any additional information below. here is my workflow: - login and get a cookie from a service accounts (e.g. jenkins) - provide cookie to test job so they can get more information, e.g. - repository - diff - destroy cookie so nobody else can make requests? the problem is that if somebody gets a hold of the rbsessionid, they can use it regardless of me doing best efforts to destroy the cookie. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3294 in reviewboard: provide DELETE for http://reviews.example.com/api/session/
Updates: Status: Confirmed Labels: -Type-Defect Type-Enhancement Milestone-Release2.0.x EasyFix Component-API Comment #1 on issue 3294 by chip...@gmail.com: provide DELETE for http://reviews.example.com/api/session/ http://code.google.com/p/reviewboard/issues/detail?id=3294 Seems like a reasonable addition. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
