Re: NiFi Registry - DatabaseFlowPersistenceProvider and GitFlowPersistenceProvider simultaniously

typo: so you can't run the DB and Git providers simultaneously. Le mar. 16 janv. 2024 à 18:08, Bryan Bende a écrit : > Hello, > > You can have only one persistence provider defined, so you can run the > DB and Git providers simultaneously. > > Thanks, > > Bryan > > On Tue, Jan 16, 2024 at 6:52 

Re: NiFi Registry - DatabaseFlowPersistenceProvider and GitFlowPersistenceProvider simultaniously

Hello, You can have only one persistence provider defined, so you can run the DB and Git providers simultaneously. Thanks, Bryan On Tue, Jan 16, 2024 at 6:52 AM Roman Wesołowski wrote: > > Hello, > > We would like to have 3 nodes cluster with Nfii Registry one for each > environment. So for

Re: Nifi - Content-repo on AWS-EBS volumes

I just switched a cluster using 3 EBS volumes for cont-repo from gp2 to gp3… resolved definite I/O throughput issues.  The change to gp3 was significant enough that I might actually reduce from 3 to 2 volumes, perhaps even a single volume would be sufficient. Of course every use case is

Re: Nifi - Content-repo on AWS-EBS volumes

Mark: Got it. Thank you for the help. Greg > On Dec 15, 2023, at 4:14 PM, Mark Payne wrote: > > Greg, > > Whether or not multiple content repos will have any impact depends very much > on where your system’s bottleneck is. If your bottleneck is disk I/O, it will > absolutely help. If your

Re: Nifi - Content-repo on AWS-EBS volumes

Greg, Whether or not multiple content repos will have any impact depends very much on where your system’s bottleneck is. If your bottleneck is disk I/O, it will absolutely help. If your bottleneck is CPU, it won’t. If, for example, you’re running on bare metal and have 48 cores on your machine

Re: Nifi - Content-repo on AWS-EBS volumes

Mark: I was just discussing multiple content repos on EBS volumes with a colleague. I found your post from a long time ago: https://lists.apache.org/thread/nq3mpry0wppzrodmldrcfnxwzp3n1cjv “Re #2: I don't know that i've used any SAN to back my repositories other than the EBS provided by

RE: [NIFI 1.23.2] Insecure Cipher Provider Algorithm

Hi Quentin, I've encountered similar errors in the past when trying to change the encryption algorithm. Here are two things that may help: 1. The password/key needs to be at least 12 characters long before you migrate to NIFI_PBKDF2_AES_GCM_256. If it is not, you have to first change the

Re: [NIFI 1.23.2] Insecure Cipher Provider Algorithm

Hi, I had the same issue changing the password and the cipher. It worked for me using the NiFi Toolkit and applying the operation onto both the flow.json.gz and the flow.xml.gz The documentation for the encrypt-config command is here:

Re: [NIFI 1.23.2] Insecure Cipher Provider Algorithm

Hi Quentin, I second these findings. I'm getting the same error on 1.23.2 using the same ciphers.   deb: 11   java: 17.0.7 Temurin Best, Lars On 23-12-13 14:58, Quentin HORNEMAN GUTTON wrote: Hello, I’m facing an issue after upgrading NiFi 1.13.2 to 1.23.2. I have a warn log with Insecure

Re: Nifi - Content-repo on AWS-EBS volumes

Hey Phil, NiFi will not spread the content of a single file over multiple partitions. It will write the content of FlowFile 1 to content repo 1, then write the next FlowFile to repo 2, etc. so it does round-robin but does not spread a single FlowFile across multiple repos. Thanks -Mark Sent

Re: NiFi custom extension and deploy phase on Maven

Exactly. The configuration on my pom. org.apache.nifi nifi-nar-bundles 1.23.2 Offering one without all ASF-isms, it can be nice also.. Thanks Le sam. 9 déc. 2023 à 19:03, Joe Witt a écrit : > Etienne, > > Are you using our nifi poms as your parent pom of your extensions? I do >

Re: NiFi custom extension and deploy phase on Maven

