Liquidbase LockException not able to launch icescrum

[jlabuelo]

Hi all
We have been testing Icescrum under Tomcat 7 with the War file for some weeks, but today we found that the service was down and when we tried to restart it, we got this error message in the log file:

Caused by: org.codehaus.groovy.runtime.InvokerInvocationException: liquibase.exception.LockException: Could not acquire change log lock.  Currently locked by SD1111100149 (192.168.2.12) since 7/10/16 12:59
	... 4 more
Caused by: liquibase.exception.LockException: Could not acquire change log lock.  Currently locked by SD1111100149 (192.168.2.12) since 7/10/16 12:59
	at liquibase.lockservice.LockService.waitForLock(LockService.java:81)
	at liquibase.lockservice.LockService$waitForLock.call(Unknown Source)
	at liquibase.LiquibaseDsl.update(LiquibaseDsl.groovy:63)
	at liquibase.LiquibaseDsl$update.call(Unknown Source)
	at autobase.Autobase.migrate(Autobase.groovy:43)
	at autobase.Autobase$migrate.call(Unknown Source)
	at AutobaseGrailsPlugin$__clinit__closure9.doCall(AutobaseGrailsPlugin.groovy:103)
	at AutobaseGrailsPlugin.invokeMethod(AutobaseGrailsPlugin.groovy)
	at AutobaseGrailsPlugin$_closure2.doCall(AutobaseGrailsPlugin.groovy:114)

I found in the forums that one solution was to create a new empty DB… however that would mean losign all the info we already have. We have tried to use an empty DB and the system restarts with no issue, but if in the new DB we restore the backup of the old DB the system crashes at restart time again.

Any ideas about how to recover our system back with the info?

Regards

[Vincent Barrier]

Hello,

You can remove lock by updating lock (from 1 to 0 value) in the single row of the table databasechangelock

[Author]

Posts