After starting VM (Centos 6), NiFi 1.1.2 cant start successfully

vft_bizman — Fri, 15 Sep 2017 23:42:47 GMT
I powered off the VM running Centos 6 and NiFi 1.1.2 with active flows in VMWare vCenter. After the next day, I turned on the VM but can't successfully start NiFI. Below are the logs with errors nifi-app.log:
2017-09-15 11:27:38,038 INFO [main] o.a.nifi.properties.NiFiPropertiesLoader Loaded 122 properties from /opt/nifidev-1.2/nifi-1.1.2/./conf/nifi.properties
2017-09-15 11:27:44,603 INFO [main] o.a.nifi.util.FileBasedVariableRegistry Loaded 78 properties from system properties and environment variables
2017-09-15 11:27:44,604 INFO [main] o.a.nifi.util.FileBasedVariableRegistry Loaded a total of 78 properties.  Including precedence overrides effective accessible registry key size is 78
2017-09-15 11:27:45,150 INFO [main] o.a.n.p.PersistentProvenanceRepository Recovered 3804294 records
2017-09-15 11:27:45,156 INFO [main] o.a.n.p.PersistentProvenanceRepository Created new Provenance Event Writers for events starting with ID 22404504
2017-09-15 11:27:45,168 INFO [main] o.a.n.c.repository.FileSystemRepository Maximum Threshold for Container default set to 13983218728 bytes; if volume exceeds this size, archived data will be deleted until it no longer exceeds this size
2017-09-15 11:27:45,170 INFO [main] o.a.n.c.repository.FileSystemRepository Initializing FileSystemRepository with 'Always Sync' set to false
2017-09-15 11:27:45,417 WARN [main] org.eclipse.jetty.webapp.WebAppContext Failed startup of context o.e.j.w.WebAppContext@2620264e{/nifi-api,file:///opt/nifidev-1.2/nifi-1.1.2/work/jetty/nifi-web-api-1.1.2.war/webapp/,UNAVAILABLE}{./work/nar/framework/nifi-framework-nar-1.1.2.nar-unpacked/META-INF/bundled-dependencies/nifi-web-api-1.1.2.war}
org.apache.nifi.web.NiFiCoreException: Unable to start Flow Controller.
        at org.apache.nifi.web.contextlistener.ApplicationStartupContextListener.contextInitialized(ApplicationStartupContextListener.java:85) ~[na:na]
        at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:837) ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:533) ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:810) ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:345) ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1404) ~[jetty-webapp-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1366) ~[jetty-webapp-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:772) ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:262) ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:520) ~[jetty-webapp-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:106) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.server.handler.gzip.GzipHandler.doStart(GzipHandler.java:231) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.server.Server.start(Server.java:411) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:106) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.server.Server.doStart(Server.java:378) [jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) [jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
        at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:675) [nifi-jetty-1.1.2.jar:1.1.2]
        at org.apache.nifi.NiFi.<init>(NiFi.java:156) [nifi-runtime-1.1.2.jar:1.1.2]
        at org.apache.nifi.NiFi.main(NiFi.java:262) [nifi-runtime-1.1.2.jar:1.1.2]
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flowService': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flowController': FactoryBean threw exception on object creation; nested exception is java.lang.IllegalArgumentException: No enum constant org.wali.UpdateType.
        at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:175) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:103) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1585) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:317) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1060) ~[spring-context-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.apache.nifi.web.contextlistener.ApplicationStartupContextListener.contextInitialized(ApplicationStartupContextListener.java:53) ~[na:na]
        ... 28 common frames omitted
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flowController': FactoryBean threw exception on object creation; nested exception is java.lang.IllegalArgumentException: No enum constant org.wali.UpdateType.
        at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:175) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:103) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1585) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:317) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1060) ~[spring-context-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        at org.apache.nifi.spring.StandardFlowServiceFactoryBean.getObject(StandardFlowServiceFactoryBean.java:48) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:168) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        ... 34 common frames omitted
Caused by: java.lang.IllegalArgumentException: No enum constant org.wali.UpdateType.
        at java.lang.Enum.valueOf(Enum.java:238) ~[na:1.8.0_74]
        at org.wali.UpdateType.valueOf(UpdateType.java:24) ~[nifi-write-ahead-log-1.1.2.jar:1.1.2]
        at org.apache.nifi.controller.state.StateMapSerDe.deserializeRecord(StateMapSerDe.java:76) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.apache.nifi.controller.state.StateMapSerDe.deserializeEdit(StateMapSerDe.java:69) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.apache.nifi.controller.state.StateMapSerDe.deserializeEdit(StateMapSerDe.java:30) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.wali.MinimalLockingWriteAheadLog$Partition.recoverNextTransaction(MinimalLockingWriteAheadLog.java:1072) ~[nifi-write-ahead-log-1.1.2.jar:1.1.2]
        at org.wali.MinimalLockingWriteAheadLog.recoverFromEdits(MinimalLockingWriteAheadLog.java:459) ~[nifi-write-ahead-log-1.1.2.jar:1.1.2]
        at org.wali.MinimalLockingWriteAheadLog.recoverRecords(MinimalLockingWriteAheadLog.java:301) ~[nifi-write-ahead-log-1.1.2.jar:1.1.2]
        at org.apache.nifi.controller.state.providers.local.WriteAheadLocalStateProvider.init(WriteAheadLocalStateProvider.java:99) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.apache.nifi.controller.state.providers.AbstractStateProvider.initialize(AbstractStateProvider.java:34) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.apache.nifi.controller.state.manager.StandardStateManagerProvider.createStateProvider(StandardStateManagerProvider.java:189) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.apache.nifi.controller.state.manager.StandardStateManagerProvider.createLocalStateProvider(StandardStateManagerProvider.java:81) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.apache.nifi.controller.state.manager.StandardStateManagerProvider.create(StandardStateManagerProvider.java:67) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.apache.nifi.controller.FlowController.<init>(FlowController.java:469) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:375) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.apache.nifi.spring.FlowControllerFactoryBean.getObject(FlowControllerFactoryBean.java:74) ~[nifi-framework-core-1.1.2.jar:1.1.2]
        at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:168) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
        ... 41 common frames omitted
Re: After starting VM (Centos 6), NiFi 1.1.2 cant start successfully

Wynner — Tue, 19 Sep 2017 23:16:25 GMT
@Virgil Fritz Taneza
That looks like the flow file repository has become corrupted. When you shutdown the VM did you stop NiFi first? If not, then next time I would recommend doing it that way.
You'll have to remove all data the flow file and content repositories and then NiFi should start.
Re: After starting VM (Centos 6), NiFi 1.1.2 cant start successfully

vft_bizman — Wed, 20 Sep 2017 00:56:13 GMT
Hi @Wynner, I did not stop NiFi first before powering off the VM. Thanks for the answer.
question After starting VM (Centos 6), NiFi 1.1.2 cant start successfully in Archives of Support Questions (Read Only)

After starting VM (Centos 6), NiFi 1.1.2 cant start successfully

Re: After starting VM (Centos 6), NiFi 1.1.2 cant start successfully

Re: After starting VM (Centos 6), NiFi 1.1.2 cant start successfully
