Thanks, Tim. Unfortunately, that did not work. I've copied the logs below.
I am copying the database from production to a test environment, but both
VMs are running Ubuntu 16.04 and PostgreSQL 9.5.
(As a sanity-check, I restored from backup and was able to update using the
regular DSpace 5.5 without issues. I have also previously managed to update
to DSpace 6.0.)
dspace@dspace:~$ /dspace/bin/dspace database repair
Database URL: jdbc:postgresql://localhost:5432/dspace
Attempting to repair any previously failed migrations via FlywayDB...
(Check logs for details)
Done.
dspace@dspace:~$ less /dspace/log/dspace.log.2016-08-31
2016-08-31 07:29:15,470 INFO com.mchange.v2.log.MLog @ MLog clients using
log4j logging.
2016-08-31 07:29:15,697 INFO com.mchange.v2.c3p0.C3P0Registry @
Initializing c3p0-0.9.1.2 [built 21-May-2007 15:04:56; debug? true; trace:
10]
2016-08-31 07:29:16,442 INFO org.hibernate.annotations.common.Version @
HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
2016-08-31 07:29:16,460 INFO org.hibernate.Version @ HHH000412: Hibernate
Core {4.1.8.Final}
2016-08-31 07:29:16,468 INFO org.hibernate.cfg.Environment @ HHH000205:
Loaded properties from resource hibernate.properties:
{hibernate.initialPoolSize=1,
hibernate.dialect=org.hibernate.dialect.PostgreSQLDialect,
hibernate.maxPoolSize=10, hibernate.minPoolSize=4,
hibernate.loginTimeout=300, hibernate.acquireIncrement=3,
hibernate.idleConnectionTestPeriod=3000,
hibernate.maxIdleTime=100, hibernate.maxStatements=100,
hibernate.bytecode.use_reflection_optimizer=false}
2016-08-31 07:29:16,469 INFO org.hibernate.cfg.Environment @ HHH000021:
Bytecode provider name : javassist
2016-08-31 07:29:16,544 INFO org.hibernate.cfg.Configuration @ HHH000044:
Configuring from URL: jar:file:/dspace/lib/dspace-cris-api-CRIS-5.5.0.jar!/
hibernate/hibernate-cris.cfg.xml
2016-08-31 07:29:16,711 INFO org.hibernate.cfg.Configuration @ HHH000041:
Configured SessionFactory: null
2016-08-31 07:29:17,956 INFO
com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource
@ Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [
acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay ->
1000, autoCommitOnClose -> false, automaticTestTable -> null,
breakAfterAcquireFailure -> false, checkoutTimeout -> 0,
connectionCustomizerClassName -> null, connectionTesterClassName ->
com.mchange.v2.c3p0.impl.DefaultConnectionTester, dataSourceName ->
z8kfsx9i1pw7mk1rkhgih|10ded6a9, debugUnreturnedConnectionStackTraces ->
false, description -> null, driverClass -> org.postgresql.Driver,
factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false,
identityToken -> z8kfsx9i1pw7mk1rkhgih|10ded6a9, idleConnectionTestPeriod
-> 3000, initialPoolSize -> 1, jdbcUrl ->
jdbc:postgresql://localhost:5432/dspace,
maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 100,
maxIdleTimeExcessConnections -> 0, maxPoolSize -> 10, maxStatements -> 100,
maxStatementsPerConnection -> 0, minPoolSize -> 4, numHelperThreads -> 3,
numThreadsAwaitingCheckoutDefaultUser -> 0, preferredTestQuery -> null,
properties -> {user=******, password=******}, propertyCycle -> 0,
testConnectionOnCheckin -> false, testConnectionOnCheckout -> false,
unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> false
]
2016-08-31 07:29:18,484 INFO org.hibernate.dialect.Dialect @ HHH000400:
Using dialect: org.hibernate.dialect.PostgreSQLDialect
2016-08-31 07:29:18,516 INFO
org.hibernate.engine.jdbc.internal.LobCreatorBuilder
@ HHH000424: Disabling contextual LOB creation as createClob() method threw
error : java.lang.reflect.InvocationTargetException
2016-08-31 07:29:18,548 INFO
org.hibernate.engine.transaction.internal.TransactionFactoryInitiator
@ HHH000399: Using default transaction strategy (direct JDBC transactions)
2016-08-31 07:29:18,554 INFO
org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory
@ HHH000397: Using ASTQueryTranslatorFactory
2016-08-31 07:29:18,636 WARN net.sf.ehcache.config.ConfigurationFactory @
No configuration found. Configuring ehcache from ehcache-failsafe.xml
found in the classpath: jar:file:/dspace/lib/ehcache-
core-2.4.3.jar!/ehcache-failsafe.xml
2016-08-31 07:29:18,793 INFO org.hibernate.cache.spi.UpdateTimestampsCache
@ HHH000250: Starting update timestamps cache at region:
org.hibernate.cache.spi.UpdateTimestampsCache
2016-08-31 07:29:18,796 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [org.hibernate.cache.spi.UpdateTimestampsCache]; using defaults.
2016-08-31 07:29:18,844 INFO org.hibernate.cache.internal.StandardQueryCache
@ HHH000248: Starting query cache at region: org.hibernate.cache.internal.
StandardQueryCache
2016-08-31 07:29:18,846 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [org.hibernate.cache.internal.StandardQueryCache]; using defaults.
2016-08-31 07:29:19,042 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [it.cilea.osd.jdyna.model.ATypeNestedObject]; using defaults.
2016-08-31 07:29:19,057 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [it.cilea.osd.jdyna.model.AWidget]; using defaults.
2016-08-31 07:29:19,065 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [it.cilea.osd.jdyna.model.Containable]; using defaults.
2016-08-31 07:29:19,119 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [it.cilea.osd.jdyna.web.Tab]; using defaults.
2016-08-31 07:29:19,133 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [it.cilea.osd.jdyna.web.Box]; using defaults.
2016-08-31 07:29:19,160 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [it.cilea.osd.jdyna.model.PropertiesDefinition]; using defaults.
2016-08-31 07:29:19,521 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [org.dspace.app.cris.model.jdyna.BoxResearcherPage.mask]; using
defaults.
2016-08-31 07:29:19,626 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [org.dspace.app.cris.model.jdyna.ProjectTypeNestedObject.mask]; using
defaults.
2016-08-31 07:29:19,627 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [org.dspace.app.cris.model.jdyna.RPTypeNestedObject.mask]; using
defaults.
2016-08-31 07:29:19,629 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [org.dspace.app.cris.model.jdyna.OUTypeNestedObject.mask]; using
defaults.
2016-08-31 07:29:19,630 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [org.dspace.app.cris.model.jdyna.TabProject.mask]; using defaults.
2016-08-31 07:29:19,631 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [org.dspace.app.cris.model.jdyna.BoxOrganizationUnit.mask]; using
defaults.
...
2016-08-31 07:29:19,648 WARN
org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory
@ HHH020003: Could not find a specific ehcache configuration for cache
named [org.dspace.app.cris.model.jdyna.BoxProject.mask]; using defaults.
2016-08-31 07:29:20,976 INFO net.sf.ehcache.util.UpdateChecker @ New
update(s) found: 2.4.7 [http://www.terracotta.org/
confluence/display/release/Release+Notes+Ehcache+Core+2.4]. Please check
http://ehcache.org for the latest version.
2016-08-31 07:29:25,496 WARN org.hibernate.hql.internal.ast.HqlSqlWalker @
[DEPRECATION] Encountered positional parameter near line 1, column 92.
Positional parameter are considered deprecated; use named parameters or
JPA-style positional parameters instead.
2016-08-31 07:29:25,498 WARN org.hibernate.hql.internal.ast.HqlSqlWalker @
[DEPRECATION] Encountered positional parameter near line 1, column 108.
Positional parameter are considered deprecated; use named parameters or
JPA-style positional parameters instead.
...
2016-08-31 07:29:26,483 WARN org.hibernate.hql.internal.ast.HqlSqlWalker @
[DEPRECATION] Encountered positional parameter near line 1, column 103.
Positional parameter are considered deprecated; use named parameters or
JPA-style positional parameters instead.
2016-08-31 07:29:27,225 WARN net.sf.ehcache.config.ConfigurationFactory @
No configuration found. Configuring ehcache from ehcache-failsafe.xml
found in the classpath: jar:file:/dspace/lib/ehcache-
core-2.4.3.jar!/ehcache-failsafe.xml
2016-08-31 07:29:27,239 WARN net.sf.ehcache.CacheManager @ Creating a new
instance of CacheManager using the diskStorePath "/tmp" which is already
used by an existing CacheManager.
The source of the configuration was net.sf.ehcache.config.
generator.ConfigurationSource$DefaultConfigurationSource@27dbaa33.
The diskStore path for this CacheManager will be set to
/tmp/ehcache_auto_created_1472621367239.
To avoid this warning consider using the CacheManager factory methods to
create a singleton CacheManager or specifying a separate ehcache
configuration (ehcache.xml) for each CacheManager instance.
2016-08-31 07:29:27,241 WARN net.sf.ehcache.Cache @ An API change between
ehcache-1.1 and ehcache-1.2 results in the persistence path being set to
/tmp when the ehcache-1.1 constructor is used. Please change to the 1.2
constructor.
2016-08-31 07:29:27,242 WARN net.sf.ehcache.Cache @ An API change between
ehcache-1.1 and ehcache-1.2 results in the persistence path being set to
/tmp when the ehcache-1.1 constructor is used. Please change to the 1.2
constructor.
2016-08-31 07:29:27,242 WARN net.sf.ehcache.Cache @ An API change between
ehcache-1.1 and ehcache-1.2 results in the persistence path being set to
/tmp when the ehcache-1.1 constructor is used. Please change to the 1.2
constructor.
2016-08-31 07:29:27,242 WARN net.sf.ehcache.Cache @ An API change between
ehcache-1.1 and ehcache-1.2 results in the persistence path being set to
/tmp when the ehcache-1.1 constructor is used. Please change to the 1.2
constructor.
2016-08-31 07:29:28,501 WARN net.sf.ehcache.CacheManager @ Creating a new
instance of CacheManager using the diskStorePath "/tmp" which is already
used by an existing CacheManager.
The source of the configuration was net.sf.ehcache.config.
generator.ConfigurationSource$InputStreamConfigurationSource@485c84d7.
The diskStore path for this CacheManager will be set to
/tmp/ehcache_auto_created_1472621368501.
To avoid this warning consider using the CacheManager factory methods to
create a singleton CacheManager or specifying a separate ehcache
configuration (ehcache.xml) for each CacheManager instance.
2016-08-31 07:29:29,028 INFO net.sf.ehcache.util.UpdateChecker @ New
update(s) found: 2.4.7 [http://www.terracotta.org/
confluence/display/release/Release+Notes+Ehcache+Core+2.4]. Please check
http://ehcache.org for the latest version.
2016-08-31 07:29:30,571 INFO org.dspace.storage.rdbms.DatabaseUtils @
Loading Flyway DB migrations from: filesystem:/dspace/etc/postgres,
classpath:org.dspace.storage.rdbms.sqlmigration.postgres,
classpath:org.dspace.storage.rdbms.migration
2016-08-31 07:29:30,757 INFO
org.flywaydb.core.internal.metadatatable.MetaDataTableImpl
@ Repair of metadata table "public"."schema_version" not necessary. No
failed migration detected.
2016-08-31 07:29:30,851 INFO org.dspace.storage.rdbms.DatabaseManager @
DBMS is 'PostgreSQL'
2016-08-31 07:29:30,851 INFO org.dspace.storage.rdbms.DatabaseManager @
DBMS driver version is '9.5.4'
2016-08-31 07:29:30,960 INFO org.dspace.storage.rdbms.DatabaseUtils @
Pending DSpace database schema migrations:
2016-08-31 07:29:30,960 INFO org.dspace.storage.rdbms.DatabaseUtils @
5.3.0.0 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
2016-08-31 07:29:30,960 INFO org.dspace.storage.rdbms.DatabaseUtils @
5.3.0.1 FIX-SNAPSHOT-DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
2016-08-31 07:29:30,960 INFO org.dspace.storage.rdbms.DatabaseUtils @
5.3.0.2 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
2016-08-31 07:29:30,960 INFO org.dspace.storage.rdbms.DatabaseUtils @
5.3.0.3 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
2016-08-31 07:29:30,960 INFO org.dspace.storage.rdbms.DatabaseUtils @
5.3.0.4 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
2016-08-31 07:29:30,960 INFO org.dspace.storage.rdbms.DatabaseUtils @
5.3.0.5 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
2016-08-31 07:29:30,960 INFO org.dspace.storage.rdbms.DatabaseUtils @
5.3.0.6 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
2016-08-31 07:29:30,964 INFO org.dspace.storage.rdbms.DatabaseUtils @
5.3.1.0 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
2016-08-31 07:29:30,964 INFO org.dspace.storage.rdbms.DatabaseUtils @
5.3.1.1 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
2016-08-31 07:29:30,964 INFO org.dspace.storage.rdbms.DatabaseUtils @
5.4.0.0 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
2016-08-31 07:29:30,964 INFO org.dspace.storage.rdbms.DatabaseUtils @
5.4.0.1 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
2016-08-31 07:29:31,006 INFO org.flywaydb.core.internal.command.DbValidate
@ Validated 32 migrations (execution time 00:00.038s)
2016-08-31 07:29:31,008 ERROR org.dspace.storage.rdbms.DatabaseManager @
SQL getDataSource Error -
java.sql.SQLException: Flyway migration error occurred
at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(
DatabaseUtils.java:483)
at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(
DatabaseUtils.java:391)
at org.dspace.storage.rdbms.DatabaseManager.initialize(
DatabaseManager.java:1378)
at org.dspace.storage.rdbms.DatabaseManager.getDataSource(
DatabaseManager.java:653)
at org.dspace.storage.rdbms.DatabaseManager.getConnection(
DatabaseManager.java:632)
at org.dspace.core.Context.init(Context.java:145)
at org.dspace.core.Context.<init>(Context.java:119)
at org.dspace.storage.rdbms.DatabaseLegacyReindexer.reindex(
DatabaseLegacyReindexer.java:52)
at org.dspace.storage.rdbms.DatabaseLegacyReindexer.afterRepair(
DatabaseLegacyReindexer.java:144)
at org.flywaydb.core.internal.command.DbRepair$3.
doInTransaction(DbRepair.java:114)
at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.
execute(TransactionTemplate.java:72)
at org.flywaydb.core.internal.command.DbRepair.repair(
DbRepair.java:111)
at org.flywaydb.core.Flyway$6.execute(Flyway.java:994)
at org.flywaydb.core.Flyway$6.execute(Flyway.java:990)
at org.flywaydb.core.Flyway.execute(Flyway.java:1171)
at org.flywaydb.core.Flyway.repair(Flyway.java:990)
at org.dspace.storage.rdbms.DatabaseUtils.main(
DatabaseUtils.java:217)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.dspace.app.launcher.ScriptLauncher.runOneCommand(
ScriptLauncher.java:226)
at org.dspace.app.launcher.ScriptLauncher.main(
ScriptLauncher.java:78)
Caused by: org.flywaydb.core.api.FlywayException: Validate failed. Found
differences between applied migrations and available migrations: Migration
on the classpath has not been applied to database: 3.2.1.0
at org.flywaydb.core.Flyway.doValidate(Flyway.java:912)
at org.flywaydb.core.Flyway.access$400(Flyway.java:50)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:817)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:811)
at org.flywaydb.core.Flyway.execute(Flyway.java:1171)
at org.flywaydb.core.Flyway.migrate(Flyway.java:811)
at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(
DatabaseUtils.java:472)
... 22 more
2016-08-31 07:29:31,012 ERROR org.dspace.storage.rdbms.DatabaseLegacyReindexer
@ Error attempting to reindex all contents for search/browse. You may need
to manually reindex Lucene or DBMS
java.lang.IllegalStateException: Flyway migration error occurred
at org.dspace.storage.rdbms.DatabaseManager.getDataSource(
DatabaseManager.java:658)
at org.dspace.storage.rdbms.DatabaseManager.getConnection(
DatabaseManager.java:632)
at org.dspace.core.Context.init(Context.java:145)
at org.dspace.core.Context.<init>(Context.java:119)
at org.dspace.storage.rdbms.DatabaseLegacyReindexer.reindex(
DatabaseLegacyReindexer.java:52)
at org.dspace.storage.rdbms.DatabaseLegacyReindexer.afterRepair(
DatabaseLegacyReindexer.java:144)
at org.flywaydb.core.internal.command.DbRepair$3.
doInTransaction(DbRepair.java:114)
at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.
execute(TransactionTemplate.java:72)
at org.flywaydb.core.internal.command.DbRepair.repair(
DbRepair.java:111)
at org.flywaydb.core.Flyway$6.execute(Flyway.java:994)
at org.flywaydb.core.Flyway$6.execute(Flyway.java:990)
at org.flywaydb.core.Flyway.execute(Flyway.java:1171)
at org.flywaydb.core.Flyway.repair(Flyway.java:990)
at org.dspace.storage.rdbms.DatabaseUtils.main(
DatabaseUtils.java:217)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.dspace.app.launcher.ScriptLauncher.runOneCommand(
ScriptLauncher.java:226)
at org.dspace.app.launcher.ScriptLauncher.main(
ScriptLauncher.java:78)
Caused by: java.sql.SQLException: Flyway migration error occurred
at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(
DatabaseUtils.java:483)
at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(
DatabaseUtils.java:391)
at org.dspace.storage.rdbms.DatabaseManager.initialize(
DatabaseManager.java:1378)
at org.dspace.storage.rdbms.DatabaseManager.getDataSource(
DatabaseManager.java:653)
... 19 more
Caused by: org.flywaydb.core.api.FlywayException: Validate failed. Found
differences between applied migrations and available migrations: Migration
on the classpath has not been applied to database: 3.2.1.0
at org.flywaydb.core.Flyway.doValidate(Flyway.java:912)
at org.flywaydb.core.Flyway.access$400(Flyway.java:50)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:817)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:811)
at org.flywaydb.core.Flyway.execute(Flyway.java:1171)
at org.flywaydb.core.Flyway.migrate(Flyway.java:811)
at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(
DatabaseUtils.java:472)
... 22 more
Starting tomcat produces the same errors as previously, ending with:
Caused by: org.flywaydb.core.api.FlywayException: Validate failed. Found
differences between applied migrations and available migrations: Migration
on the classpath has not been applied to database: 3.2.1.0
at org.flywaydb.core.Flyway.doValidate(Flyway.java:912)
at org.flywaydb.core.Flyway.access$400(Flyway.java:50)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:817)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:811)
at org.flywaydb.core.Flyway.execute(Flyway.java:1171)
at org.flywaydb.core.Flyway.migrate(Flyway.java:811)
at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(
DatabaseUtils.java:472)
... 25 more
Sean
On 30 August 2016 at 15:58, Tim Donohue <[email protected]> wrote:
> Hi Sean,
>
> In the version of Flyway (3.x) used by DSpace 5.5, a validation error
> ("Caused by: org.flywaydb.core.api.FlywayException: Validate failed.")
> often is the result of running migrations from different OSes (e.g. Ubuntu
> vs Mac vs Windows) or sometimes even different servers. When Flyway
> "validates" a migration, it just generates a checksum from the validation
> file. Unfortunately, in this version of Flyway, the checksum generated was
> different based on the operating system, etc.
>
> In any case, this error is usually something that can be safely
> ignored/corrected. To tell Flyway to ignore the validation issues and
> update the checksums, simply run:
>
> [dspace]/bin/dspace database repair
>
> This runs a "repair" in Flyway, which just regenerates the checksums of
> all migrations on the current server. It will ensure validation should no
> longer fail on this server in the future.
>
> After running the "repair", you should be able to rerun the migrations
> successfully.
>
> As a sidenote, in Flyway 4 (which we are upgrading to in DSpace 6), this
> issue is resolved. They've figured out a better way to generate these
> checksums so that they are now supposedly the same cross-platform. So,
> hopefully this sort of validation issue will happen less in the future.
>
> - Tim
>
> On 8/30/2016 7:34 AM, Sean Carte wrote:
>
> I'm trying to update a standard DSpace 5.5 installation into a DSpace-CRIS
> installation. But problems arise after tomcat is started, during the flyway
> db update.
>
> I'm running this on Ubuntu 16.04, PostgreSQL 9.5, Tomcat 7, OpenJDK 1.8.
>
> Any suggestions on how I can get around this?
>
> The steps I took and the dspace log are copied below.
>
> I downloaded the source code from https://github.com/Cineca/DSpa
> ce/tree/dspace-cris-5.5.0
>
> dspace@dspace:~/DSpace-dspace-cris-5.5.0$ mvn -U clean package
> ...
> [INFO] BUILD SUCCESS
> ...
> dspace@dspace:~/DSpace-dspace-cris-5.5.0$ cd
> dspace/target/dspace-installer/
> dspace@dspace:~/DSpace-dspace-cris-5.5.0/dspace/target/dspace-installer$
> ant update
> ...
> BUILD SUCCESSFUL
> Total time: 1 minute 1 second
> dspace@dspace:~/DSpace-dspace-cris-5.5.0/dspace/target/dspace-installer$
> cd /dspace/
> dspace@dspace:/dspace$ mkdir rp-files
> dspace@dspace:/dspace$ mkdir rg-files
> dspace@dspace:/dspace$ mkdir ou-files
> dspace@dspace:/dspace$ mkdir do-files
> dspace@dspace:/dspace$ mkdir ws-xsd
> dspace@dspace:/dspace$ cp -r /home/dspace/DSpace-dspace-cri
> s-5.5.0/dspace/etc/webservice/* ws-xsd/
> dspace@dspace:/dspace$ logout
> root@dspace:~# service tomcat7 restart
>
> root@dspace:~# tail -f /dspace/log/dspace.log.2016-08-30
> 2016-08-30 13:19:12,014 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Loading F
> lyway DB migrations from: filesystem:/dspace/etc/postgres,
> classpath:org.dspace.
> storage.rdbms.sqlmigration.postgres, classpath:org.dspace.storage.r
> dbms.migratio
> n
> 2016-08-30 13:19:12,145 INFO org.dspace.storage.rdbms.DatabaseUtils @
> DSpace da
> tabase schema is up to date
> 2016-08-30 13:19:31,044 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS is
> 'PostgreSQL'
> 2016-08-30 13:19:31,046 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS dr
> iver version is '9.5.4'
> 2016-08-30 13:19:31,078 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Loading F
> lyway DB migrations from: filesystem:/dspace/etc/postgres,
> classpath:org.dspace.
> storage.rdbms.sqlmigration.postgres, classpath:org.dspace.storage.r
> dbms.migratio
> n
> 2016-08-30 13:19:31,109 INFO org.flywaydb.core.internal.dbs
> upport.DbSupportFact
> ory @ Database: jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.5)
> 2016-08-30 13:19:31,179 INFO org.dspace.storage.rdbms.DatabaseUtils @
> DSpace da
> tabase schema is up to date
> 2016-08-30 13:19:33,861 INFO org.dspace.content.MetadataSchema @ Loading
> schema
> cache for fast finds
> 2016-08-30 13:19:33,889 INFO org.dspace.content.MetadataField @ Loading
> Metadat
> aField elements into cache.
> 2016-08-30 13:19:34,522 INFO org.dspace.app.xmlui.aspect.ar
> tifactbrowser.Commun
> ityBrowser @ anonymous:session_id=E5A4709B5B44D932EBB86F788B2F03CE:ip_
> addr=10.0.
> 36.134:view_community_list:
> 2016-08-30 13:19:34,536 INFO org.dspace.app.xmlui.aspect.di
> scovery.SidebarFacet
> sTransformer @ facets for scope, null: 3
> 2016-08-30 13:56:41,449 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS is
> 'PostgreSQL'
> 2016-08-30 13:56:41,452 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS dr
> iver version is '9.5.4'
> 2016-08-30 13:56:41,494 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Loading F
> lyway DB migrations from: filesystem:/dspace/etc/postgres,
> classpath:org.dspace.
> storage.rdbms.sqlmigration.postgres, classpath:org.dspace.storage.r
> dbms.migratio
> n
> 2016-08-30 13:56:41,573 INFO org.flywaydb.core.internal.dbs
> upport.DbSupportFact
> ory @ Database: jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.5)
> 2016-08-30 13:56:41,721 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Pending DSpace database schema migrations:
> 2016-08-30 13:56:41,722 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.0
> DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 13:56:41,722 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.1
> DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 13:56:41,759 INFO org.flywaydb.core.internal.command.DbValidate
> @ Va
> lidated 32 migrations (execution time 00:00.030s)
> 2016-08-30 13:56:41,761 ERROR org.dspace.storage.rdbms.DatabaseManager @
> SQL get
> DataSource Error -
> java.sql.SQLException: Flyway migration error occurred
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.j
> ava:483)
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.j
> ava:391)
> at org.dspace.storage.rdbms.DatabaseManager.initialize(Database
> Manager.j
> ava:1378)
> at org.dspace.storage.rdbms.DatabaseManager.getDataSource(Datab
> aseManage
> r.java:653)
> at org.dspace.storage.rdbms.DatabaseManager.getConnection(Datab
> aseManage
> r.java:632)
> at org.dspace.core.Context.init(Context.java:145)
> at org.dspace.core.Context.<init>(Context.java:119)
> at org.dspace.app.util.AbstractDSpaceWebapp.register(AbstractDS
> paceWebap
> p.java:80)
> at org.dspace.app.util.DSpaceContextListener.contextInitialized
> (DSpaceCo
> ntextListener.java:128)
> at org.apache.catalina.core.StandardContext.listenerStart(Stand
> ardContex
> t.java:5068)
> at org.apache.catalina.core.StandardContext.startInternal(Stand
> ardContex
> t.java:5584)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.
> java:147)
> at org.apache.catalina.startup.HostConfig.reload(HostConfig.jav
> a:1547)
> at org.apache.catalina.startup.HostConfig.checkResources(HostCo
> nfig.java
> :1511)
> at org.apache.catalina.startup.HostConfig.check(HostConfig.java
> :1744)
> at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostCo
> nfig.java
> :333)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent
> (Lifecycl
> eSupport.java:117)
> at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(
> LifecycleBa
> se.java:90)
> at org.apache.catalina.core.ContainerBase.backgroundProcess(
> ContainerBas
> e.java:1371)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundPr
> ocessor.p
> rocessChildren(ContainerBase.java:1543)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundPr
> ocessor.p
> rocessChildren(ContainerBase.java:1553)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundPr
> ocessor.run(ContainerBase.java:1521)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.flywaydb.core.api.FlywayException: Validate failed. Found
> differe
> nces between applied migrations and available migrations: Migration on the
> class
> path has not been applied to database: 3.2.1.0
> at org.flywaydb.core.Flyway.doValidate(Flyway.java:912)
> at org.flywaydb.core.Flyway.access$400(Flyway.java:50)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:817)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:811)
> at org.flywaydb.core.Flyway.execute(Flyway.java:1171)
> at org.flywaydb.core.Flyway.migrate(Flyway.java:811)
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.j
> ava:472)
> ... 22 more
> 2016-08-30 13:57:26,647 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS is
> 'PostgreSQL'
> 2016-08-30 13:57:26,650 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS dr
> iver version is '9.5.4'
> 2016-08-30 13:57:26,687 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Loading F
> lyway DB migrations from: filesystem:/dspace/etc/postgres,
> classpath:org.dspace.
> storage.rdbms.sqlmigration.postgres, classpath:org.dspace.storage.r
> dbms.migratio
> n
> 2016-08-30 13:57:26,724 INFO org.flywaydb.core.internal.dbs
> upport.DbSupportFact
> ory @ Database: jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.5)
> 2016-08-30 13:57:26,870 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Pending D
> Space database schema migrations:
> 2016-08-30 13:57:26,871 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.0
> DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:57:26,871 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.1
> FIX-SNAPSHOT-DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:57:26,871 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.2
> DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:57:26,871 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.3
> DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:57:26,871 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.4
> DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:57:26,871 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.5
> DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:57:26,871 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.6
> DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:57:26,871 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.1.0
> DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:57:26,871 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.1.1 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:57:26,871 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.0 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 13:57:26,871 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.1 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 13:57:26,954 INFO org.flywaydb.core.internal.command.DbValidate
> @ Va
> lidated 32 migrations (execution time 00:00.062s)
> 2016-08-30 13:57:26,955 ERROR org.dspace.storage.rdbms.DatabaseManager @
> SQL get
> DataSource Error -
> java.sql.SQLException: Flyway migration error occurred
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.j
> ava:483)
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.j
> ava:391)
> at org.dspace.storage.rdbms.DatabaseManager.initialize(Database
> Manager.j
> ava:1378)
> at org.dspace.storage.rdbms.DatabaseManager.getDataSource(Datab
> aseManage
> r.java:653)
> at org.dspace.storage.rdbms.DatabaseManager.getConnection(Datab
> aseManage
> r.java:632)
> at org.dspace.core.Context.init(Context.java:145)
> at org.dspace.core.Context.<init>(Context.java:119)
> at org.dspace.app.util.AbstractDSpaceWebapp.register(AbstractDS
> paceWebap
> p.java:80)
> at org.dspace.app.util.DSpaceContextListener.contextInitialized
> (DSpaceCo
> ntextListener.java:128)
> at org.apache.catalina.core.StandardContext.listenerStart(Stand
> ardContex
> t.java:5068)
> at org.apache.catalina.core.StandardContext.startInternal(Stand
> ardContex
> t.java:5584)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.
> java:147)
> at org.apache.catalina.startup.HostConfig.reload(HostConfig.jav
> a:1547)
> at org.apache.catalina.startup.HostConfig.checkResources(HostCo
> nfig.java
> :1511)
> at org.apache.catalina.startup.HostConfig.check(HostConfig.java
> :1744)
> at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostCo
> nfig.java
> :333)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent
> (Lifecycl
> eSupport.java:117)
> at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(
> LifecycleBa
> se.java:90)
> at org.apache.catalina.core.ContainerBase.backgroundProcess(
> ContainerBas
> e.java:1371)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundPr
> ocessor.p
> rocessChildren(ContainerBase.java:1543)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundPr
> ocessor.p
> rocessChildren(ContainerBase.java:1553)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundPr
> ocessor.r
> un(ContainerBase.java:1521)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.flywaydb.core.api.FlywayException: Validate failed. Found
> differences between applied migrations and available migrations: Migration
> on the classpath has not been applied to database: 3.2.1.0
> at org.flywaydb.core.Flyway.doValidate(Flyway.java:912)
> at org.flywaydb.core.Flyway.access$400(Flyway.java:50)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:817)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:811)
> at org.flywaydb.core.Flyway.execute(Flyway.java:1171)
> at org.flywaydb.core.Flyway.migrate(Flyway.java:811)
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.java:472)
> ... 22 more
> 2016-08-30 13:58:31,489 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS is 'PostgreSQL'
> 2016-08-30 13:58:31,493 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS driver version is '9.5.4'
> 2016-08-30 13:58:31,563 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Loading Flyway DB migrations from: filesystem:/dspace/etc/postgres,
> classpath:org.dspace.storage.rdbms.sqlmigration.postgres,
> classpath:org.dspace.storage.rdbms.migration
> 2016-08-30 13:58:31,605 INFO
> org.flywaydb.core.internal.dbsupport.DbSupportFactory
> @ Database: jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.5)
> 2016-08-30 13:58:31,837 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Pending DSpace database schema migrations:
> 2016-08-30 13:58:31,838 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.0 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:58:31,838 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.1 FIX-SNAPSHOT-DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:58:31,838 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.2 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:58:31,838 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.3 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:58:31,838 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.4 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:58:31,839 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.5 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:58:31,839 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.6 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:58:31,839 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.1.0 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:58:31,839 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.1.1 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:58:31,839 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.0 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 13:58:31,839 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.1 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 13:58:31,882 INFO org.flywaydb.core.internal.command.DbValidate
> @ Validated 32 migrations (execution time 00:00.038s)
> 2016-08-30 13:58:31,884 ERROR org.dspace.storage.rdbms.DatabaseManager @
> SQL getDataSource Error -
> java.sql.SQLException: Flyway migration error occurred
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.java:483)
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.java:391)
> at org.dspace.storage.rdbms.DatabaseManager.initialize(Database
> Manager.java:1378)
> at org.dspace.storage.rdbms.DatabaseManager.getDataSource(Datab
> aseManager.java:653)
> at org.dspace.storage.rdbms.DatabaseManager.getConnection(Datab
> aseManager.java:632)
> at org.dspace.core.Context.init(Context.java:145)
> at org.dspace.core.Context.<init>(Context.java:119)
> at org.dspace.app.util.AbstractDSpaceWebapp.register(AbstractDS
> paceWebapp.java:80)
> at org.dspace.app.util.DSpaceContextListener.contextInitialized
> (DSpaceContextListener.java:128)
> at org.apache.catalina.core.StandardContext.listenerStart(Stand
> ardContext.java:5068)
> at org.apache.catalina.core.StandardContext.startInternal(Stand
> ardContext.java:5584)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.
> java:147)
> at org.apache.catalina.core.ContainerBase.addChildInternal(Cont
> ainerBase.java:899)
> at org.apache.catalina.core.ContainerBase.access$000(ContainerB
> ase.java:133)
> at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.
> run(ContainerBase.java:156)
> at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.
> run(ContainerBase.java:145)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBas
> e.java:873)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.
> java:652)
> at org.apache.catalina.startup.HostConfig.deployDescriptor(Host
> Config.java:677)
> at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(
> HostConfig.java:1962)
> at java.util.concurrent.Executors$RunnableAdapter.call(
> Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> Executor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> lExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.flywaydb.core.api.FlywayException: Validate failed. Found
> differences between applied migrations and available migrations: Migration
> on the classpath has not been applied to database: 3.2.1.0
> at org.flywaydb.core.Flyway.doValidate(Flyway.java:912)
> at org.flywaydb.core.Flyway.access$400(Flyway.java:50)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:817)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:811)
> at org.flywaydb.core.Flyway.execute(Flyway.java:1171)
> at org.flywaydb.core.Flyway.migrate(Flyway.java:811)
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.java:472)
> ... 25 more
> 2016-08-30 13:59:14,609 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS is 'PostgreSQL'
> 2016-08-30 13:59:14,613 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS driver version is '9.5.4'
> 2016-08-30 13:59:14,656 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Loading Flyway DB migrations from: filesystem:/dspace/etc/postgres,
> classpath:org.dspace.storage.rdbms.sqlmigration.postgres,
> classpath:org.dspace.storage.rdbms.migration
> 2016-08-30 13:59:14,695 INFO
> org.flywaydb.core.internal.dbsupport.DbSupportFactory
> @ Database: jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.5)
> 2016-08-30 13:59:14,802 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Pending DSpace database schema migrations:
> 2016-08-30 13:59:14,803 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.0 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:59:14,808 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.1 FIX-SNAPSHOT-DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:59:14,809 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.2 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:59:14,809 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.3 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:59:14,809 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.4 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:59:14,809 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.5 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:59:14,809 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.6 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:59:14,810 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.1.0 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:59:14,810 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.1.1 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 13:59:14,810 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.0 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 13:59:14,810 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.1 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 13:59:14,880 INFO org.flywaydb.core.internal.command.DbValidate
> @ Validated 32 migrations (execution time 00:00.057s)
> 2016-08-30 13:59:14,885 ERROR org.dspace.storage.rdbms.DatabaseManager @
> SQL getDataSource Error -
> java.sql.SQLException: Flyway migration error occurred
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.java:483)
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.java:391)
> at org.dspace.storage.rdbms.DatabaseManager.initialize(Database
> Manager.java:1378)
> at org.dspace.storage.rdbms.DatabaseManager.getDataSource(Datab
> aseManager.java:653)
> at org.dspace.storage.rdbms.DatabaseManager.getConnection(Datab
> aseManager.java:632)
> at org.dspace.core.Context.init(Context.java:145)
> at org.dspace.core.Context.<init>(Context.java:119)
> at org.dspace.app.util.AbstractDSpaceWebapp.register(AbstractDS
> paceWebapp.java:80)
> at org.dspace.app.util.DSpaceContextListener.contextInitialized
> (DSpaceContextListener.java:128)
> at org.apache.catalina.core.StandardContext.listenerStart(Stand
> ardContext.java:5068)
> at org.apache.catalina.core.StandardContext.startInternal(Stand
> ardContext.java:5584)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.
> java:147)
> at org.apache.catalina.core.ContainerBase.addChildInternal(Cont
> ainerBase.java:899)
> at org.apache.catalina.core.ContainerBase.access$000(ContainerB
> ase.java:133)
> at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.
> run(ContainerBase.java:156)
> at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.
> run(ContainerBase.java:145)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBas
> e.java:873)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.
> java:652)
> at org.apache.catalina.startup.HostConfig.deployDescriptor(Host
> Config.java:677)
> at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(
> HostConfig.java:1962)
> at java.util.concurrent.Executors$RunnableAdapter.call(
> Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> Executor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> lExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.flywaydb.core.api.FlywayException: Validate failed. Found
> differences between applied migrations and available migrations: Migration
> on the classpath has not been applied to database: 3.2.1.0
> at org.flywaydb.core.Flyway.doValidate(Flyway.java:912)
> at org.flywaydb.core.Flyway.access$400(Flyway.java:50)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:817)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:811)
> at org.flywaydb.core.Flyway.execute(Flyway.java:1171)
> at org.flywaydb.core.Flyway.migrate(Flyway.java:811)
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.java:472)
> ... 25 more
> 2016-08-30 14:00:04,741 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Loading Flyway DB migrations from: filesystem:/dspace/etc/postgres,
> classpath:org.dspace.storage.rdbms.sqlmigration.postgres,
> classpath:org.dspace.storage.rdbms.migration
> 2016-08-30 14:00:04,913 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Pending DSpace database schema migrations:
> 2016-08-30 14:00:04,913 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.0 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:04,913 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.1 FIX-SNAPSHOT-DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:04,913 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.2 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:04,913 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.3 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:04,913 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.4 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:04,913 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.5 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:04,914 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.6 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:04,914 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.1.0 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:04,914 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.1.1 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:04,914 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.0 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 14:00:04,914 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.1 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 14:00:58,914 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS is 'PostgreSQL'
> 2016-08-30 14:00:58,917 INFO org.dspace.storage.rdbms.DatabaseManager @
> DBMS driver version is '9.5.4'
> 2016-08-30 14:00:58,959 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Loading Flyway DB migrations from: filesystem:/dspace/etc/postgres,
> classpath:org.dspace.storage.rdbms.sqlmigration.postgres,
> classpath:org.dspace.storage.rdbms.migration
> 2016-08-30 14:00:58,996 INFO
> org.flywaydb.core.internal.dbsupport.DbSupportFactory
> @ Database: jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.5)
> 2016-08-30 14:00:59,226 INFO org.dspace.storage.rdbms.DatabaseUtils @
> Pending DSpace database schema migrations:
> 2016-08-30 14:00:59,227 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.0 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:59,228 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.1 FIX-SNAPSHOT-DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:59,228 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.2 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:59,228 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.3 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:59,228 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.4 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:59,229 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.5 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:59,229 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.0.6 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:59,229 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.1.0 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:59,229 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.3.1.1 DSpaceCRIS-Upgrade-crismodule 5 to 53 SQL PENDING
> 2016-08-30 14:00:59,229 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.0 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 14:00:59,229 INFO org.dspace.storage.rdbms.DatabaseUtils @
> 5.4.0.1 DSpaceCRIS-Upgrade-crismodule 5 to 54 SQL PENDING
> 2016-08-30 14:00:59,289 INFO org.flywaydb.core.internal.command.DbValidate
> @ Validated 32 migrations (execution time 00:00.054s)
> 2016-08-30 14:00:59,291 ERROR org.dspace.storage.rdbms.DatabaseManager @
> SQL getDataSource Error -
> java.sql.SQLException: Flyway migration error occurred
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.java:483)
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.java:391)
> at org.dspace.storage.rdbms.DatabaseManager.initialize(Database
> Manager.java:1378)
> at org.dspace.storage.rdbms.DatabaseManager.getDataSource(Datab
> aseManager.java:653)
> at org.dspace.storage.rdbms.DatabaseManager.getConnection(Datab
> aseManager.java:632)
> at org.dspace.core.Context.init(Context.java:145)
> at org.dspace.core.Context.<init>(Context.java:119)
> at org.dspace.app.util.AbstractDSpaceWebapp.register(AbstractDS
> paceWebapp.java:80)
> at org.dspace.app.util.DSpaceContextListener.contextInitialized
> (DSpaceContextListener.java:128)
> at org.apache.catalina.core.StandardContext.listenerStart(Stand
> ardContext.java:5068)
> at org.apache.catalina.core.StandardContext.startInternal(Stand
> ardContext.java:5584)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.
> java:147)
> at org.apache.catalina.core.ContainerBase.addChildInternal(Cont
> ainerBase.java:899)
> at org.apache.catalina.core.ContainerBase.access$000(ContainerB
> ase.java:133)
> at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.
> run(ContainerBase.java:156)
> at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.
> run(ContainerBase.java:145)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBas
> e.java:873)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.
> java:652)
> at org.apache.catalina.startup.HostConfig.deployDescriptor(Host
> Config.java:677)
> at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(
> HostConfig.java:1962)
> at java.util.concurrent.Executors$RunnableAdapter.call(
> Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> Executor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> lExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.flywaydb.core.api.FlywayException: Validate failed. Found
> differences between applied migrations and available migrations: Migration
> on the classpath has not been applied to database: 3.2.1.0
> at org.flywaydb.core.Flyway.doValidate(Flyway.java:912)
> at org.flywaydb.core.Flyway.access$400(Flyway.java:50)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:817)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:811)
> at org.flywaydb.core.Flyway.execute(Flyway.java:1171)
> at org.flywaydb.core.Flyway.migrate(Flyway.java:811)
> at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(Databa
> seUtils.java:472)
> ... 25 more
> ^C
>
> Sean
> --
>
> --
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
>
--
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