Etienne, Are you using our nifi poms as your parent pom of your extensions? I do wonder if perhaps we should offer one that doesn't tie to all our ASF-isms Thanks On Sat, Dec 9, 2023 at 10:54 AM Etienne Jouvin wrote: > Hello all; > > Since now, I never push my extensions to any Nexus or

Re: NIFI-REGISTRY Migration

ter in the registry_A, will be register in the same way in registry_B after migration ? Or needs we also use the URL aliasing ?   Regards    Envoyé: vendredi 29 septembre 2023 à 12:41 De: "Pierre Villard" À: users@nifi.apache.org Objet: Re: NIFI-REGISTRY Migration Hi, the  Y

Re: NIFI-REGISTRY Migration

À: users@nifi.apache.org Objet: Re: NIFI-REGISTRY Migration Hi, the  You could also consider using the recently added Toolkit CLI optihons to export all / import all from Registry A to B.   Pierre   Le ven. 29 sept. 2023 à 12:13, Lars Winderling <lars.winderl...@posteo.de> a écrit :

Re: NIFI-REGISTRY Migration

Hi, You could also consider using the recently added Toolkit CLI options to export all / import all from Registry A to B. Pierre Le ven. 29 sept. 2023 à 12:13, Lars Winderling a écrit : > Hi Minh, > > you could try to employ URL aliasing >

Re: NIFI-REGISTRY Migration

Hi Minh, you could try to employ URL aliasing as explained in the docs. This way, the registry will store only an alias instead of the actual registry address. When migrating to another host, make

Re: NiFi hanging during large sql query

The resolution was to manually paginate the query statement with the appropriate postgres syntax and set the fetchSize to 250 instead of 0, which is unlimited. On Mon, Sep 11, 2023 at 8:54 AM wrote: > > Hello Mike, > > Could you please give me the details about the resolution ? > Have you

Re: NiFi hanging during large sql query

  Hello Mike,   Could you please give me the details about the resolution ? Have you change something in the processor or just changing the sql command ?   Regards   Envoyé: samedi 2 septembre 2023 à 00:00 De: "Mike Thomsen" À: users@nifi.apache.org Objet: NiFi hanging during large sql

Re: [NIFI] ExecuteScript

Hello Quentin,   I also used the python with ExecuteScript but it is not native and not really supported.   The better thing it is use executeGroovy processor.   Minh     Envoyé: vendredi 8 septembre 2023 à 22:55 De: "Rafael Fracasso" À: users@nifi.apache.org Objet:

Re: NiFi OpenTelemetry JavaAgent

Hi Joe, Thanks for the fast response, I will circle back to this when I can (hopefully a week or 2) and update with what the root cause was if I can find it. There was no smoking gun in the app log as far as I can tell. In the meantime if anyone has success with this on their own I'd appreciate

Re: NiFi OpenTelemetry JavaAgent

