manage.py syncdb - should I run it or not?
I upgraded our RB site 2 weeks ago from 1.0.9 to 1.5.5. As part of the upgrade, I ran $ rb-site upgrade /var/www/reviewboard Everything went smoothly and RB has been running fine for over a week. Then today, several users reported being unable to access RB. They were getting a message saying: The Review Board database schema has changed since your last upgrade. To update your schema, run: $ ./manage.py syncdb That seemed odd because I'm pretty sure 'rb-site upgrade' updated the database schema. If it hadn't, RB would have been pretty non- functional and that wasn't the case. So I searched here and found a message from 2009 where the OP was getting the same message: Database changes The Review Board database schema has changed since your last upgrade. To update your schema, run: $ ./manage.py syncdb Follow any additional instructions it may give you. If, for example, it tells you to perform a schema evolution, run: $ ./manage.py evolve --execute The reply to that was Those instructions should be changed. You need to follow the instructions in the admin guide on upgrading sites using 'rb-site upgrade /path/to/ site' Based on that, I decided to restart RB and that made the problem go away. Or at least it made RB functional again, but I have a nagging feeling the problem could return. To add to my confusion, I see a recent discussion here where 'manage.py syncdb' was the correct action to take, for something called a django evolution. So, 1. If I ran 'rb-site upgrade', do I still need to run 'manage.py syncdb'? 2. Is that still an outdated message that should be changed? 3. Can anyone think of why the site would be running fine for over a week (it gets pretty high traffic) and then suddenly behave in this way? Thanks! -- -- Steve -- 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: manage.py syncdb - should I run it or not?
Hi Steve, That error is, indeed, old and wrong. We've fixed this in 1.6, and it's much more clear now. What probably happened is that, for some reason, there was a temporary communication problem or something with your database. Perhaps it couldn't talk to it, or it reached a max number of connections, or it had some other error. Either way, our checks saw We failed to get this table we were checking for! and made an assumption. A bad assumption. One that 1.6 doesn't make anymore. So you did the right thing with rb-site upgrade. No, those commands it lists shouldn't be used. The assumption in the past is that you'd only see that in development installs, hence the lack of rb-site, and that you'd never see them anymore because the table we try to fetch is from pre-1.0 days. If you upgrade to 1.6, you'll start seeing actual error messages telling you exactly what went wrong. Hopefully you never see them again, but if you do, it'll at least give you an idea what to look for. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Tue, Oct 4, 2011 at 12:43 PM, Steve seide.al...@gmail.com wrote: I upgraded our RB site 2 weeks ago from 1.0.9 to 1.5.5. As part of the upgrade, I ran $ rb-site upgrade /var/www/reviewboard Everything went smoothly and RB has been running fine for over a week. Then today, several users reported being unable to access RB. They were getting a message saying: The Review Board database schema has changed since your last upgrade. To update your schema, run: $ ./manage.py syncdb That seemed odd because I'm pretty sure 'rb-site upgrade' updated the database schema. If it hadn't, RB would have been pretty non- functional and that wasn't the case. So I searched here and found a message from 2009 where the OP was getting the same message: Database changes The Review Board database schema has changed since your last upgrade. To update your schema, run: $ ./manage.py syncdb Follow any additional instructions it may give you. If, for example, it tells you to perform a schema evolution, run: $ ./manage.py evolve --execute The reply to that was Those instructions should be changed. You need to follow the instructions in the admin guide on upgrading sites using 'rb-site upgrade /path/to/ site' Based on that, I decided to restart RB and that made the problem go away. Or at least it made RB functional again, but I have a nagging feeling the problem could return. To add to my confusion, I see a recent discussion here where 'manage.py syncdb' was the correct action to take, for something called a django evolution. So, 1. If I ran 'rb-site upgrade', do I still need to run 'manage.py syncdb'? 2. Is that still an outdated message that should be changed? 3. Can anyone think of why the site would be running fine for over a week (it gets pretty high traffic) and then suddenly behave in this way? Thanks! -- -- Steve -- 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
Re: manage.py syncdb - should I run it or not?
Thanks for the explanation Chris. Very helpful and reassuring - I'll be adding this information to our internal docs. Moving to 1.6 is on my TODO list, but we have some key scripts that use the 1.0 version of the Web API which we need to do something with before we can move to 1.6. Thanks again! -- -- Steve On Oct 4, 12:56 pm, Christian Hammond chip...@chipx86.com wrote: Hi Steve, That error is, indeed, old and wrong. We've fixed this in 1.6, and it's much more clear now. What probably happened is that, for some reason, there was a temporary communication problem or something with your database. Perhaps it couldn't talk to it, or it reached a max number of connections, or it had some other error. Either way, our checks saw We failed to get this table we were checking for! and made an assumption. A bad assumption. One that 1.6 doesn't make anymore. So you did the right thing with rb-site upgrade. No, those commands it lists shouldn't be used. The assumption in the past is that you'd only see that in development installs, hence the lack of rb-site, and that you'd never see them anymore because the table we try to fetch is from pre-1.0 days. If you upgrade to 1.6, you'll start seeing actual error messages telling you exactly what went wrong. Hopefully you never see them again, but if you do, it'll at least give you an idea what to look for. Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com On Tue, Oct 4, 2011 at 12:43 PM, Steve seide.al...@gmail.com wrote: I upgraded our RB site 2 weeks ago from 1.0.9 to 1.5.5. As part of the upgrade, I ran $ rb-site upgrade /var/www/reviewboard Everything went smoothly and RB has been running fine for over a week. Then today, several users reported being unable to access RB. They were getting a message saying: The Review Board database schema has changed since your last upgrade. To update your schema, run: $ ./manage.py syncdb That seemed odd because I'm pretty sure 'rb-site upgrade' updated the database schema. If it hadn't, RB would have been pretty non- functional and that wasn't the case. So I searched here and found a message from 2009 where the OP was getting the same message: Database changes The Review Board database schema has changed since your last upgrade. To update your schema, run: $ ./manage.py syncdb Follow any additional instructions it may give you. If, for example, it tells you to perform a schema evolution, run: $ ./manage.py evolve --execute The reply to that was Those instructions should be changed. You need to follow the instructions in the admin guide on upgrading sites using 'rb-site upgrade /path/to/ site' Based on that, I decided to restart RB and that made the problem go away. Or at least it made RB functional again, but I have a nagging feeling the problem could return. To add to my confusion, I see a recent discussion here where 'manage.py syncdb' was the correct action to take, for something called a django evolution. So, 1. If I ran 'rb-site upgrade', do I still need to run 'manage.py syncdb'? 2. Is that still an outdated message that should be changed? 3. Can anyone think of why the site would be running fine for over a week (it gets pretty high traffic) and then suddenly behave in this way? Thanks! -- -- Steve -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know athttp://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
Re: ./manage.py syncdb
Hi,
This is New installation
1:- rb-site install /var/www/html/crt
Every thing is installed in /var/www/html/crt
2:- After your mail.
'rb-site upgrade [r...@crt html]# rb-site upgrade /var/www/html/crt
Rebuilding directory structure
Updating database
[!] Unable to execute the manager command syncdb: No module named
dummy
[!] Unable to execute the manager command evolve: No module named
dummy
3:- [r...@crt html]# rb-site upgrade /var/www/html/rbd [I tried once
again with different name, then i got the below error].
Creating database ...
[!] Unable to execute the manager command syncdb: No module named
dummy
OK
Performing migrations ...
[!] Unable to execute the manager command evolve: No module named
dummy
OK
Creating administrator account ... Traceback (most recent call last):
File /usr/local/bin/rb-site, line 5, in module
pkg_resources.run_script('ReviewBoard==1.0rc1', 'rb-site')
File build/bdist.linux-x86_64/egg/pkg_resources.py, line 448, in
run_script
File build/bdist.linux-x86_64/egg/pkg_resources.py, line 1166, in
run_script
File /usr/local/lib/python2.6/site-packages/ReviewBoard-1.0rc1-
py2.6.egg/EGG-INFO/scripts/rb-site, line 1446, in module
main(sys.argv[1:])
File /usr/local/lib/python2.6/site-packages/ReviewBoard-1.0rc1-
py2.6.egg/EGG-INFO/scripts/rb-site, line 1441, in main
command.run()
File /usr/local/lib/python2.6/site-packages/ReviewBoard-1.0rc1-
py2.6.egg/EGG-INFO/scripts/rb-site, line 1049, in run
self.show_install_status()
File /usr/local/lib/python2.6/site-packages/ReviewBoard-1.0rc1-
py2.6.egg/EGG-INFO/scripts/rb-site, line 1304, in show_install_status
site.create_admin_user)
File /usr/local/lib/python2.6/site-packages/ReviewBoard-1.0rc1-
py2.6.egg/EGG-INFO/scripts/rb-site, line 630, in step
func()
File /usr/local/lib/python2.6/site-packages/ReviewBoard-1.0rc1-
py2.6.egg/EGG-INFO/scripts/rb-site, line 325, in create_admin_user
self.admin_password)
File /usr/local/lib/python2.6/site-packages/Django-1.0.2_final-
py2.6.egg/django/contrib/auth/models.py, line 118, in
create_superuser
u = self.create_user(username, email, password)
File /usr/local/lib/python2.6/site-packages/Django-1.0.2_final-
py2.6.egg/django/contrib/auth/models.py, line 114, in create_user
user.save()
File /usr/local/lib/python2.6/site-packages/Django-1.0.2_final-
py2.6.egg/django/db/models/base.py, line 311, in save
self.save_base(force_insert=force_insert,
force_update=force_update)
File /usr/local/lib/python2.6/site-packages/Django-1.0.2_final-
py2.6.egg/django/db/models/base.py, line 383, in save_base
result = manager._insert(values, return_id=update_pk)
File /usr/local/lib/python2.6/site-packages/Django-1.0.2_final-
py2.6.egg/django/db/models/manager.py, line 138, in _insert
return insert_query(self.model, values, **kwargs)
File /usr/local/lib/python2.6/site-packages/Django-1.0.2_final-
py2.6.egg/django/db/models/query.py, line 894, in insert_query
return query.execute_sql(return_id)
File /usr/local/lib/python2.6/site-packages/Django-1.0.2_final-
py2.6.egg/django/db/models/sql/subqueries.py, line 309, in
execute_sql
cursor = super(InsertQuery, self).execute_sql(None)
File /usr/local/lib/python2.6/site-packages/Django-1.0.2_final-
py2.6.egg/django/db/models/sql/query.py, line 1724, in execute_sql
sql, params = self.as_sql()
File /usr/local/lib/python2.6/site-packages/Django-1.0.2_final-
py2.6.egg/django/db/models/sql/subqueries.py, line 303, in as_sql
result = ['INSERT INTO %s' % qn(self.model._meta.db_table)]
File /usr/local/lib/python2.6/site-packages/Django-1.0.2_final-
py2.6.egg/django/db/backends/dummy/base.py, line 15, in complain
raise ImproperlyConfigured, You haven't set the DATABASE_ENGINE
setting yet.
django.core.exceptions.ImproperlyConfigured: You haven't set the
DATABASE_ENGINE setting yet.
On May 19, 10:36 am, Christian Hammond chip...@chipx86.com wrote:
Those instructions should be changed. You need to follow the instructions in
the admin guide on upgrading sites using 'rb-site upgrade /path/to/site'
Is this a new install? What changed on the server before this happened?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.review-board.org
VMware, Inc. -http://www.vmware.com
On Mon, May 18, 2009 at 10:26 PM, myhuna myh...@gmail.com wrote:
Hi,
When i am typing the ipadress on the browser i am getting the below
error.
Database changes
The Review Board database schema has changed since your last upgrade.
To update your schema, run:
$ ./manage.py syncdb
Follow any additional instructions it may give you. If, for example,
it tells you to perform a schema evolution, run:
$ ./manage.py evolve --execute
[r...@crt reviewboard]# vi manage.py
[r...@crt reviewboard]# ./manage.py
Unable to read settings_local.py.
Please seehttp://www.review-board.org/docs/manual/dev/admin/
for help setting up Review
Re: ./manage.py syncdb
schema, run: $ ./manage.py syncdb Follow any additional instructions it may give you. If, for example, it tells you to perform a schema evolution, run: $ ./manage.py evolve --execute [r...@crt reviewboard]# vi manage.py [r...@crt reviewboard]# ./manage.py Unable to read settings_local.py. Please seehttp://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# vi manage.py [r...@crt reviewboard]# python manage.py evolve --execute Unable to read settings_local.py. Please seehttp://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# pwd /usr/local/lib/python2.6/site-packages/ReviewBoard-1.0rc1-py2.6.egg/ reviewboard [r...@crt reviewboard]# python manage.py evolve --execute Unable to read settings_local.py. Please seehttp://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# ./manage.py syncdb Unable to read settings_local.py. Please seehttp://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com 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 -~--~~~~--~~--~--~---
./manage.py syncdb
Hi, When i am typing the ipadress on the browser i am getting the below error. Database changes The Review Board database schema has changed since your last upgrade. To update your schema, run: $ ./manage.py syncdb Follow any additional instructions it may give you. If, for example, it tells you to perform a schema evolution, run: $ ./manage.py evolve --execute [r...@crt reviewboard]# vi manage.py [r...@crt reviewboard]# ./manage.py Unable to read settings_local.py. Please see http://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# vi manage.py [r...@crt reviewboard]# python manage.py evolve --execute Unable to read settings_local.py. Please see http://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# pwd /usr/local/lib/python2.6/site-packages/ReviewBoard-1.0rc1-py2.6.egg/ reviewboard [r...@crt reviewboard]# python manage.py evolve --execute Unable to read settings_local.py. Please see http://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# ./manage.py syncdb Unable to read settings_local.py. Please see http://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com 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: ./manage.py syncdb
Those instructions should be changed. You need to follow the instructions in the admin guide on upgrading sites using 'rb-site upgrade /path/to/site' Is this a new install? What changed on the server before this happened? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.review-board.org VMware, Inc. - http://www.vmware.com On Mon, May 18, 2009 at 10:26 PM, myhuna myh...@gmail.com wrote: Hi, When i am typing the ipadress on the browser i am getting the below error. Database changes The Review Board database schema has changed since your last upgrade. To update your schema, run: $ ./manage.py syncdb Follow any additional instructions it may give you. If, for example, it tells you to perform a schema evolution, run: $ ./manage.py evolve --execute [r...@crt reviewboard]# vi manage.py [r...@crt reviewboard]# ./manage.py Unable to read settings_local.py. Please see http://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# vi manage.py [r...@crt reviewboard]# python manage.py evolve --execute Unable to read settings_local.py. Please see http://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# pwd /usr/local/lib/python2.6/site-packages/ReviewBoard-1.0rc1-py2.6.egg/ reviewboard [r...@crt reviewboard]# python manage.py evolve --execute Unable to read settings_local.py. Please see http://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# ./manage.py syncdb Unable to read settings_local.py. Please see http://www.review-board.org/docs/manual/dev/admin/ for help setting up Review Board. [r...@crt reviewboard]# --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com 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 -~--~~~~--~~--~--~---
