CMA Master slow to start

Resolve a slow long CMA Master startup immediately after upgrade by tracking Liquibase migration work against the metadata database.

Symptom: CMA Master takes a long time to start or appears unresponsive after startup.

Cause: Liquibase database migration runs on first startup after an upgrade, which can take about 60–90 seconds.

For database expectations and external JDBC backends, see CMA database backends.

Wait for startup to finish instead of restarting repeatedly.
Monitor the CMA Master application log for progress.

Default path: /var/log/cma/cma-server.log. For other log paths, see Log locations and key file paths.