Using liquibase 4.6.2 on GitlabCI error SEVERE [liquibase.integration] Unexpected error running Liquibase: ../update.log.lck

Hello

I’m trying to use the latest offical community edition available, 4.6.2, from GitlabCI on a docker image.

I have the following error when trying to run an update command :

Unexpected error running Liquibase: /.../update.log.lck

[229](https://gitlab.../-/jobs/111#L111)For more information, please use the --logLevel flag

[230](https://gitlab.../-/jobs/111#L111)[2021-12-24 10:17:01] FINE [liquibase.configuration] No configuration value for liquibase.filterLogMessages found

[231](https://gitlab.../-/jobs/111#L111)[2021-12-24 10:17:01] SEVERE [liquibase.integration] Unexpected error running Liquibase: /.../update.log.lck

[232](https://gitlab.../-/jobs/111#L111)java.nio.file.NoSuchFileException: /.../update.log.lck

[233](https://gitlab.../-/jobs/111#L111) at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
...

A previous version of liquibase (I don’t have the exact version but it is from 2017/2018 ) is running fine via GitlabCI on the same docker image. I can’t use it because a changelog was generated using the 4.6.2 version, and when I tryied running the update command using the old liquibase version, I presumed that the format is not compatible because I had this error :

Unexpected error running Liquibase: Error parsing line 220 column 300 of initialization-changelog.xml: cvc-complex-type.3.2.2 : attribute 'validate' is not allowed for 'addForeignKeyConstraint'.

Line 220 of the changelog :
<addForeignKeyConstraint baseColumnNames="column" baseTableName="table" constraintName="constraintName" deferrable="false" initiallyDeferred="false" onDelete="NO ACTION" onUpdate="NO ACTION" referencedColumnNames="column" referencedTableName="table2" validate="true"/>

When running the same command from a powershell command it is running fine with version 4.6.2 :

call Liquibase --changeLogFile=master-changelog.xml --defaultsFile=Liquibase_Local.properties --logFile=update.log --logLevel=debug update
Liquibase Community 4.6.2 by Liquibase
####################################################
##   _     _             _ _                      ##
##  | |   (_)           (_) |                     ##
##  | |    _  __ _ _   _ _| |__   __ _ ___  ___   ##
##  | |   | |/ _` | | | | | '_ \ / _` / __|/ _ \  ##
##  | |___| | (_| | |_| | | |_) | (_| \__ \  __/  ##
##  \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___|  ##
##              | |                               ##
##              |_|                               ##
##                                                ##
##  Get documentation at docs.liquibase.com       ##
##  Get certified courses at learn.liquibase.com  ##
##  Free schema change activity reports at        ##
##      https://hub.liquibase.com                 ##
##                                                ##
####################################################
Starting Liquibase at 11:46:01 (version 4.6.2 #886 built at 2021-11-30 16:20+0000)
Liquibase: Update has been successful.

A rollback command also runs also successfully from a powershell command.

Do you know how I could solve the error shown when trying to run the 4.6.2 version from GitlabCI ?

Thank you :slight_smile:

Hello @benoo,

The error message you are getting Unexpected error running Liquibase: /.../update.log.lck indicates that the database changelog lock table is locked for some reason. Sometimes if the update application is abruptly stopped, then the lock table remains locked.

You can try running the release-locks command to unlock the DATABASECHANGELOGLOCK table. Or manually change the value for the column locked to false or 0 (depending on the database platform).

Please let us know if the issue persists.