Container ssg cannot start. Log has error information:
error running Liquibase: Could not acquire change log lock. Currently locked by 5365b08ff53f (fe80:0:0:0:42:acff:fe12:4%eth1) since 9/10/22 12:33 AM.
Release : 10.0 10.1
Component : API GATEWAY
Mysql DB ( local , aws rds , ...)
Because concurrent update/rollback/etc. operations to a database will interfere with each other, Liquibase has a LockService which is used to coordinate access so only one instance can run against a database at time.
Examples of when you can run into concurrency trouble:
The StandardLockService is the normal implementation that uses a
databasechangeloglock table. Liquibase inserts a record and commits it at startup time, and if other instances see that record they wait until it is cleared.
The big problem with this standard implementation is that IF the instance doing the update is killed before it commits the clearing of the record, that value is stuck until
liquibase clearLocks is ran.
Container gateway portal uses Liquibase when the server is starting. So it is possible the database is locked due to unexpected exception.