Hi guys, I need to test the upgrade to latest Bitbucket Server version.
Firstly I'm copying my files/db to new instance and trying to get it up and running.
I've did full copy of installation/home directories using rsync. Also had my MySQL db back using mysqldump utility.
not sure if that could be a problem, but anyway, my MySQL db are versioning like this:
* Source MySQL version: 5.6.20
* Target MySQL version: 5.6.40
I did changed BITBUCKET_HOME variable, JRE variable. Changed db connection properties in bitbucket.properties to migrated db.
And having there errors:
```
2018-05-07 00:38:06,433 INFO [spring-startup] c.a.s.i.server.BuildInfoLogger Starting Bitbucket 4.13.0 (5467926 built on Wed Jan 18 20:34:39 PST 2017)
2018-05-07 00:38:06,437 INFO [spring-startup] c.a.s.i.server.BuildInfoLogger JVM: Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 1.8.0_102-b14
2018-05-07 00:38:06,449 INFO [spring-startup] c.a.s.internal.home.HomeLockAcquirer Successfully acquired lock on home directory /data/bitbucket-data
2018-05-07 00:38:09,153 ERROR [spring-startup] liquibase Change Set liquibase/r3_4/bootstrap-upgrade.xml::STASHDEV-7910-1::jhinch failed. Error: Error executing SQL CREATE TABLE `stash413db`.`app_property` (`prop_key` VARCHAR(50) NOT NULL, `prop_value`
VARCHAR(2000) NOT NULL, CONSTRAINT `PK_APP_PROPERTY` PRIMARY KEY (`prop_key`)): Table 'app_property' already exists
liquibase.exception.DatabaseException: Error executing SQL CREATE TABLE `stash413db`.`app_property` (`prop_key` VARCHAR(50) NOT NULL, `prop_value` VARCHAR(2000) NOT NULL, CONSTRAINT `PK_APP_PROPERTY` PRIMARY KEY (`prop_key`)): Table 'app_property' already
exists
at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:62) ~[liquibase-core-2.0.5.jar:na]
at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:104) ~[liquibase-core-2.0.5.jar:na]
at liquibase.database.AbstractDatabase.execute(AbstractDatabase.java:1091) ~[liquibase-core-2.0.5.jar:na]
at liquibase.database.AbstractDatabase.executeStatements(AbstractDatabase.java:1075) ~[liquibase-core-2.0.5.jar:na]
at liquibase.changelog.ChangeSet.execute(ChangeSet.java:317) ~[liquibase-core-2.0.5.jar:na]
at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:27) [liquibase-core-2.0.5.jar:na]
at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:58) [liquibase-core-2.0.5.jar:na]
at liquibase.Liquibase.update(Liquibase.java:114) [liquibase-core-2.0.5.jar:na]
at liquibase.integration.spring.SpringLiquibase.performUpdate(SpringLiquibase.java:262) [liquibase-core-2.0.5.jar:na]
at liquibase.database.DefaultingSchemaLiquibase.afterPropertiesSet(DefaultingSchemaLiquibase.java:44) [bitbucket-dao-impl-4.13.0.jar:na]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:866) [spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:542) [spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
at javax.servlet.GenericServlet.init(GenericServlet.java:158) [servlet-api.jar:3.1.FR]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_102]
... 77 frames trimmed
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'app_property' already exists
```
I also tried running new install binary for 4.13.0, and I got the same errors.
I had copied from prod instance. Basically I did very short stop of instance only to copy db files, it's about 1G, around 15 seconds or so. But files I did copy over running instance, I suspect here could be a problem.
Ivan.
Hey Ivan
Here is a good document about how to make the backups which you can use to migrate.
Try to make sure that the database and the home directory are in a consistent state.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.