Could not upgrade the database

Unimus support forum
Post Reply
Sprooky
Posts: 2
Joined: Tue May 22, 2018 3:32 pm

Tue May 22, 2018 3:34 pm

Hi !

I upgrade from 1.6 to 1.7.2 and i got this error message :

Could not upgrade the database.
Please contact support or restart Unimus and try again.

I try to reboot the server and it still does'nt work.

I'm on debian 9.

Thank you
Sprooky
Posts: 2
Joined: Tue May 22, 2018 3:32 pm

Tue May 22, 2018 3:38 pm

2018-05-22 11:28:02.850 INFO 566 --- [main] net.unimus.Application : The following profiles are active: together,unix,jar
2018-05-22 11:28:35.323 INFO 566 --- [main] s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat initialized with port(s): 8085 (http)
2018-05-22 11:28:41.049 INFO 566 --- [main] s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat started on port(s): 8085 (http)
2018-05-22 11:28:41.066 INFO 566 --- [main] net.unimus.Application : Started Application in 47.733 seconds (JVM running for 49.299)
2018-05-22 11:28:41.696 INFO 566 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.b.step.LoggingPathAccessibility : Checking logging subsystem
2018-05-22 11:28:41.730 INFO 566 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.b.step.DatabaseConnectionCheck : Testing database connection
2018-05-22 11:28:42.633 INFO 566 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.b.step.DatabaseConnectionCheck : Database connection test passed
2018-05-22 11:28:42.635 INFO 566 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.boot.step.DatabaseUpdate : Connecting to database (HSQL, jdbc:hsqldb:file:///etc/unimus/hsql/db)
2018-05-22 11:28:42.639 INFO 566 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.boot.step.DatabaseUpdate : Updating database schema
2018-05-22 11:29:42.951 WARN 566 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.boot.step.DatabaseUpdate : Failed to update database schema. Reason = liquibase.exception.LockException: Could not acquire change log lock. Currently locked by unimus.smith.local (10.6.66.80) since 22/05/18 11:24 AM
User avatar
Tomas
Posts: 510
Joined: Sat Jun 25, 2016 12:33 pm

Tue May 22, 2018 3:42 pm

Hi,

Could we please do a Webex session to look at this issue more closely?
(please contact me in a PM to work out the details)

Thanks!
Post Reply