[ 
https://issues.apache.org/jira/browse/NIFIREG-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358548#comment-16358548
 ] 

Bryan Bende commented on NIFIREG-142:
-------------------------------------

[~doaks80] sorry for the troubles here, can you try deleting the 'database' 
directory in the directory and then starting again?

It should get created relative to the base directory for NiFi registry:
{code:java}
ls -1
LICENSE
NOTICE
README
bin
conf
database
docs
flow_storage
lib
logs
run
work{code}
I'm hoping that the H2 database is just in some bad state from the first failed 
start, and by wiping it out it will start from scratch and hopefully work since 
you have the JDK now.

> First start problem: Error creating bean with name 'flywayInitializer'
> ----------------------------------------------------------------------
>
>                 Key: NIFIREG-142
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-142
>             Project: NiFi Registry
>          Issue Type: Bug
>    Affects Versions: 0.1.0
>         Environment: RHEL7
> openjdk version "1.8.0_161"
>            Reporter: Daniel Oakley
>            Priority: Major
>         Attachments: nifi-registry-app.log, nifi-registry-bootstrap.log
>
>
> Downloaded 0.1.0 tarball and and tried to run on RHEL7. No changes to any 
> config files.
> Error in log file was:
> 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)
> I could not find anything about "flyway" in the docs or config files...any 
> hints on how to get around this problem?
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to