Eric Any sign anything in the nifi app log? Did it perhaps run out of mem and hang? In general such agents should be fine. Thanks On Fri, Sep 8, 2023 at 6:15 PM Eric Secules wrote: > Hello, > > I have tried adding opentelemetry to NiFi by running the OpenTelemetry > javaagent ( >

Re: [NIFI] ExecuteScript

ress. > > -Jeremy Dyer > > Get Outlook for iOS <https://aka.ms/o0ukef> > -- > *From:* Rafael Fracasso > *Sent:* Friday, September 8, 2023 4:55:40 PM > *To:* users@nifi.apache.org > *Subject:* Re: [NIFI] ExecuteScript > > As far as

Re: [NIFI] ExecuteScript

for NiFi to address. -Jeremy Dyer Get Outlook for iOS<https://aka.ms/o0ukef> From: Rafael Fracasso Sent: Friday, September 8, 2023 4:55:40 PM To: users@nifi.apache.org Subject: Re: [NIFI] ExecuteScript As far as I know, you cannot use any external l

Re: [NIFI] ExecuteScript

As far as I know, you cannot use any external library on executescript, only the native one on jython env. But you can call native python to execute your script using executestreamcommand On Fri, Sep 8, 2023 at 6:15 AM Quentin HORNEMAN GUTTON < qhornemangut...@gmail.com> wrote: > Hello

Re: NiFi hanging during large sql query

I don't think so. On Sat, Sep 2, 2023 at 11:36 AM Mark Payne wrote: > Thanks for sharing the solution Mike. Is there something we need to update > in nifi to prevent this from biting others? > > Thanks > Mark > > Sent from my iPhone > > On Sep 2, 2023, at 9:48 AM, Joe Witt wrote: > >  > Nice.

Re: NiFi hanging during large sql query

When you said "fetchSize set low", I assume you mean non-zero, a zero will fetch all the rows at once. How did you paginate your query with ExecuteSQLRecord? I was going to suggest GenerateTableFetch in front to paginate the queries for you, but it definitely seems like we should be able to do or

Re: NiFi hanging during large sql query

Thanks for sharing the solution Mike. Is there something we need to update in nifi to prevent this from biting others? Thanks Mark Sent from my iPhone On Sep 2, 2023, at 9:48 AM, Joe Witt wrote:  Nice. Gald you found it. On Sat, Sep 2, 2023 at 5:07 AM Mike Thomsen

Re: NiFi hanging during large sql query

Nice. Gald you found it. On Sat, Sep 2, 2023 at 5:07 AM Mike Thomsen wrote: > It was the PostgreSQL JDBC driver. If you don't paginate the query > aggressively, it will try to load a significant chunk of the table into > memory rather than just pulling chunks, even with fetchSize set low. > >

Re: NiFi hanging during large sql query

It was the PostgreSQL JDBC driver. If you don't paginate the query aggressively, it will try to load a significant chunk of the table into memory rather than just pulling chunks, even with fetchSize set low. On Fri, Sep 1, 2023 at 6:01 PM Mike Thomsen wrote: > I have a three node cluster with

Re: NiFi-Registry GitFlowMetaData Error

Hello, I believe this issue [1] was just resolved yesterday and will be part of the upcoming 1.23.1 release that is being discussed. It was an incompatibility with the git library used by registry and the underlying ssh library used. Thanks, Bryan [1]

Re: NiFi not rolling logs

David, great recommendations, thanks! Best, Lars On 23-07-10 15:59, David Handermann wrote: It is worth noting that the totalSizeCap can be added at any time to an existing NiFi deployment, it is not necessary to wait for an updated release. Also related, the nifi-deprecation.log default

Re: NiFi not rolling logs

The totalcapsize feature will help a lot from what I’ve seen.Sent from my iPhoneOn Jul 8, 2023, at 9:26 AM, Lars Winderling wrote: Hi Mike,thanks for the advice. Our NiFi instances are running for week, if not months. Often times until the next update, so the startup option will bring much

Re: NiFi not rolling logs

Hi Mike, thanks for the advice. Our NiFi instances are running for week, if not months. Often times until the next update, so the startup option will bring much benefit, I fear, or am I mistaken. But looking forward to 1.23! On 8 July 2023 13:40:15 CEST, Mike Thomsen wrote: >Lars, > >You

Re: NiFi not rolling logs

Lars, You should also experiment with cleanHistoryOnStart. I did some experimentation this morning where I set the maxHistory to 1 (1 day vs the default of 30 which is 30 days), created a few fake log files from previous days and NiFi immediately cleared out those "old files" on startup. I have a

Re: NiFi not rolling logs

Dear NiFiers, we have been bugged so much by overflowing logfiles, and nothing has ever helped. I thought it was just my lack of skills...especially when NiFi has some issues and keeps on spilling stacktraces with high frequency to disk, it eats up space quickly. I have created cronjobs that

Re: NiFi not rolling logs

Hi Please have a look at this old jira: https://issues.apache.org/jira/browse/NIFI-2203 I have had issues where a processor create a log message ever 10ms resulting in the disk is being full. For me it seems like the maxHistory settings only effect how many files defined by the rolling patten to

Re: NiFi not rolling logs

Yeah, I'm working through some of it where I have time. I plan to have a Jira up this weekend. I'm wondering, though, if we shouldn't consider a spike for switching to log4j2 in 2.X because I saw a lot of complaints about logback being inconsistent in honoring its settings. On Fri, Jul 7, 2023 at

Re: NiFi not rolling logs

H. Interesting. Can you capture these bits of fun in a jira? Thanks On Fri, Jul 7, 2023 at 7:17 PM Mike Thomsen wrote: > After doing some research, it appears that is a wonky > setting WRT how well it's honored by logback. I let a GenerateFlowFile > > LogAttribute flow run for a long

Re: NiFi not rolling logs

Hi Mike, You aren't alone in experiencing this. I think logback uses a pattern matcher on filename to discover files to delete. If "something" happens which causes a gap in the date pattern, then the matcher will then fail to pick up and delete files on the other side of that gap. Regards, --

Re: Nifi Registry v1.22.0 - Unable to create buckets over http behind proxy

Ignore, I found the option is available after pressing the settings button. On Mon, Jun 19, 2023 at 11:04 PM Juan Pablo Gardella < gardellajuanpa...@gmail.com> wrote: > Hi, > > I am testing the nifi registry behind a proxy and it is unable to create > buckets. Last time I tested using v 1.14.0

RE: NiFi 1.19.1 - ExecuteSQL - Decimal Precision above 6 returns "OE-7"

still don’t know the real impact because we only detected two days ago, but yeah we started to force a type cast to string as a workaround. Thank you. Tiago Sebastião From: Isha Lamboo [mailto:isha.lam...@virtualsciences.nl] Sent: 19 de abril de 2023 15:10 To: users@nifi.apache.org Subject: RE

RE: NiFi 1.19.1 - ExecuteSQL - Decimal Precision above 6 returns "OE-7"

Hi Tiago, The content is not messed up but converted to scientific notation. This is valid in json and various other data formats. Apparently either the database or NiFi considers decimal(x,7) the point at which scientific notation is more suitable. Since you’re going to CSV format, you can

Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes issue

ays stop the processors, do the NiFi >> registry update and start the processors again. Very annoying as we have >> HTTP listeners which stop answering in that period. >> >> Cheers Josef >> >> >> From: Zahner Josef, GSB-LR-TRW-LI >> Date: Tue

Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes issue

and start the processors again. Very annoying as we have HTTP > listeners which stop answering in that period. > > Cheers Josef > > > From: Zahner Josef, GSB-LR-TRW-LI > Date: Tuesday, 13 December 2022 at 13:53 > To: users@nifi.apache.org > Subject: Re: NiFi 1.19.1 Regis

Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes issue

Subject: Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes issue Hi Bence I mentioned yesterday another issue which we thought would be solved after the upgrade steps. Sadly it happened again and after an investigation on our side it seems to be fully reproducible, I’ve opened

Re: NiFi 1.20.0 PutSFTP: SSH Client connection failed -> Timeout expired

NiFi handles SFTP we decided to restart and > upgrade our NAS to the newest firmware. In the last few hours the issue > happened only two times, but we will monitor it. It’s very likely that the > issue is or was related to our SFTP server and not to NiFi. > > > > Cheers

Re: NiFi 1.20.0 PutSFTP: SSH Client connection failed -> Timeout expired

users@nifi.apache.org Subject: Re: NiFi 1.20.0 PutSFTP: SSH Client connection failed -> Timeout expired Hi Josef, The FetchSFTP Processor implements some connection reuse, but GetSFTP, ListSFTP, and PutSFTP create a new connection for every invocation of the processor. I have considered a new appr

Re: NiFi 1.20.0 PutSFTP: SSH Client connection failed -> Timeout expired

Hi Josef, The FetchSFTP Processor implements some connection reuse, but GetSFTP, ListSFTP, and PutSFTP create a new connection for every invocation of the processor. I have considered a new approach SFTP components using a Controller Service with connection pooling, but it still requires some

Re: NiFi docker container fails to start on VMWare host

It was because of this: https://stackoverflow.com/questions/72841549/container-fails-to-start-insufficient-memory-for-the-java-runtime-environment-t#:~:text=Possible%20reasons%3A%20The%20system%20is,physical%20memory%20or%20swap%20space The customer had installed docker 18.xx, and we have not

Re: NiFi docker container fails to start on VMWare host

Have you tried an earlier version of nifi in the same environment? Does the image for nifi 1.18.0 boot successfully, for example? The reason I'd check this is mainly that the apache/nifi convenience docker image switched from java 8 to java 11 for nifi version 1.19.0+. I think the way in which

Re: NiFi docker container fails to start on VMWare host

Check the resources on the host. By default, the docker container will have all of the available memory on the host machine available to it. If you'd like to ensure that this available memory is at least X, you can use a memory reservation in your docker compose file: ``` ... mem_reservation:

Re: Nifi flowfile monitoring

Hi, We have a seven nodes cluster with 1.16.3. We haven't been able to reproduce it. We just know that only it happens in the same nodes of the cluster, but we havent seen any difference between them. All the processor groups have only one input port and one output port. We have single batch per

Re: Nifi flowfile monitoring

Hi, We should figure out why this happens as it should not. Which version are you using? Is it something you've been able to reproduce? How are flow files getting into the process group, and how are they going out? Multiple input ports? Multiple output ports? Also you configured "Batch" for the

Re: Nifi flowfile monitoring

Hi, Sometimes we have flowfiles stuck without reason in queues before out ports in consumer groups with batch output flowfile concurrency configured. We don't know why, and we haven't been able to find out where the problem is. So our operation teams has to check periodically, and change the

Re: NiFi failing to start

Russ and Chris, thank you for responding. I got this to work. It turned out to be a combination of different issues. One was finding the proper arguments for tls-toolkit so that my CN would be set properly in my certs. The second was configuration settings in my nifi.properties file. For that

Re: Nifi flowfile monitoring

I think it'd be good to take a step back. How can a flow file get stuck in a relationship? 1 - Is it because you have a self loop failure relationship? 2 - Is it because you have "dead ends" with a failure relationship going to a funnel? 3 - or is it because a flow file is failing and is being

Re: Nifi flowfile monitoring

Activate prometheus exporter and you will have a metric for number of objects in the queue > On 31. Dec 2022, at 07:08, nayan sharma wrote: > > Hi Users, > Is there anyway through which I can monitor or raise alert if any flow file > got stuck in nifi queue. > > For now operation team

Re: NiFi failing to start

In case you or someone else wishes only to run, develop, start, stop, start over, etc., and doesn't care to authenticate a (non-production) installation, I have followed this since NiFi 1.14 and last used it for 1.19: https://www.javahotchocolate.com/notes/nifi.html#20210716 If this doesn't

Re: NiFi failing to start

I think you will need to remove/comment out the references to single-user-provider in authorisers.xml and login-providers.xml as well as removing it from nifi.properties (see the comments in these files as they're provided in the nifi distributions). If you are using 2-way TLS authentication then

Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes issue

ilto:users@nifi.apache.org>" > mailto:users@nifi.apache.org>> > Date: Monday, 12 December 2022 at 16:40 > To: "users@nifi.apache.org" > Subject: Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes > issue > > Hi Josef, > >

Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes issue

details. It’s as well related to NiFi Registry nested flows… Thanks for taking care of it :-). Cheers Josef From: Simon Bence Reply to: "users@nifi.apache.org" Date: Monday, 12 December 2022 at 16:40 To: "users@nifi.apache.org" Subject: Re: NiFi 1.19.1 Registry Nested Process

Re: NiFi 1.19.1 Registry Nested Process Groups - Show Local Changes issue

Hi Josef, Thanks for the quick update! Meanwhile I tried to reproduce this situation but based on the known facts I was not able (Note: without any version change). I think it is connected to the version change indeed, but if you face with this ever again, please let me know! Regards, Bence

Re: NiFi 1.18.0 Sensitive Property broken after Upgrade

ers@nifi.apache.org> Subject: RE: NiFi 1.18.0 Sensitive Property broken after Upgrade *** ATENÇÃO: esta mensagem de e-mail tem origem externa! A cibersegurança é uma responsabilidade partilhada. Não aceda a links nem anexos de mensagens suspeitas ou inesperadas. CSIRT CGD *** __

RE: NiFi 1.18.0 Sensitive Property broken after Upgrade

[mailto:isha.lam...@virtualsciences.nl] Sent: 7 de dezembro de 2022 08:42 To: users@nifi.apache.org Subject: RE: NiFi 1.18.0 Sensitive Property broken after Upgrade *** ATENÇÃO: esta mensagem de e-mail tem origem externa! A cibersegurança é uma responsabilidade partilhada. Não aceda a links nem

RE: NiFi 1.18.0 Sensitive Property broken after Upgrade

be an easier fix. Regards, Isha Van: Tiago Luís Sebastião (DSI) Verzonden: dinsdag 6 december 2022 17:24 Aan: users@nifi.apache.org Onderwerp: RE: NiFi 1.18.0 Sensitive Property broken after Upgrade Hi Isha, I had already tried that and didn’t work also. But I tried the last thing I wrote

RE: NiFi 1.18.0 Sensitive Property broken after Upgrade

48 To: users@nifi.apache.org Subject: RE: NiFi 1.18.0 Sensitive Property broken after Upgrade *** ATENÇÃO: esta mensagem de e-mail tem origem externa! A cibersegurança é uma responsabilidade partilhada. Não aceda a links nem anexos de mensagens suspeitas ou inesperada

Re: NiFi Registry Bug which brakes the flow sync with NiFi 1.18.0 (and same version of the registry) on nested flows

ks a lot, So we will try to sync as less as possible. Let’s > hope that we will see a NiFi 1.19.1 soon… > > > > Cheers Josef > > > > *From: *Simon Bence > *Reply to: *"users@nifi.apache.org" > *Date: *Thursday, 1 December 2022 at 13:42 > *To: *"users

Re: NiFi Registry Bug which brakes the flow sync with NiFi 1.18.0 (and same version of the registry) on nested flows

Hi Bence Ok got it, thanks a lot, So we will try to sync as less as possible. Let’s hope that we will see a NiFi 1.19.1 soon… Cheers Josef From: Simon Bence Reply to: "users@nifi.apache.org" Date: Thursday, 1 December 2022 at 13:42 To: "users@nifi.apache.org" Subject: R

Re: NiFi Registry Bug which brakes the flow sync with NiFi 1.18.0 (and same version of the registry) on nested flows

red to change >> anything as it could brake anytime again. >> >> Cheers Josef >> >> >> >> From: Simon Bence > <mailto:simonbence@gmail.com>> >> Reply to: "users@nifi.apache.org <mailto:users@nifi.apache.org>" >>

Re: NiFi Registry Bug which brakes the flow sync with NiFi 1.18.0 (and same version of the registry) on nested flows

om: Simon Bence mailto:simonbence@gmail.com>> > Reply to: "users@nifi.apache.org <mailto:users@nifi.apache.org>" > mailto:users@nifi.apache.org>> > Date: Tuesday, 29 November 2022 at 13:31 > To: "users@nifi.apache.org" > Subject: Re: NiFi Registry Bug

Re: NiFi Registry Bug which brakes the flow sync with NiFi 1.18.0 (and same version of the registry) on nested flows

again. Cheers Josef From: Simon Bence Reply to: "users@nifi.apache.org" Date: Tuesday, 29 November 2022 at 13:31 To: "users@nifi.apache.org" Subject: Re: NiFi Registry Bug which brakes the flow sync with NiFi 1.18.0 (and same version of the registry) on nested flow

Re: NiFi Registry Bug which brakes the flow sync with NiFi 1.18.0 (and same version of the registry) on nested flows

Hi Josef, Thanks for your patience! I took a deeper look on what you were writing. In general, this is a sign for the case where the registry client cannot find the nested flow. As far as I understood in your case this happens when you are having a sync. Based on this you may be hitting

Re: NiFi Registry Bug which brakes the flow sync with NiFi 1.18.0 (and same version of the registry) on nested flows

Hi Josef, Thank you for raising the attention to this. The storageLocation is a new concept to generalise the information used to locate nested flows in a versioned flow. In general it can be there and does not cause issues, as of now NiFi falls back the previous way to locate nested flows.

RE: NiFi 1.18.0 Sensitive Property broken after Upgrade

) Verzonden: donderdag 24 november 2022 16:19 Aan: users@nifi.apache.org Onderwerp: RE: NiFi 1.18.0 Sensitive Property broken after Upgrade Hi again, Sorry for not following up but other priorities came ahead… Basically it’s still not working, I’ve tried several combinations and I still keep

