Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- INFO: Starting service Catalina
- Nov 17, 2020 5:01:23 PM org.apache.catalina.core.StandardEngine startInternal
- INFO: Starting Servlet Engine: Apache Tomcat/7.0.52 (Ubuntu)
- Nov 17, 2020 5:01:23 PM org.apache.catalina.startup.HostConfig deployDescriptor
- INFO: Deploying configuration descriptor /etc/tomcat7/Catalina/localhost/manager.xml
- Nov 17, 2020 5:01:24 PM org.apache.catalina.startup.HostConfig deployDescriptor
- INFO: Deploying configuration descriptor /etc/tomcat7/Catalina/localhost/host-manager.xml
- Nov 17, 2020 5:01:24 PM org.apache.catalina.startup.HostConfig deployWAR
- INFO: Deploying web application archive /var/lib/tomcat7/webapps/openmrs.war
- WARN - OpenmrsUtil.getRuntimePropertiesFilePathName(2078) |2020-11-17 17:01:35,920| Unable to find a runtime properties file at /var/lib/tomcat7/openmrs-runtime.properties
- WARN - OpenmrsUtil.getRuntimePropertiesFilePathName(2078) |2020-11-17 17:01:35,987| Unable to find a runtime properties file at /var/lib/tomcat7/openmrs-runtime.properties
- INFO - Listener.contextInitialized(173) |2020-11-17 17:01:35,988| Using runtime properties file: /usr/share/tomcat7/.OpenMRS/openmrs-runtime.properties
- INFO 11/17/20 5:01 PM:liquibase: Reading from `liquibasechangelog`
- WARNING 11/17/20 5:01 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:01 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:01 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- INFO 11/17/20 5:01 PM:liquibase: Reading from `liquibasechangelog`
- WARNING 11/17/20 5:01 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:01 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:01 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARN - OpenmrsUtil.getRuntimePropertiesFilePathName(2078) |2020-11-17 17:01:41,866| Unable to find a runtime properties file at /var/lib/tomcat7/openmrs-runtime.properties
- Nov 17, 2020 5:01:42 PM org.apache.catalina.startup.HostConfig deployDirectory
- INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
- Nov 17, 2020 5:01:42 PM org.apache.coyote.AbstractProtocol start
- INFO: Starting ProtocolHandler ["http-bio-8080"]
- Nov 17, 2020 5:01:42 PM org.apache.catalina.startup.Catalina start
- INFO: Server startup in 18715 ms
- ERROR - CommonsLogLogChute.log(96) |2020-11-17 17:03:09,329| #parse() null argument
- ERROR - CommonsLogLogChute.log(96) |2020-11-17 17:03:09,382| #parse() null argument
- ERROR - CommonsLogLogChute.log(96) |2020-11-17 17:03:22,596| #parse() null argument
- ERROR - CommonsLogLogChute.log(96) |2020-11-17 17:03:22,623| #parse() null argument
- ERROR - CommonsLogLogChute.log(96) |2020-11-17 17:03:28,079| #parse() null argument
- ERROR - CommonsLogLogChute.log(96) |2020-11-17 17:03:28,147| #parse() null argument
- INFO 11/17/20 5:03 PM:liquibase: Reading from `liquibasechangelog`
- WARNING 11/17/20 5:03 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:03 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:03 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- ERROR - DatabaseUpdater.executeChangelog(230) |2020-11-17 17:03:29,832| Could not release lock
- liquibase.exception.LockException: liquibase.exception.LockException: Did not update change log lock correctly.
- 0 rows were updated instead of the expected 1 row using executor liquibase.executor.jvm.JdbcExecutor there are 0 rows in the table
- at liquibase.lockservice.LockService.releaseLock(LockService.java:152)
- at org.openmrs.util.DatabaseUpdater.executeChangelog(DatabaseUpdater.java:227)
- at org.openmrs.util.DatabaseUpdater.executeChangelog(DatabaseUpdater.java:150)
- at org.openmrs.web.filter.update.UpdateFilter$UpdateFilterCompletion$1.run(UpdateFilter.java:726)
- at java.lang.Thread.run(Thread.java:748)
- Caused by: liquibase.exception.LockException: Did not update change log lock correctly.
- 0 rows were updated instead of the expected 1 row using executor liquibase.executor.jvm.JdbcExecutor there are 0 rows in the table
- at liquibase.lockservice.LockService.releaseLock(LockService.java:140)
- ... 4 more
- ERROR - UpdateFilter$UpdateFilterCompletion$1.run(742) |2020-11-17 17:03:29,839| Unable to update the database
- org.openmrs.util.DatabaseUpdateException: There was an error while updating the database to the latest. file: liquibase-update-to-latest.xml. Error: liquibase.exception.DatabaseException: Empty result set, expected one row
- at org.openmrs.util.DatabaseUpdater.executeChangelog(DatabaseUpdater.java:154)
- at org.openmrs.web.filter.update.UpdateFilter$UpdateFilterCompletion$1.run(UpdateFilter.java:726)
- at java.lang.Thread.run(Thread.java:748)
- Caused by: liquibase.exception.LockException: liquibase.exception.DatabaseException: Empty result set, expected one row
- at liquibase.lockservice.LockService.acquireLock(LockService.java:121)
- at liquibase.lockservice.LockService.waitForLock(LockService.java:61)
- at org.openmrs.util.DatabaseUpdater.executeChangelog(DatabaseUpdater.java:208)
- at org.openmrs.util.DatabaseUpdater.executeChangelog(DatabaseUpdater.java:150)
- ... 2 more
- Caused by: liquibase.exception.DatabaseException: Empty result set, expected one row
- at liquibase.util.JdbcUtils.requiredSingleResult(JdbcUtils.java:124)
- at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:159)
- at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:167)
- at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:163)
- at liquibase.lockservice.LockService.acquireLock(LockService.java:96)
- ... 5 more
- INFO 11/17/20 5:03 PM:liquibase: Reading from `liquibasechangelog`
- WARNING 11/17/20 5:03 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:03 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:03 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- ERROR - CommonsLogLogChute.log(96) |2020-11-17 17:19:58,815| #parse() null argument
- ERROR - CommonsLogLogChute.log(96) |2020-11-17 17:19:58,821| #parse() null argument
- INFO 11/17/20 5:19 PM:liquibase: Reading from `liquibasechangelog`
- WARNING 11/17/20 5:20 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:20 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:20 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- ERROR - DatabaseUpdater.executeChangelog(230) |2020-11-17 17:20:00,296| Could not release lock
- liquibase.exception.LockException: liquibase.exception.LockException: Did not update change log lock correctly.
- 0 rows were updated instead of the expected 1 row using executor liquibase.executor.jvm.JdbcExecutor there are 0 rows in the table
- at liquibase.lockservice.LockService.releaseLock(LockService.java:152)
- at org.openmrs.util.DatabaseUpdater.executeChangelog(DatabaseUpdater.java:227)
- at org.openmrs.util.DatabaseUpdater.executeChangelog(DatabaseUpdater.java:150)
- at org.openmrs.web.filter.update.UpdateFilter$UpdateFilterCompletion$1.run(UpdateFilter.java:726)
- at java.lang.Thread.run(Thread.java:748)
- Caused by: liquibase.exception.LockException: Did not update change log lock correctly.
- 0 rows were updated instead of the expected 1 row using executor liquibase.executor.jvm.JdbcExecutor there are 0 rows in the table
- at liquibase.lockservice.LockService.releaseLock(LockService.java:140)
- ... 4 more
- ERROR - UpdateFilter$UpdateFilterCompletion$1.run(742) |2020-11-17 17:20:00,298| Unable to update the database
- org.openmrs.util.DatabaseUpdateException: There was an error while updating the database to the latest. file: liquibase-update-to-latest.xml. Error: liquibase.exception.DatabaseException: Empty result set, expected one row
- at org.openmrs.util.DatabaseUpdater.executeChangelog(DatabaseUpdater.java:154)
- at org.openmrs.web.filter.update.UpdateFilter$UpdateFilterCompletion$1.run(UpdateFilter.java:726)
- at java.lang.Thread.run(Thread.java:748)
- Caused by: liquibase.exception.LockException: liquibase.exception.DatabaseException: Empty result set, expected one row
- at liquibase.lockservice.LockService.acquireLock(LockService.java:121)
- at liquibase.lockservice.LockService.waitForLock(LockService.java:61)
- at org.openmrs.util.DatabaseUpdater.executeChangelog(DatabaseUpdater.java:208)
- at org.openmrs.util.DatabaseUpdater.executeChangelog(DatabaseUpdater.java:150)
- ... 2 more
- Caused by: liquibase.exception.DatabaseException: Empty result set, expected one row
- at liquibase.util.JdbcUtils.requiredSingleResult(JdbcUtils.java:124)
- at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:159)
- at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:167)
- at liquibase.executor.jvm.JdbcExecutor.queryForObject(JdbcExecutor.java:163)
- at liquibase.lockservice.LockService.acquireLock(LockService.java:96)
- ... 5 more
- INFO 11/17/20 5:20 PM:liquibase: Reading from `liquibasechangelog`
- WARNING 11/17/20 5:20 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:20 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
- WARNING 11/17/20 5:20 PM:liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement