Thanks for the update and apologies for the inconvenience you are experiencing, Lee.
I went through the log and compiled a condensed version:
[INFO] Scanning for projects...
Downloading from openmrs-repo: https://mavenrepo.openmrs.org/nexus/content/repositories/public/javax/annotation/javax.annotation-api/maven-metadata.xml
Progress (1): 591 B
Downloaded from openmrs-repo: https://mavenrepo.openmrs.org/nexus/content/repositories/public/javax/annotation/javax.annotation-api/maven-metadata.xml (591 B at 262 B/s)
[INFO]
[INFO] -------------------< org.openmrs.web:openmrs-webapp >-------------------
[INFO] Building openmrs-webapp 2.4.0-SNAPSHOT
[INFO] --------------------------------[ war ]---------------------------------
[INFO]
[INFO]
...
Line 89 >>>> INFO - Slf4jLogger.info(42) |2020-05-22T05:56:41,874| CREATE TABLE openmrs.liquibasechangelog (ID VARCHAR(255) NOT NULL, AUTHOR VARCHAR(255) NOT NULL, FILENAME VARCHAR(255) NOT NULL, DATEEXECUTED datetime NOT NULL, ORDEREXECUTED INT NOT NULL, EXECTYPE VARCHAR(10) NOT NULL, MD5SUM VARCHAR(35) NULL, `DESCRIPTION` VARCHAR(255) NULL, COMMENTS VARCHAR(255) NULL, TAG VARCHAR(255) NULL, LIQUIBASE VARCHAR(20) NULL, CONTEXTS VARCHAR(255) NULL, LABELS VARCHAR(255) NULL, DEPLOYMENT_ID
...
Line 96 >>>> INFO - Slf4jLogger.info(42) |2020-05-22T05:56:46,095| CREATE TABLE openmrs.liquibasechangeloglock (ID INT NOT NULL, `LOCKED` TINYINT(1) NOT NULL, LOCKGRANTED datetime NULL, LOCKEDBY VARCHAR(255) NULL, CONSTRAINT PK_LIQUIBASECHANGELOGLOCK PRIMARY KEY (ID))
...
Line 105 >>>> INFO - Slf4jLogger.info(42) |2020-05-22T05:56:48,966| ChangeSet org\openmrs\liquibase\snapshots\schema-only\liquibase-schema-only-2.3.x.xml::1582473628795-1::wolf (generated) ran successfully in 110ms
...
Line 3615 >>>> INFO - Slf4jLogger.info(42) |2020-05-22T05:58:22,234| ChangeSet org\openmrs\liquibase\snapshots\core-data\liquibase-core-data-2.3.x.xml::1582473679024-17::wolf (generated) ran successfully in 20ms
...
Line 4789 >>>> [INFO] Initializing Spring root WebApplicationContext
...
Line 4798 >>>> INFO - ChangeLogDetective.getInitialLiquibaseSnapshotVersion(80) |2020-05-22T05:58:48,415| looking for un-run change sets in snapshot version '2.3.x'
...
Line 4805 >>>> INFO - ChangeLogDetective.getInitialLiquibaseSnapshotVersion(89) |2020-05-22T05:58:50,053| file 'org\openmrs\liquibase\snapshots\schema-only\liquibase-schema-only-2.3.x.xml' contains 875 un-run change sets
...
Line 4812 >>>> INFO - ChangeLogDetective.getInitialLiquibaseSnapshotVersion(89) |2020-05-22T05:58:50,572| file 'org\openmrs\liquibase\snapshots\core-data\liquibase-core-data-2.3.x.xml' contains 25 un-run change sets
...
The first four entries marked by “>>>>” show that the database was successfully initialised based on the 2.3.x Liquibase snapshots (which is good and as expected).
Line 4789 signals that initialisation is over and the web application is initialised.
The last three entries show that the 2.3.x snapshots are not being recognised (which is bad) and we need to figure out why that is the case.
Could you please share the result of running these commands:
$ mysql -u root -p
mysql> use openmrs;
mysql> describe liquibasechangelog;
mysql> select * from liquibasechangelog;
Could you please also share the link to the Google doc folder containing all documents? I could open the log file but not the other files you had shared.
Thank you,
Wolf