RE: NiFi 1.18.0 Sensitive Property broken after Upgrade

e WARN. Sorry for the long email… Regards. Tiago Sebastião From: Tiago Luís Sebastião (DSI) Sent: 28 de outubro de 2022 09:48 To: users@nifi.apache.org<mailto:users@nifi.apache.org> Subject: RE: NiFi 1.18.0 Sensitive Property broken after Upgrade Hi David, It’s a standalone deploym

Re: Nifi unable to list/empty queue.

Hello, For access to data, because it’s considered more sensitive than the flow definition, both the user and the nifi node accessing the data must be granted permissions to view and modify data. Did you give the nodes permissions to view and modify data? Also moving this from security@ to

Re: NiFi component status history not showing more than a days worth of data

Hi Michael, I did not have time to take a deeper look on this, but I had a fix for cleanup related issues lately: https://github.com/apache/nifi/pull/6374 As for the size of the stored data, it might be perfectly normal. The amount of data primarily

RE: NiFi component status history not showing more than a days worth of data

Further investigation has shown that for the Node Status History, in order to get it working, I have had to disconnect 4 out of 6 nodes from the cluster in order to get any node level status history to be displayed without occurring a parse error. This seems to suggest the QuestDB

Re: Nifi with Nginx(ssl) reverse proxy

