Re: Azure Event Hub Processors Upgrade Problem

[Mark Payne]

Hey Sunny,

Very happy to have your help! Thanks! Sorry it wasn't more obvious how to 
connect remotely. What you'll want to do is to update the "bootstrap.conf" file 
in the conf/ directory. On or around line 39, you'll see the following line:

#java.arg.debug=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000

You'll want to un-comment that line and restart. Then, you'll be able to attach 
to NiFi remotely from within IntelliJ, connecting to localhost on port 8000. Of 
course, you can change the port if you want from 8000 to whatever makes more 
sense for you.

Hopefully this clears things up but if you have any more questions, or if I 
didn't clarify things, please do let us know!

Thanks
-Mark


> On Aug 20, 2019, at 7:58 PM, Sunny Zhang  
> wrote:
> 
> Hi there,
> 
> I'm a dev from Microsoft Azure Event Hub team. We noticed that the Azure 
> Event Hub processors on Nifi is using an very old version and may cause 
> usability problems to the users. We want to help to upgrade it to the newest 
> version!
> 
> However, I met some problem trying to debug with the project with IntelliJ 
> IDE. I can build-run the code with command lines, read log when exception 
> happens, and I can successfully opened the project in IntelliJ and edit, but 
> I'm not sure how to run and debug the project in IntelliJ. More specifically, 
> we wanna attach the running Nifi (http://localhost:8080/nifi/) with the IDE 
> so that we can have breakpoints, check runtime value without having to print 
> variables to log (but we didn't find a way yet). We wanna ensure the quality, 
> so we want to do enough testing etc, so we hope to work on debugging more 
> effectively.
> 
> Could you help to explain how to work on the project with IntelliJ, or is 
> there any good ways?
> 
> Best,
> Sunny
> 

Azure Event Hub Processors Upgrade Problem

[Sunny Zhang]

Hi there,

I'm a dev from Microsoft Azure Event Hub team. We noticed that the Azure Event 
Hub processors on Nifi is using an very old version and may cause usability 
problems to the users. We want to help to upgrade it to the newest version!

However, I met some problem trying to debug with the project with IntelliJ IDE. 
I can build-run the code with command lines, read log when exception happens, 
and I can successfully opened the project in IntelliJ and edit, but I'm not 
sure how to run and debug the project in IntelliJ. More specifically, we wanna 
attach the running Nifi (http://localhost:8080/nifi/) with the IDE so that we 
can have breakpoints, check runtime value without having to print variables to 
log (but we didn't find a way yet). We wanna ensure the quality, so we want to 
do enough testing etc, so we hope to work on debugging more effectively.

Could you help to explain how to work on the project with IntelliJ, or is there 
any good ways?

Best,
Sunny

Re: nifi deploy automation - variables pass through (incl controller services)

[sivasankar Reddy]

Hi Bryan, 

Thanks for your input. I would like to know more 

1. how does CLI pg-import  works if already canvas has 100 to 150 flows. Will 
CLI pg-import always place the flow in canvas which can be easily located. As 
nipyapi has location(x,y) during deploy flow. 

2. From enterprise usage, do you recommend toolkit CLI vs nipyapi, it seems 
toolkit CLI is part of official Nifi. 

Any other points regarding this will be helpful. 

Regards,
Siva 

On 2019/08/08 22:41:43, Bryan Bende  wrote: 
> Hello,
> 
> A lot depends on whether you are doing the promotion with the UI or
> with scripts using something like NiFi CLI or NiPyApi.
> 
> 1) Currently references to controller services outside the versioned
> process group need to be set after initial import. In the next release
> it will auto-select by name as long as there is only one service with
> the given name and type in a parent group (name is not unique).
> 
> 2) The snapshot of the variables are part of the versioned flow, so
> after importing you would have to set the new values in the target
> environment. This can be done in the UI or with scripts.
> 
> 3) The REST API allows for positioning of any component that is
> created. i can't speak for how to do it with NiPyApi, but I know the
> CLI pg-import command attempts to automatically organize the imported
> process groups on the root canvas so that they don't overlap.
> 
> Thanks,
> 
> Bryan
> 
> On Thu, Aug 8, 2019 at 4:32 PM sivasankar Reddy  wrote:
> >
> > Hi,
> >
> > We are looking for nifi deploy automation from regsitry -> higher nifi 
> > instance. Quick observations during intial evaluation.
> >
> > 1. After process group import, controller services are not set in nifi 
> > instance
> > 2. How to set variables from source process group to destination process 
> > group.
> > 3. Is there any possibility of definining the positioning of process group 
> > to be imported in Nifi Canvas.
> >
> > Any other best practices  regarding NiFi deployment automation will be 
> > helpful.
> >
> > Thanks in Advance!
> >
> 

Re: [DISCUSS] NiFi Registry 0.5.0 release

[Bryan Bende]

A few final items have been merged, including the Knox work referenced
earlier, as well as the FDS upgrade, and a few improvements to support
the parameter work on NiFi side.

There is one last PR with some dependency upgrades that would be good
to get in, and it looks like its close, so we'll see if we can get
that in.

Hoping to possibly kick out an RC some time tomorrow.

On Sun, Aug 11, 2019 at 3:49 PM Mike Thomsen  wrote:
>
> No, we're running NiFi 1.8 and Registry 0.4
>
> On Sun, Aug 11, 2019 at 11:20 AM Bryan Bende  wrote:
>
> > There shouldn’t be... 0.5.0 shouldn’t be too much different than 0.4.0,
> > just a few improvements and a couple of fixes that NiFi needs from the
> > released registry artifacts.
> >
> > Are you running NiFi 1.8 with registry 0.4?
> >
> > On Sat, Aug 10, 2019 at 11:19 AM Mike Thomsen 
> > wrote:
> >
> > > Are there any incompatibilities expected between this release and NiFi
> > 1.8?
> > > We're not planning on upgrading until 1.10 at the earliest.
> > >
> > > Thanks,
> > >
> > > Mike
> > >
> > > On Sat, Aug 10, 2019 at 8:48 AM Denes Arvay  wrote:
> > >
> > > > There's an ongoing initiative to add Knox proxy support to NiFi
> > Registry
> > > > [1]. It might involve Knox changes too [2], so I don't know how
> > > complicated
> > > > it is, but it'd be good if that could go to the release as well.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/NIFIREG-295
> > > > [2] https://issues.apache.org/jira/browse/KNOX-1952
> > > >
> > > > Regards,
> > > > Denes
> > > >
> > > > On Sat, Aug 10, 2019 at 2:25 PM Kevin Doran  wrote:
> > > >
> > > > > Thanks for kicking off this discussion thread, Bryan. I agree we are
> > > > > reaching a good point to start preparing a release candidate. I see a
> > > > > few PRs up, I'll go through those and if any are close will get them
> > > > > merged prior to a RC.
> > > > >
> > > > > If anyone else wants to submit a PR in the next week or so I am also
> > > > > happy to review them.
> > > > >
> > > > > On Fri, Aug 9, 2019 at 12:25 PM Bryan Bende 
> > wrote:
> > > > > >
> > > > > > That would be a nice addition, although it doesn't look like anyone
> > > is
> > > > > > actively working on it.
> > > > > >
> > > > > > If someone is able to tackle it and get a PR up in the next week,
> > I'd
> > > > > > be happy to review it.
> > > > > >
> > > > > > On Fri, Aug 9, 2019 at 12:07 PM Mark Bean 
> > > > wrote:
> > > > > > >
> > > > > > > I'd like to see NIFIREG-177 included in the next release. It
> > seems
> > > > > like a
> > > > > > > fairly simple addition, but I have not had time to dig in; I'm
> > not
> > > > > familiar
> > > > > > > with modifying the UI. I hope someone knowledge of the UI could
> > > knock
> > > > > this
> > > > > > > out fairly quickly?
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/NIFIREG-177
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Aug 8, 2019 at 7:01 PM Bryan Bende 
> > > wrote:
> > > > > > >
> > > > > > > > It looks like we are close to wrapping up the remaining items
> > for
> > > > an
> > > > > > > > 0.5.0 release. There is one open PR that integrates the latest
> > > FDS
> > > > > > > > release into the UI which looks like it is close to getting in.
> > > > Once
> > > > > > > > that wraps up I think we can get an RC out. I'm happy to
> > perform
> > > RM
> > > > > > > > duties.
> > > > > > > >
> > > > >
> > > >
> > >
> > --
> > Sent from Gmail Mobile
> >

Re: Re:[EXT] [DISCUSS] Predictive Analytics for NiFi Metrics

[Andy Christianson]

Hi Rob,

Thanks for the UI PR. Taking a look.

-Andy

‐‐‐ Original Message ‐‐‐
On Tuesday, August 20, 2019 10:04 AM, Robert Fellows  
wrote:

> Mark and Yolanda,
> I submitted the PR I mentioned yesterday for the UI changes that surface
> the exposed prediction data. Let me know what you think.
>
> https://github.com/apache/nifi/pull/3660
>
> Thanks,
> Rob
>
> On Mon, Aug 19, 2019 at 4:17 PM Yolanda Davis yolanda.m.da...@gmail.com
> wrote:
>
> > Hi Mark and Rob
> > Mark thanks so much for the info on your work and Rob thanks for jumping in
> > on the UI! I just wanted to add, Mark, that looking at your branch I think
> > we also may have some opportunities to exchange notes or collaborate on the
> > backend as well. The work in the feature branch is still in progress (with
> > some decoupling to ensure we can allow flexible configuration of models).
> > Please feel free to review and leave comments under the parent JIRA. At
> > the same time I'll take a deeper dive on your branch and perhaps we can
> > exchange notes on potential areas for improvement/collaboration if it makes
> > sense?
> > Thanks Again,
> > -yolanda
> > On Mon, Aug 19, 2019 at 3:34 PM Robert Fellows rob.fell...@gmail.com
> > wrote:
> >
> > > Hey Mark,
> > > I've started working on some UI based on the initial commit for this
> > > proposal. What you have done and what I am working on have a bit of
> > > overlap, but not much.
> > > I'm working on getting the predicted count and bytes into the existing
> > > connection metric display that is already on the canvas. The only overlap
> > > looks like it might be in the
> > > Summary table. I plan on adding a PR for my additions hopefully tomorrow.
> > > Maybe once it is up we can discuss how we bring the them together where
> > > it
> > > makes sense?
> > > This is the main JIRA case:
> > > https://issues.apache.org/jira/browse/NIFI-6510
> > > And this is the subtask that I am working toward:
> > > https://issues.apache.org/jira/browse/NIFI-6568
> > > -- Rob Fellows
> > > On Mon, Aug 19, 2019 at 2:26 PM Owens, Mark jmow...@evoforge.org
> > > wrote:
> > >
> > > > The images from the preview email do not appear to be displaying. They
> > > > can
> > > > be viewed at:
> > > > https://github.com/jmark99/nifi-images
> > > > From: Owens, Mark jmow...@evoforge.org
> > > > Sent: Monday, August 19, 2019 2:25 PM
> > > > To: dev@nifi.apache.org
> > > > Subject: RE: Re:[EXT] [DISCUSS] Predictive Analytics for NiFi Metrics
> > > > Hi Yolanda,
> > > > I've been working on a feature that appears to possibly overlap with
> > > > the
> > >
> > > > work you are pursuing. Perhaps we should see if/should we try to
> > > > coordinate
> > > > our efforts. I've been updating NiFi to predict the time to queue
> > > > overflow
> > > > for both flowfiles and bytes and displaying that information in the
> > > > GUI.
> > >
> > > > For the initial attempt, I’ve been using a simple model of straight
> > > > line
> > >
> > > > prediction over a sliding window of 15 minutes to predict when flows
> > > > will
> > >
> > > > fail. This estimate is then displayed on both the NiFi Summary page
> > > > under
> > >
> > > > the connections tab and in the status history graphs. Below are
> > > > examples
> > >
> > > > of what would be displayed to the user.
> > > > [cid:image001.png@01D55696.E4CCD550]
> > > > The Connection tab contains a new column on the right that displays the
> > > > prediction for both flow files and data size. The user can select a
> > > > maximum
> > > > time at which specific times are no longer displayed. In this example,
> > > > if
> > >
> > > > the prediction lies beyond 12 hours then the display simply indicates
> > > > that
> > > > the flow is greater than 12 hours away from failure at the moment.
> > > > [cid:image002.png@01D55697.2C8AC500]
> > > > This display graphs the prediction for byte overflow over time. Note
> > > > that
> > >
> > > > if the estimate is greater than the user provided maximum value of
> > > > interest
> > > > the graph maxes out at that time, effectively indicating no overflow
> > > > concerns.
> > > > [cid:image003.png@01D55697.965C27D0]
> > > > A similar display for flowfile count is displayed as well.
> > > > The current state of work can be found at
> > > > https://github.com/jmark99/nifi/tree/time-to-overflow
> > > > I welcome your (or any others) feedback on this effort.
> > > > Thanks,
> > > > Mark
> > > > P.S. If the images are not displaying, they can be viewed at
> > > > https://github.com/jmark99/nifi-images
> > > > -Original Message-
> > > > From: Yolanda Davis  > > > yolanda.m.da...@gmail.com>>
> > > > Sent: Monday, August 19, 2019 11:29 AM
> > > > To: dev@nifi.apache.orgmailto:dev@nifi.apache.org
> > > > Subject: Re:[EXT] [DISCUSS] Predictive Analytics for NiFi Metrics
> > > > Hello All,
> > > > I just wanted to follow up on the discussion we started a couple of
> > > > weeks
> > >
> > > > ago concerning an analytics framework for NiFi metrics. 

Re: Re:[EXT] [DISCUSS] Predictive Analytics for NiFi Metrics

[Robert Fellows]

Mark and Yolanda,
  I submitted the PR I mentioned yesterday for the UI changes that surface
the exposed prediction data. Let me know what you think.

https://github.com/apache/nifi/pull/3660

Thanks,
Rob


On Mon, Aug 19, 2019 at 4:17 PM Yolanda Davis 
wrote:

> Hi Mark and Rob
>
> Mark thanks so much for the info on your work and Rob thanks for jumping in
> on the UI! I just wanted to add, Mark, that looking at your branch I think
> we also may have some opportunities to exchange notes or collaborate on the
> backend as well.  The work in the feature branch is still in progress (with
> some decoupling to ensure we can allow flexible configuration of models).
> Please feel free to review and leave comments under the parent JIRA.  At
> the same time I'll take a deeper dive on your branch and perhaps we can
> exchange notes on potential areas for improvement/collaboration if it makes
> sense?
>
> Thanks Again,
>
> -yolanda
>
>
> On Mon, Aug 19, 2019 at 3:34 PM Robert Fellows 
> wrote:
>
> > Hey Mark,
> >   I've started working on some UI based on the initial commit for this
> > proposal. What you have done and what I am working on have a bit of
> > overlap, but not much.
> > I'm working on getting the predicted count and bytes into the existing
> > connection metric display that is already on the canvas. The only overlap
> > looks like it might be in the
> > Summary table. I plan on adding a PR for my additions hopefully tomorrow.
> > Maybe once it is up we can discuss how we bring the them together where
> it
> > makes sense?
> >
> > This is the main JIRA case:
> > https://issues.apache.org/jira/browse/NIFI-6510
> > And this is the subtask that I am working toward:
> > https://issues.apache.org/jira/browse/NIFI-6568
> >
> >
> > -- Rob Fellows
> >
> > On Mon, Aug 19, 2019 at 2:26 PM Owens, Mark 
> wrote:
> >
> > > The images from the preview email do not appear to be displaying. They
> > can
> > > be viewed at:
> > > https://github.com/jmark99/nifi-images
> > >
> > > From: Owens, Mark 
> > > Sent: Monday, August 19, 2019 2:25 PM
> > > To: dev@nifi.apache.org
> > > Subject: RE: Re:[EXT] [DISCUSS] Predictive Analytics for NiFi Metrics
> > >
> > >
> > > Hi Yolanda,
> > >
> > >
> > >
> > > I've been working on a feature that appears to possibly overlap with
> the
> > > work you are pursuing. Perhaps we should see if/should we try to
> > coordinate
> > > our efforts. I've been updating NiFi to predict the time to queue
> > overflow
> > > for both flowfiles and bytes and displaying that information in the
> GUI.
> > > For the initial attempt, I’ve been using a simple model of straight
> line
> > > prediction over a sliding window of 15 minutes to predict when flows
> will
> > > fail. This estimate is then displayed on both the NiFi Summary page
> under
> > > the connections tab and in the status history graphs.  Below are
> examples
> > > of what would be displayed to the user.
> > >
> > >
> > >
> > > [cid:image001.png@01D55696.E4CCD550]
> > >
> > >
> > >
> > > The Connection tab contains a new column on the right that displays the
> > > prediction for both flow files and data size. The user can select a
> > maximum
> > > time at which specific times are no longer displayed. In this example,
> if
> > > the prediction lies beyond 12 hours then the display simply indicates
> > that
> > > the flow is greater than 12 hours away from failure at the moment.
> > >
> > >
> > >
> > > [cid:image002.png@01D55697.2C8AC500]
> > >
> > >
> > >
> > > This display graphs the prediction for byte overflow over time. Note
> that
> > > if the estimate is greater than the user provided maximum value of
> > interest
> > > the graph maxes out at that time, effectively indicating no overflow
> > > concerns.
> > >
> > >
> > >
> > > [cid:image003.png@01D55697.965C27D0]
> > >
> > >
> > >
> > > A similar display for flowfile count is displayed as well.
> > >
> > >
> > >
> > > The current state of work can be found at
> > > https://github.com/jmark99/nifi/tree/time-to-overflow
> > >
> > >
> > >
> > > I welcome your (or any others) feedback on this effort.
> > >
> > >
> > >
> > > Thanks,
> > > Mark
> > >
> > >
> > >
> > > P.S. If the images are not displaying, they can be viewed at
> > > https://github.com/jmark99/nifi-images
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > -Original Message-
> > > From: Yolanda Davis  > > yolanda.m.da...@gmail.com>>
> > > Sent: Monday, August 19, 2019 11:29 AM
> > > To: dev@nifi.apache.org
> > > Subject: Re:[EXT] [DISCUSS] Predictive Analytics for NiFi Metrics
> > >
> > >
> > >
> > > Hello All,
> > >
> > >
> > >
> > > I just wanted to follow up on the discussion we started a couple of
> weeks
> > > ago concerning an analytics framework for NiFi metrics.  Working with
> > Andy
> > > Christianson and Matt Burgess we shaped our ideas and drafted a
> proposal
> > > for this feature on the Apache NiFi Wiki [1] . We've also begun
> > > implementing some of these ideas in a 

Re: Restore nifi after /database_repository/ folder being cleared

[Endre Kovács]

Hi,

I think the problem is that the path:


/disk_r5_01/nifi-1.7.1/database_repository/nifi-user-keys.lock.db


is not writable by the user running NiFi.

this database holds the keys which can verify the bearer / jwt token,
passed by each, authenticated client request.

Best regards,
Endre


On Tue, Aug 20, 2019, 12:37 PM Кочетов Николай Александрович <
na.koche...@severstal.com> wrote:

> Hello, guys and girls!
>
> Could you kindly help me to restore my nifi instance and get it up and
> running again after the content of the nifi/database_repository/ folder was
> being removed?
> Now, while I'm trying to start it I'm getting the error
> (nifi-bootstrap.log):
>
> 2019-08-19 18:55:32,970 ERROR [NiFi logging handler]
> org.apache.nifi.StdErr Failed to start web server: Error creating bean with
> name
> 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration':
> Unsatisfied dependency expressed through method
> 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is
> org.springframework.beans.factory.BeanExpressionException: Expression
> parsing failed; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied
> dependency expressed through method 'setJwtAuthenticationProvider'
> parameter 0; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'jwtAuthenticationProvider' defined in class path resource
> [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'jwtService' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'jwtService' defined in class path resource
> [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'keyService' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'keyService' defined in class path resource
> [nifi-administration-context.xml]: Cannot resolve reference to bean
> 'keyTransactionBuilder' while setting bean property 'transactionBuilder';
> nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'keyTransactionBuilder' defined in class path resource
> [nifi-administration-context.xml]: Cannot resolve reference to bean
> 'keyDataSource' while setting bean property 'dataSource'; nested exception
> is org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'keyDataSource': FactoryBean threw exception on object
> creation; nested exception is org.h2.jdbc.JdbcSQLException: Error opening
> database: "Could not save properties
> /disk_r5_01/nifi-1.7.1/database_repository/nifi-user-keys.lock.db"
> [8000-176]
>
> And quite a long stacktrace in nifi.app.log:
>
> 2019-08-19 18:55:32,971 WARN [main] org.apache.nifi.web.server.JettyServer
> Failed to start web server... shutting down.
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration':
> Unsatisfied dependency expressed through method
> 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is
> org.springframework.beans.factory.BeanExpressionException: Expression
> parsing failed; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied
> dependency expressed through method 'setJwtAuthenticationProvider'
> parameter 0; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'jwtAuthenticationProvider' defined in class path resource
> [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'jwtService' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'jwtService' defined in class path resource
> [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'keyService' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'keyService' defined in class path resource
> [nifi-administration-context.xml]: Cannot resolve reference to bean
> 'keyTransactionBuilder' while setting bean property 'transactionBuilder';
> nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'keyTransactionBuilder' defined in class path resource
> [nifi-administration-context.xml]: Cannot resolve reference to bean
> 'keyDataSource' while setting bean property 'dataSource'; nested exception
> is 

Restore nifi after /database_repository/ folder being cleared

[Кочетов Николай Александрович]

Hello, guys and girls!

Could you kindly help me to restore my nifi instance and get it up and running 
again after the content of the nifi/database_repository/ folder was being 
removed?
Now, while I'm trying to start it I'm getting the error (nifi-bootstrap.log):

2019-08-19 18:55:32,970 ERROR [NiFi logging handler] org.apache.nifi.StdErr 
Failed to start web server: Error creating bean with name 
'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration':
 Unsatisfied dependency expressed through method 
'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is 
org.springframework.beans.factory.BeanExpressionException: Expression parsing 
failed; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': 
Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' 
parameter 0; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'jwtAuthenticationProvider' defined in class path resource 
[nifi-web-security-context.xml]: Cannot resolve reference to bean 'jwtService' 
while setting constructor argument; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'jwtService' defined in class path resource 
[nifi-web-security-context.xml]: Cannot resolve reference to bean 'keyService' 
while setting constructor argument; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'keyService' defined in class path resource 
[nifi-administration-context.xml]: Cannot resolve reference to bean 
'keyTransactionBuilder' while setting bean property 'transactionBuilder'; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'keyTransactionBuilder' defined in class path 
resource [nifi-administration-context.xml]: Cannot resolve reference to bean 
'keyDataSource' while setting bean property 'dataSource'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'keyDataSource': FactoryBean threw exception on object creation; 
nested exception is org.h2.jdbc.JdbcSQLException: Error opening database: 
"Could not save properties 
/disk_r5_01/nifi-1.7.1/database_repository/nifi-user-keys.lock.db" [8000-176]

And quite a long stacktrace in nifi.app.log:

2019-08-19 18:55:32,971 WARN [main] org.apache.nifi.web.server.JettyServer 
Failed to start web server... shutting down.
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 
'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration':
 Unsatisfied dependency expressed through method 
'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is 
org.springframework.beans.factory.BeanExpressionException: Expression parsing 
failed; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': 
Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' 
parameter 0; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'jwtAuthenticationProvider' defined in class path resource 
[nifi-web-security-context.xml]: Cannot resolve reference to bean 'jwtService' 
while setting constructor argument; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'jwtService' defined in class path resource 
[nifi-web-security-context.xml]: Cannot resolve reference to bean 'keyService' 
while setting constructor argument; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'keyService' defined in class path resource 
[nifi-administration-context.xml]: Cannot resolve reference to bean 
'keyTransactionBuilder' while setting bean property 'transactionBuilder'; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'keyTransactionBuilder' defined in class path 
resource [nifi-administration-context.xml]: Cannot resolve reference to bean 
'keyDataSource' while setting bean property 'dataSource'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'keyDataSource': FactoryBean threw exception on object creation; 
nested exception is org.h2.jdbc.JdbcSQLException: Error opening database: 
"Could not save properties 
/disk_r5_01/nifi-1.7.1/database_repository/nifi-user-keys.lock.db" [8000-176]
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredMethodElement.inject(AutowiredAnnotationBeanPostProcessor.java:667)
at