Openmrs fails at startup after rebasing with upstream master

Hello @dkayiwa @paradise

The following error occurred at startup: Error occurred while trying to get the updates needed for the database. Validation Failed: 2 change sets check sum liquibase-update-to-latest.xml::20180214-1000::Kelechi+iheanyi is now: 3:803e7f09b2e60ff14f0760095f470292 liquibase-update-to-latest.xml::20181402-TRUNK-5339::esirkings is now: 3:bde2e3cb0e7a69640acc16e53f4e8ee8 java.lang.RuntimeException: Error occurred while trying to get the updates needed for the database. Validation Failed: 2 change sets check sum liquibase-update-to-latest.xml::20180214-1000::Kelechi+iheanyi is now: 3:803e7f09b2e60ff14f0760095f470292 liquibase-update-to-latest.xml::20181402-TRUNK-5339::esirkings is now: 3:bde2e3cb0e7a69640acc16e53f4e8ee8

at org.openmrs.util.DatabaseUpdater.getUnrunDatabaseChanges(DatabaseUpdater.java:630)
at org.openmrs.util.DatabaseUpdater.getUnrunDatabaseChanges(DatabaseUpdater.java:587)
at org.openmrs.util.DatabaseUpdater.updatesRequired(DatabaseUpdater.java:252)
at org.openmrs.web.Listener.setupNeeded(Listener.java:217)
at org.openmrs.web.Listener.contextInitialized(Listener.java:179)
at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:835)
at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:530)
at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:808)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:342)
at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1368)
at org.eclipse.jetty.maven.plugin.JettyWebAppContext.startWebapp(JettyWebAppContext.java:320)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1335)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:772)
at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:259)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:511)
at org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:403)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:161)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.server.Server.start(Server.java:405)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:106)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart(Server.java:372)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.maven.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:457)
at org.eclipse.jetty.maven.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:328)
at org.eclipse.jetty.maven.plugin.JettyRunMojo.execute(JettyRunMojo.java:170)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: liquibase.exception.ValidationFailedException: Validation Failed: 2 change sets check sum liquibase-update-to-latest.xml::20180214-1000::Kelechi+iheanyi is now: 3:803e7f09b2e60ff14f0760095f470292 liquibase-update-to-latest.xml::20181402-TRUNK-5339::esirkings is now: 3:bde2e3cb0e7a69640acc16e53f4e8ee8

at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:141)
at liquibase.Liquibase.listUnrunChangeSets(Liquibase.java:625)
at org.openmrs.util.DatabaseUpdater.getUnrunDatabaseChanges(DatabaseUpdater.java:617)
... 56 more

The easiest for you is going to be dropping the database and runtime properties file. Then run again.

@dkayiwa Yeah this is the third time this issue has happened and i always had to drop everything as you said, i usually think am doing it the crud way. just hope there was another alternative that doesnot involved droping tables; Thanks

Which ticket are you working on?

@dkayiwa I finished and made a pull request on TRUNK-5221 with pull request here and trying to start wok on RESTWS-706 after building the Rest webservice module I could not start openmrs any longer with the error above.

If you are not working on a TRUNK ticket, you can just use a released instead of snapshot version of openmrs-core.

I theory you should not be applying liquibase changesets to your development database except for those that have made it to master. If you are working on a ticket you always have to use a different database that you can discard after working on the ticket.

Thanks @dkayiwa @wyclif. for the info