Thanks! On Tue, Nov 15, 2022 at 10:06 AM Ben .T.George wrote: > Hello, > > I have achieved this with nginx - reverse proxy method. > > Regards, > Ben > > On Sun, Nov 13, 2022 at 7:22 PM Ben .T.George > wrote: > >> Hello, >> >> i have a nifi instance running fine on port 8443, i would like to

Re: Nifi with Nginx(ssl) reverse proxy

Hello, I have achieved this with nginx - reverse proxy method. Regards, Ben On Sun, Nov 13, 2022 at 7:22 PM Ben .T.George wrote: > Hello, > > i have a nifi instance running fine on port 8443, i would like to > configure SSL and configureit to listen on 443, > > i was trying to do that with

Re: NiFi on AWS EC2

I used the command docker exec -it nifi /bin/bash to review what I understand to be the nifi directories and config files in the container. I notice nifi in the container is in many ways not configured to Apache NiFi recommendations for optimal performance. For example, the nifi.properties repo

Re: NiFi on AWS EC2

Jim, You're welcome! Thanks for following up and confirming the solution, great collaborative effort! Regard, David Handermann On Tue, Nov 8, 2022, 7:25 PM James McMahon wrote: > That was it. Adding the port to the docker run command proxy got me to the > promised land. I was then able to

