Hi Miles, I'm familiar with it, and would also expect it to work, but I was under the impression that they've done more than simply rename the binary, which means there could be some subtle differences in integration that is breaking things. Or, maybe it's a configuration issue, or something else that's wonky.
Looking at that traceback, our installer is simply kicking off a standard 'manage.py syncdb' operation, which tells Django to build the initial database schema. We're not executing any special code on our end, and I believe Django is doing one transaction at a time. I would expect it all to work, particularly since this is done all the time on MySQL. Django massively changed how transactions work in Django 1.6, which the Review Board 2.0 betas/RCs are using. Maybe give RB 2.0 a try, see if it behaves any better? Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Sun, May 4, 2014 at 4:22 PM, Miles Wilton <mewil...@gmail.com> wrote: > It's a drop in replacement for MySQL and haven;t had any issues with any > other app so far. > > The deadlock can only happen with simultaneuos transactions, so presumably > the install script is creating multiple connectons for some reason? > > > > > On Monday, 5 May 2014 00:16:31 UTC+1, Christian Hammond wrote: > >> We have experience using different hosts, though nobody on our end has >> ever tested MariaDB. I'd like to support it, but right now, we can't >> guarantee compatibility. >> >> Christian >> >> >> On Sunday, May 4, 2014, Miles Wilton <mewi...@gmail.com> wrote: >> >>> It's on a different host. It is a MariaDB install... >>> >>> On Saturday, 3 May 2014 23:36:36 UTC+1, Christian Hammond wrote: >>>> >>>> Hi Miles, >>>> >>>> Hmm, that's the first time I've seen this error reported. >>>> >>>> Is there anything special in your MySQL setup? Is it running on the >>>> same machine, or a different one? >>>> >>>> Christian >>>> >>>> -- >>>> Christian Hammond - chi...@chipx86.com >>>> Review Board - http://www.reviewboard.org >>>> Beanbag, Inc. - http://www.beanbaginc.com >>>> >>>> >>>> On Sat, May 3, 2014 at 1:27 AM, Miles Wilton <mewi...@gmail.com> wrote: >>>> >>>>> Trying to do a clean install of the latest reviewboard on debian. >>>>> Followed the instructions and hit this database deadlock error when >>>>> running >>>>> rb-site install: >>>>> >>>>> Have tried multiple times and get the same error. >>>>> >>>>> >>>>> Evolutions in site baseline: localsite_public >>>>> Traceback (most recent call last): >>>>> File "/usr/local/bin/rb-site", line 9, in <module> >>>>> load_entry_point('ReviewBoard==1.7.25', 'console_scripts', >>>>> 'rb-site')() >>>>> File "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.25- >>>>> py2.7.egg/reviewboard/cmdline/rbsite.py", line 2055, in main >>>>> command.run() >>>>> File "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.25- >>>>> py2.7.egg/reviewboard/cmdline/rbsite.py", line 1496, in run >>>>> self.show_install_status() >>>>> File "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.25- >>>>> py2.7.egg/reviewboard/cmdline/rbsite.py", line 1775, in >>>>> show_install_status >>>>> site.sync_database) >>>>> File "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.25- >>>>> py2.7.egg/reviewboard/cmdline/rbsite.py", line 967, in step >>>>> func() >>>>> File "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.25- >>>>> py2.7.egg/reviewboard/cmdline/rbsite.py", line 399, in sync_database >>>>> self.run_manage_command("syncdb", params) >>>>> File "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.25- >>>>> py2.7.egg/reviewboard/cmdline/rbsite.py", line 589, in >>>>> run_manage_command >>>>> execute_manager(reviewboard.settings, [__file__, cmd] + params) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/core/management/__init__.py", line 459, in execute_manager >>>>> utility.execute() >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/core/management/__init__.py", line 382, in execute >>>>> self.fetch_command(subcommand).run_from_argv(self.argv) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/core/management/base.py", line 196, in run_from_argv >>>>> self.execute(*args, **options.__dict__) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/core/management/base.py", line 232, in execute >>>>> output = self.handle(*args, **options) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/core/management/base.py", line 371, in handle >>>>> return self.handle_noargs(**options) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/core/management/commands/syncdb.py", line 110, in >>>>> handle_noargs >>>>> emit_post_sync_signal(created_models, verbosity, interactive, db) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/core/management/sql.py", line 189, in emit_post_sync_signal >>>>> interactive=interactive, db=db) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/dispatch/dispatcher.py", line 172, in send >>>>> response = receiver(signal=self, sender=sender, **named) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/contrib/sites/management.py", line 22, in >>>>> create_default_site >>>>> Site(pk=1, domain="example.com", name="example.com").save(using >>>>> =db) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/contrib/sites/models.py", line 51, in save >>>>> super(Site, self).save(*args, **kwargs) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/db/models/base.py", line 463, in save >>>>> self.save_base(using=using, force_insert=force_insert, >>>>> force_update=force_update) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/db/models/base.py", line 555, in save_base >>>>> transaction.commit_unless_managed(using=using) >>>>> File "/usr/local/lib/python2.7/dist-packages/Django-1.4.12-py2.7. >>>>> egg/django/db/transaction.py", line 135, in commit_unless_managed >>>>> connection.commit_unless_managed() >>>>> File "/usr/local/lib/python2.7/< >>>>> >>>>> -- >>>>> Get the Review Board Power Pack at http://www.reviewboard.org/pow >>>>> erpack/ >>>>> --- >>>>> 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. >>>>> >>>> >>>> >> >> -- >> -- >> Christian Hammond - chi...@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. > -- 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.
