Hi Christian,
Thank you for your replies.
In turned out this was a configuration issue with our database server. The
reason I hadn't experienced it with other apps is that it appears the
install script disconnects and reconnects to the mysql (mariadb) server
multiple times during the install
Hi Miles,
Glad to hear that! This would be useful for us to document. Can you tell me
what you changed?
Christian
On Tuesday, May 6, 2014, Miles Wilton mewil...@gmail.com wrote:
Hi Christian,
Thank you for your replies.
In turned out this was a configuration issue with our database
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?
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 mewil...@gmail.com wrote:
It's on a different host. It is a MariaDB install...
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
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
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):
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 - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. -