Re: NiFi on AWS EC2

That was it. Adding the port to the docker run command proxy got me to the promised land. I was then able to use the userid and password from the docker log to access nifi on my ec2 instance. David, Dmitry - thank you so much. This was a huge help to me, and I hope it will help others trying the

Re: NiFi on AWS EC2

Yes sir, I did. I used the full public domain name. On Tue, Nov 8, 2022 at 8:08 PM Dmitry Stepanov wrote: > Make sure you use your full domain name > ec2-3-238-27-220.compute-1.amazonaws.com > David shorten it in his code > > On November 8, 2022 5:57:26 p.m. James McMahon > wrote: > >> Thank

Re: NiFi on AWS EC2

It may also be necessary to include the port in the host variable: docker run --name nifi -p 8443:8443 -e NIFI_WEB_PROXY_HOST= ec2-3-238-27-220.compute-1.amazonaws.com:8443 -d apache/nifi:latest It is possible to access the configuration and logs files using an interactive shell with the

Re: NiFi on AWS EC2

Make sure you use your full domain name ec2-3-238-27-220.compute-1.amazonaws.com David shorten it in his code On November 8, 2022 5:57:26 p.m. James McMahon wrote: Thank you, David. I’ve made that change, adding the proxy host specification on the docker command line. I continue to get the

