HDF-3.1.1.0 NiFi Registry not starting

[#1]

Hi all,

I'm trying to start NiFi registry but it keeps on failing with this below

2018-03-22 12:50:49,102 INFO [main] o.apache.nifi.registry.bootstrap.Command Starting Apache NiFi Registry...
2018-03-22 12:50:49,104 INFO [main] o.apache.nifi.registry.bootstrap.Command Working Directory: /usr/hdf/current/nifi-registry
2018-03-22 12:50:49,105 INFO [main] o.apache.nifi.registry.bootstrap.Command Command: /usr/lib/jvm/jre-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/bin/java -classpath /usr/hdf/current/nifi-registry/conf:/usr/hdf/current/nifi-registry/lib/shared/commons-lang3-3.5.jar:/usr/hdf/current/nifi-registry/lib/shared/nifi-registry-utils-0.1.0.3.1.1.0-35.jar:/usr/hdf/current/nifi-registry/lib/apache-el-8.5.9.1.jar:/usr/hdf/current/nifi-registry/lib/apache-jsp-8.5.9.1.jar:/usr/hdf/current/nifi-registry/lib/taglibs-standard-spec-1.2.5.jar:/usr/hdf/current/nifi-registry/lib/apache-jsp-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/apache-jstl-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/asm-5.1.jar:/usr/hdf/current/nifi-registry/lib/asm-commons-5.1.jar:/usr/hdf/current/nifi-registry/lib/asm-tree-5.1.jar:/usr/hdf/current/nifi-registry/lib/bcprov-jdk15on-1.55.jar:/usr/hdf/current/nifi-registry/lib/commons-lang3-3.5.jar:/usr/hdf/current/nifi-registry/lib/ecj-4.4.2.jar:/usr/hdf/current/nifi-registry/lib/javax.annotation-api-1.2.jar:/usr/hdf/current/nifi-registry/lib/javax.servlet-api-3.1.0.jar:/usr/hdf/current/nifi-registry/lib/jcl-over-slf4j-1.7.12.jar:/usr/hdf/current/nifi-registry/lib/jetty-annotations-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-continuation-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-http-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-io-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-jndi-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-plus-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-schemas-3.1.jar:/usr/hdf/current/nifi-registry/lib/jetty-security-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-server-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-servlet-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-servlets-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-util-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-webapp-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jetty-xml-9.4.3.v20170317.jar:/usr/hdf/current/nifi-registry/lib/jul-to-slf4j-1.7.12.jar:/usr/hdf/current/nifi-registry/lib/log4j-over-slf4j-1.7.12.jar:/usr/hdf/current/nifi-registry/lib/logback-classic-1.1.3.jar:/usr/hdf/current/nifi-registry/lib/logback-core-1.1.3.jar:/usr/hdf/current/nifi-registry/lib/slf4j-api-1.7.12.jar:/usr/hdf/current/nifi-registry/lib/nifi-registry-jetty-0.1.0.3.1.1.0-35.jar:/usr/hdf/current/nifi-registry/lib/nifi-registry-properties-0.1.0.3.1.1.0-35.jar:/usr/hdf/current/nifi-registry/lib/nifi-registry-provider-api-0.1.0.3.1.1.0-35.jar:/usr/hdf/current/nifi-registry/lib/taglibs-standard-impl-1.2.5.jar:/usr/hdf/current/nifi-registry/lib/nifi-registry-runtime-0.1.0.3.1.1.0-35.jar:/usr/hdf/current/nifi-registry/lib/nifi-registry-security-api-0.1.0.3.1.1.0-35.jar -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true -Djava.protocol.handler.pkgs=sun.net.www.protocol -Dnifi.registry.properties.file.path=/usr/hdf/current/nifi-registry/conf/nifi-registry.properties -Dnifi.registry.bootstrap.listen.port=29952 -Dapp=NiFiRegistry -Dorg.apache.nifi.registry.bootstrap.config.log.dir= org.apache.nifi.registry.NiFiRegistry 
2018-03-22 12:50:49,116 INFO [main] o.apache.nifi.registry.bootstrap.Command Launched Apache NiFi Registry with Process ID 13082
2018-03-22 12:50:49,468 INFO [NiFi Registry Bootstrap Command Listener] o.a.n.registry.bootstrap.RunNiFiRegistry Apache NiFi Registry now running and listening for Bootstrap requests on port 19605
2018-03-22 12:50:51,604 INFO [NiFi logging handler] org.apache.nifi.registry.StdOut 
2018-03-22 12:50:51,605 INFO [NiFi logging handler] org.apache.nifi.registry.StdOut   Apache NiFi   _     _
2018-03-22 12:50:51,605 INFO [NiFi logging handler] org.apache.nifi.registry.StdOut  _ __ ___  __ _(_)___| |_ _ __ _   _
2018-03-22 12:50:51,605 INFO [NiFi logging handler] org.apache.nifi.registry.StdOut | '__/ _ \/ _` | / __| __| '__| | | |
2018-03-22 12:50:51,605 INFO [NiFi logging handler] org.apache.nifi.registry.StdOut | | |  __/ (_| | \__ \ |_| |  | |_| |
2018-03-22 12:50:51,605 INFO [NiFi logging handler] org.apache.nifi.registry.StdOut |_|  \___|\__, |_|___/\__|_|   \__, |
2018-03-22 12:50:51,605 INFO [NiFi logging handler] org.apache.nifi.registry.StdOut ==========|___/================|___/=
2018-03-22 12:50:51,605 INFO [NiFi logging handler] org.apache.nifi.registry.StdOut                v0.1.0.3.1.1.0-35
2018-03-22 12:50:51,605 INFO [NiFi logging handler] org.apache.nifi.registry.StdOut 
2018-03-22 12:50:56,380 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr Failed to start web server: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Validate failed: Detected failed migration to version 1.3 (DropBucketItemNameUniqueness)
2018-03-22 12:50:56,380 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr Shutting down...
2018-03-22 12:50:57,118 INFO [main] o.a.n.registry.bootstrap.RunNiFiRegistry NiFi Registry never started. Will not restart NiFi Registry 

Any ideas on this please "Error creating bean with name 'flywayInitializer'"

[#2]

@Wynand J van Vuuren I'm having the same problem. Any luck?

[#3]

Hi @Thomas Williams

The error seems to be caused by incorrect paths to the keystore.jks and or incorrect generation of the keystore.jks, I have my NiFi Registry switched off now, I'm trying to get Ranger and NiFi to talk to each other so that I can get Ranger to authenticate the NiFi users, it has been an uphill battle

Cheers

[#4]

The issue seems to be due to the error documented in the Registry Admin Guide (https://nifi.apache.org/docs/nifi-registry-docs/html/administration-guide.html#system-requirements) if you don't have a JDK installed:

When running Registry with only a JRE you may encounter the following error as Flyway (database migration tool) attempts to utilize a resource from the JDK:

java.lang.RuntimeException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Validate failed: Detected failed migration to version 1.3 (DropBucketItemNameUniqueness)

Try installing the  JDK , deleting the `database` directory that was created prior and then start the Registry.