JHipster Liquibase startup failure: diagnosing checksum or lock errors

Problem

During a new deployment of a JHipster‑generated Spring Boot application, the application aborts during startup, immediately after the Liquibase migration step. The log shows either a ValidationFailedException mentioning a changeset id and author, or a LockException indicating the change‑log lock cannot be acquired.

Goal

Identify the root cause of the Liquibase failure from the startup logs and determine whether it is a checksum mismatch, a stale lock, or a database‑compatibility issue.

Constraints

The application uses the prod profile, with spring.jpa.hibernate.ddl-auto set to none and spring.liquibase.change-log pointing to classpath:config/liquibase/master.xml. The database used at deployment may differ from the one used at generation time.

Questions

1. Which changeset id and author are reported in the ValidationFailedException, and what is the MD5SUM discrepancy?

2. Does DATABASECHANGELOGOCK contain a row with LOCKED=1, and is any Liquibase process still running?

3. Are there database‑specific DDL or type errors that could surface only in the target engine?