Re: NiFi on AWS EC2

Thank you, David. I’ve made that change, adding the proxy host specification on the docker command line. I continue to get the same error message. Is it possible I need to indicate my key on the docker command line too? Related, how can one access nifi.properties and the usual nifi config files,

Re: NiFi on AWS EC2

Hi Jim, Good adjustment on the security group inbound rules. The error page is the result of NiFi receiving an unexpected HTTP Host header, not matching one of the expected values. For this to work, it is possible to pass the external DNS name as the value of the NIFI_WEB_PROXY_HOST environment

Re: NiFi on AWS EC2

Hi David. This is very helpful, thank you. I feel like I am close, but I get an error. My Inbound Rules for my security group now include: 8443 TCP (MyIP)/32 443 TCP (MyIP)/32 22 TCP (MyIP)/32 In my browser - I tried both Edge and Chrome - I use this URL:

Re: NiFi on AWS EC2

> won't render if you're using Edge or IE to access. The old, discontinued Edge had that problem, but Edge has worked just fine for the last 2 years or so since it was redone on top of Chromium. IMO if you're going to use Chromium with NiFi, the best experience seems to be Brave. On Tue, Nov 8,

Re: NiFi on AWS EC2

Hi Jim, Thanks for the reply and additional background. The instructions are dated March 2021, which is prior to the release of NiFi 1.14.0. In particular, the run command is no longer accurate with the default NiFi container image. The current Docker Hub instructions [1] show the basic command

