Re: problem upgrading 1.5.6 to 1.6(.1)
Excellent! Glad it's working :) Christian On Monday, September 12, 2011, M. Exner wrote: > Problem solved! > > I switched all existing reviewboard tables to storage engine InnoDB > and the upgrade went fine. > Can only imagine the problem was the engine mix of old tables (MyISAM) > and newly created tables (InnoDB). > > Thanks for your help and keep up the great work! > > Regards, > Martin > > -- > 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 > -- -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: problem upgrading 1.5.6 to 1.6(.1)
Problem solved! I switched all existing reviewboard tables to storage engine InnoDB and the upgrade went fine. Can only imagine the problem was the engine mix of old tables (MyISAM) and newly created tables (InnoDB). Thanks for your help and keep up the great work! Regards, Martin -- 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: problem upgrading 1.5.6 to 1.6(.1)
The windows server runs MySQL v5.5.10 using InnoDB storage engine.
But now that I looked at the tables in the windows server's
reviewboard db I see they're using MyISAM storage engine.
The test server runs MySQL 5.1.54-1ubuntu4 with storage engine unset,
so defaulting to MyISAM.
Here the tables also use MyISAM storage so I think this might be the
problem.
I'll check if I may set the default storage engine on the windows
server to MyISAM and retry the upgrade.
On 12 Sep., 12:57, Christian Hammond wrote:
> Hi Martin,
>
> The "#sql-" tables are generated internally by MySQL. Do you know if you're
> using InnoDB or MyISAM on the database?
>
> From a Google search, it seems that there may be several causes for this.
> It's basically a very misleading error message, and seems to vary on
> configuration.
>
> What version of MySQL are you running? And how about the test server?
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vmware.com
>
>
>
>
>
>
>
> On Mon, Sep 12, 2011 at 1:56 AM, M. Exner wrote:
> > We've been using reviewboard for a while now and had no problems with
> > upgrading several times.
> > We're running it on a windows server using apache 2.2 and mysql 5.5.
> > But now I try to upgrade our 1.5.6 installation to 1.6 I get several
> > database issues.
>
> > 'rb-site upgrade reviewboard' gives the following:
>
> > Rebuilding directory structure
> > Upgrading site settings_local.py
> > Updating database. This may take a while.
> > C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\db
> > \__init__.py:19: DeprecationWarning: settings.DATABASE_* is
> > deprecated; use settings.DATABASES instead.
> > DeprecationWarning
> > Creating tables ...
> > Creating table accounts_localsiteprofile
> > Traceback (most recent call last):
> > File "C:\Python27\Scripts\rb-site-script.py", line 8, in
> > load_entry_point('ReviewBoard==1.6', 'console_scripts', 'rb-site')
> > ()
> > File "C:\Python27\lib\site-packages\reviewboard-1.6-py2.7.egg
> > \reviewboard\cmdline\rbsite.py", line 1747, in main
> > command.run()
> > File "C:\Python27\lib\site-packages\reviewboard-1.6-py2.7.egg
> > \reviewboard\cmdline\rbsite.py", line 1644, in run
> > site.sync_database()
> > File "C:\Python27\lib\site-packages\reviewboard-1.6-py2.7.egg
> > \reviewboard\cmdline\rbsite.py", line 346, in sync_database
> > self.run_manage_command("syncdb", params)
> > File "C:\Python27\lib\site-packages\reviewboard-1.6-py2.7.egg
> > \reviewboard\cmdline\rbsite.py", line 472, in run_manage_command
> > execute_manager(reviewboard.settings, [__file__, cmd] + params)
> > File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> > \management\__init__.py", line 438, in execute_manager
> > utility.execute()
> > File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> > \management\__init__.py", line 379, in execute
> > self.fetch_command(subcommand).run_from_argv(self.argv)
> > File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> > \management\base.py", line 191, in run_from_argv
> > self.execute(*args, **options.__dict__)
> > File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> > \management\base.py", line 220, in execute
> > output = self.handle(*args, **options)
> > File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> > \management\base.py", line 351, in handle
> > return self.handle_noargs(**options)
> > File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> > \management\commands\syncdb.py", line 101, in handle_noargs
> > cursor.execute(statement)
> > File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\db
> > \backends\mysql\base.py", line 86, in execute
> > return self.cursor.execute(query, args)
> > File "C:\Python27\lib\site-packages\MySQLdb\cursors.py", line 174,
> > in execute
> > self.errorhandler(self, exc, value)
> > File "C:\Python27\lib\site-packages\MySQLdb\connections.py", line
> > 36, in defaulterrorhandler
> > raise errorclass, errorvalue
> > _mysql_exceptions.OperationalError: (1005, "Can't create table
> > 'reviewboard.#sql-680_1' (errno: 150)")
>
> > I've been able to go back to 1.5.6 again and used the site and
> > database backups, so I'm fine for the moment.
> > But we really would like to use 1.6 for all the great new features.
> > Same problem occurs if I try to update to 1.6.1 release.
>
> > On my test sytem (Ubuntu 11.04) there was no problem with the upgrade,
> > but the steps were 1.5.6 -> 1.6RC1 -> 1.6RC2 -> 1.6.
>
> > Any advise would be appreciated!
>
> > Regards,
> > Martin
>
> > --
> > 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+unsub
Re: problem upgrading 1.5.6 to 1.6(.1)
Hi Martin,
The "#sql-" tables are generated internally by MySQL. Do you know if you're
using InnoDB or MyISAM on the database?
>From a Google search, it seems that there may be several causes for this.
It's basically a very misleading error message, and seems to vary on
configuration.
What version of MySQL are you running? And how about the test server?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Mon, Sep 12, 2011 at 1:56 AM, M. Exner wrote:
> We've been using reviewboard for a while now and had no problems with
> upgrading several times.
> We're running it on a windows server using apache 2.2 and mysql 5.5.
> But now I try to upgrade our 1.5.6 installation to 1.6 I get several
> database issues.
>
> 'rb-site upgrade reviewboard' gives the following:
>
> Rebuilding directory structure
> Upgrading site settings_local.py
> Updating database. This may take a while.
> C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\db
> \__init__.py:19: DeprecationWarning: settings.DATABASE_* is
> deprecated; use settings.DATABASES instead.
> DeprecationWarning
> Creating tables ...
> Creating table accounts_localsiteprofile
> Traceback (most recent call last):
> File "C:\Python27\Scripts\rb-site-script.py", line 8, in
>load_entry_point('ReviewBoard==1.6', 'console_scripts', 'rb-site')
> ()
> File "C:\Python27\lib\site-packages\reviewboard-1.6-py2.7.egg
> \reviewboard\cmdline\rbsite.py", line 1747, in main
>command.run()
> File "C:\Python27\lib\site-packages\reviewboard-1.6-py2.7.egg
> \reviewboard\cmdline\rbsite.py", line 1644, in run
>site.sync_database()
> File "C:\Python27\lib\site-packages\reviewboard-1.6-py2.7.egg
> \reviewboard\cmdline\rbsite.py", line 346, in sync_database
>self.run_manage_command("syncdb", params)
> File "C:\Python27\lib\site-packages\reviewboard-1.6-py2.7.egg
> \reviewboard\cmdline\rbsite.py", line 472, in run_manage_command
>execute_manager(reviewboard.settings, [__file__, cmd] + params)
> File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> \management\__init__.py", line 438, in execute_manager
>utility.execute()
> File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> \management\__init__.py", line 379, in execute
>self.fetch_command(subcommand).run_from_argv(self.argv)
> File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> \management\base.py", line 191, in run_from_argv
>self.execute(*args, **options.__dict__)
> File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> \management\base.py", line 220, in execute
>output = self.handle(*args, **options)
> File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> \management\base.py", line 351, in handle
>return self.handle_noargs(**options)
> File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\core
> \management\commands\syncdb.py", line 101, in handle_noargs
>cursor.execute(statement)
> File "C:\Python27\lib\site-packages\django-1.3-py2.7.egg\django\db
> \backends\mysql\base.py", line 86, in execute
>return self.cursor.execute(query, args)
> File "C:\Python27\lib\site-packages\MySQLdb\cursors.py", line 174,
> in execute
>self.errorhandler(self, exc, value)
> File "C:\Python27\lib\site-packages\MySQLdb\connections.py", line
> 36, in defaulterrorhandler
>raise errorclass, errorvalue
> _mysql_exceptions.OperationalError: (1005, "Can't create table
> 'reviewboard.#sql-680_1' (errno: 150)")
>
> I've been able to go back to 1.5.6 again and used the site and
> database backups, so I'm fine for the moment.
> But we really would like to use 1.6 for all the great new features.
> Same problem occurs if I try to update to 1.6.1 release.
>
> On my test sytem (Ubuntu 11.04) there was no problem with the upgrade,
> but the steps were 1.5.6 -> 1.6RC1 -> 1.6RC2 -> 1.6.
>
> Any advise would be appreciated!
>
> Regards,
> Martin
>
> --
> 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
