[Solved] Upgrading to latest version. DB could not be updated

Unimus support forum
Post Reply
histec
Posts: 5
Joined: Mon Nov 19, 2018 2:24 pm

Tue Aug 10, 2021 7:50 pm

This is during the startup checks, but GUI shows, but failed on Database upgrade. This should be HSQL it is using. Sounds like it may be locked, any ideas. Thank you. HIS

2021-08-10 14:38:02.005 INFO 9047 --- [main] n.unimus.starter.composite.Application : Started Application in 22.55 seconds (JVM running for 23.556)
2021-08-10 14:38:02.915 INFO 9047 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.b.step.LoggingPathAccessibility : Checking logging subsystem
2021-08-10 14:38:02.917 INFO 9047 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.b.step.DatabaseConnectionCheck : Testing database connection
2021-08-10 14:38:03.691 INFO 9047 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.b.step.DatabaseConnectionCheck : Database connection test passed
2021-08-10 14:38:03.692 INFO 9047 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.boot.step.DatabaseUpdate : Connecting to database (HSQL, jdbc:hsqldb:file:///etc/unimus/hsql/db;hsqldb.tx=mvcc)
2021-08-10 14:38:03.694 INFO 9047 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.boot.step.DatabaseUpdate : Updating database schema
2021-08-10 14:39:04.217 ERROR 9047 --- [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.his.io (10.4.4.222) since 8/10/21 1:23 PM'
2021-08-10 14:41:51.463 WARN 9047 --- [SpringContextShutdownHook] o.s.b.f.support.DisposableBeanAdapter : Invocation of destroy method failed on bean with name 'database': java.lang.NullPointerException
User avatar
Tomas
Posts: 1269
Joined: Sat Jun 25, 2016 12:33 pm

Tue Aug 10, 2021 7:57 pm

Hi,

This lock happens when Unimus is restarted during an already in progress update - in other words when a DB update is interrupted. If this is HSQL, one of our team can do a Zoom session with you and help you fix this (it is easier to fix on MySQL/ PGSQL, but on HSQL requires us).

Please open a Support Ticket on the Portal, and we will get this sorted out with you :)
Post Reply