Re: NiFi on AWS EC2

Hi and thank you, David and Dmitry. In my case I was following this example, https://joeygoksu.com/software/apache-nifi-on-aws/ which results in NiFi installed within a container. So to answer one of your questions, I don’t yet know how or where to find nifi.properties in the container

Re: NiFi on AWS EC2

In addition to the other suggestions, the last time I checked, the HTML5 of the NiFi interface won't render if you're using Edge or IE to access.  Brave, Chrome, Firefox etc will work, however. On 11/8/2022 1:53 PM, James McMahon wrote: Has anyone successfully configured NiFi on AWS, and

Re: NiFi on AWS EC2

We did. Since NiFi is HTTPS by default (recent versions) you need to open ports 8443 or 443(default HTTPS) Try opening those and see what happens Cheers, Dima Stepanov

Re: NiFi on AWS EC2

Hi Jim, NiFi 1.14.0 and following default to HTTPS on port 8443, listening on the localhost address. The nifi.web.https.host can be changed to blank in order to listen on all interfaces, but the default HTTPS setting with authenticated required should be retained. Can you provide the version of

Re: NiFi Registry Event Logging - Missing User Principal on Some Events

I’ll start a ticket and try and get a PR submitted this week. Thanks Shawn > On Nov 1, 2022, at 8:05 AM, Bryan Bende wrote: > > Seems like it was just missed in here: > >

Re: nifi-api with a server secured with Microsoft AD

Hi David It's also possible to configure authorizers.xml to both handle LDAP and local users (file-access) so you can have both. It's using composite-configurable-user-group-provider. Just remember that nifi is case sentitive, so the what you specify as the user, should match exactly what nifi

Re: nifi-api with a server secured with Microsoft AD

Mike and Shawn, thanks for the feedback, have not had a chance to try either, but appreciate your help. Will be trying the cert this week, will reach out to the AD managers about a more direct AD solution. Dave On Sat, Oct 29, 2022 at 7:10 PM Mike Thomsen wrote: > David, > > Another option

Re: NiFi Registry Event Logging - Missing User Principal on Some Events

Seems like it was just missed in here: https://github.com/apache/nifi/blob/main/nifi-registry/nifi-registry-core/nifi-registry-framework/src/main/java/org/apache/nifi/registry/event/EventFactory.java No JIRA that I know of. On Mon, Oct 31, 2022 at 10:58 AM Shawn Weeks wrote: > > I’m running

Re: nifi-api with a server secured with Microsoft AD

David, Another option you might want to explore is having AD generate client certificates for your users. On Sat, Oct 29, 2022 at 12:01 PM Shawn Weeks wrote: > > NiFi should always accept a cert at the rest api if you provide one. If your > using curl just add the “--key” and “--cert” and call

  1   2   3   4   5   6   7   8   9   10   >