Re: NiFi Registry metadata DB lost data, can we restore from disk?

and apologies for the full email signature... Dave On Tue, Jul 30, 2024 at 12:49 PM David Early wrote: > I am going to answer my own question. > > Yes, you can for a default H2 database, at least we have not had a > catastrophic error since doing the following. > > - > In our

Re: NiFi Registry metadata DB lost data, can we restore from disk?

I am going to answer my own question. Yes, you can for a default H2 database, at least we have not had a catastrophic error since doing the following. - In our case, all the flows were still in flow_storage AND nothing was lost and the buckets were still defined in the H2

Re: ConsumeJMS concurrent tasks

Thank you Mike. I created a ticket to add documentation for this to the processor: https://issues.apache.org/jira/browse/NIFI-13597 > On Jul 29, 2024, at 12:45 PM, Michael Moser wrote: > > Hello Greg. If you give ConsumeJMS > 1 concurrent task, each task will > create a separate consumer.

Re: ConsumeJMS concurrent tasks

Hello Greg. If you give ConsumeJMS > 1 concurrent task, each task will create a separate consumer. If you are consuming from a JMS Queue, then you are OK and will not duplicate any messages. If, however, you are consuming from a JMS Topic, then you should keep ConsumeJMS at 1 concurrent task.

Re: ListSFTP Processors losing state after upgrading from 1.26.0 to 2.0.0-M3

gt; Peter > > From: Jim Steinebrey mailto:jrsteineb...@gmail.com>> > Sent: Wednesday, July 10, 2024 11:00 AM > To: users@nifi.apache.org <mailto:users@nifi.apache.org> > Subject: Re: ListSFTP Processors losing state after upgrading from 1.26.0 to > 2.0.0-M3 >

RE: ListSFTP Processors losing state after upgrading from 1.26.0 to 2.0.0-M3

approach for restoring the processor state for the ListSFTP processors. Any further suggestions would be greatly appreciated! Cheers ~ Peter From: Jim Steinebrey Sent: Wednesday, July 10, 2024 11:00 AM To: users@nifi.apache.org Subject: Re: ListSFTP Processors losing state after upgrading from

Re: PublishKafkaRecord_2_6 produces negative partition number

;,"type":["string","null"]},{"name":"Id","type":["string","null"]},{"name":"NumericId","type":"long"},…. > > > > Did I miss something else? > > > > *Fr

Re: PublishKafkaRecord_2_6 produces negative partition number

":"nifiRecord","namespace":"org.apache.nifi","fields":[{"name":"_hdl_loadstamp","type":["string","null"]},{"name":"Id","type":["string","null"]},{"name":&q

RE: PublishKafkaRecord_2_6 produces negative partition number

Interesting. The largest number representable by a 32 bit integer is 2147483647. Which exactly one less than th number you have. That sounds like a hint... Sent via the Samsung Galaxy A54 5G, an AT 5G smartphone Original message From: "Richter, Robert" Date: 7/11/24 5:38

Re: ListSFTP Processors losing state after upgrading from 1.26.0 to 2.0.0-M3

Hi Peter, Can you review the configuration for your local state provider from state-management.xml for 1.26.0 and 2.0.0-M3 configurations? From comparing the code in 1.26.0 vs 2.x, My working theory is that you have partitions set to the default of 16 for both old and new Nifi configurations.

Re: [ANNOUNCE] Apache NiFi 1.27.0 Released

Russ, Thanks for highlighting that confusing title attribute on the download links. The hard-coded reference to the source was not intentional. The website is now updated with those title attributes removed. Regards, David Handermann On Tue, Jul 9, 2024 at 11:01 AM Russell Bateman wrote: > >

Re: [ANNOUNCE] Apache NiFi 1.27.0 Released

On the Downloads page , is it intentional to offer--under Binaries--source titles? This is for both v2 and v1. Looking at view-source, it's because title=mistakenly (?) uses "source" in the name. When I click to download, I *do* get the binary and not the

Re: Containerizing, clustering, Registry - how to begin?

Hi, At Stackable we have Kubernetes operators and images for Apache NiFi and Apache ZooKeeper, so if you want avoid the effort of building all of this yourself it’s worth taking a look. There’s an experimental NiFi 2.0 Docker image in our repository if you’re keen to try that out, but that

Re: Containerizing, clustering, Registry - how to begin?

+1 to this. Would like to know if we can scale out and scale in based on the load. On 9 Jul 2024, 7:32 PM +0530, Joe Obernberger , wrote: > Hi James - I too would like more information on this. I've been using NiFi in > a kubernetes cluster for over a year now using cetic >

Re: Containerizing, clustering, Registry - how to begin?

Hi James - I too would like more information on this.  I've been using NiFi in a kubernetes cluster for over a year now using cetic (https://github.com/cetic/helm-nifi) and have it working with NiFi 1.25.0.  This works well with a 3 node cluster, and can successfully scale up.  Scaling down

Re: Received SHUTDOWN request from Bootstrap

FO [pool-2-thread-1] org.eclipse.jetty.server.session node0 Stopped scavenging   Very hard to find the root cause ..   Envoyé: lundi 8 juillet 2024 à 16:56 De: "Mark Payne" À: "users@nifi.apache.org" Objet: Re: Received SHUTDOWN request from Bootstrap Hey Minh,   T

Re: DBCPConnectionPool 2.0.0-M3 Database Connection URL field says EL is supported

Hi Mark, Thanks for your question. Unfortunately the "Database Connection URL” does not support reading flow file attributes. DBConnectionPool is intended to hold and reuse connections to a single data source. In its definition below, it only support reading from (Nifi variables in 1.X) or

Re: DBCPConnectionPool 2.0.0-M3 Database Connection URL field says EL is supported

Hi, The purpose of the DBCPConnectionPool is to manage a pool of reusable database connections and avoiding establishing new connections for each database request. Because they share the same connection, Flow File scoped dynamic URL evaluation is not supported. For dynamic use of connection

Re: Received SHUTDOWN request from Bootstrap

juillet 2024 à 15:18 De: "David Handermann" À: users@nifi.apache.org Objet: Re: Received SHUTDOWN request from Bootstrap Hi Minh, The log snippet shows standard behavior for NiFi when receiving the stop command from the nifi.sh control script. There may be some additional details in nifi-boo

Re: Received SHUTDOWN request from Bootstrap

iFi logging handler] org.apache.nifi.StdErr > Log configuration loaded from default internal file. > > Envoyé: lundi 8 juillet 2024 à 15:18 > De: "David Handermann" > À: users@nifi.apache.org > Objet: Re: Received SHUTDOWN request from Bootstrap > Hi Minh, > > The

Re: Received SHUTDOWN request from Bootstrap

:17,916 ERROR [NiFi logging handler] org.apache.nifi.StdErr Log configuration loaded from default internal file.   Envoyé: lundi 8 juillet 2024 à 15:18 De: "David Handermann" À: users@nifi.apache.org Objet: Re: Received SHUTDOWN request from Bootstrap Hi Minh, The log snippet show

Re: Received SHUTDOWN request from Bootstrap

Hi Minh, The log snippet shows standard behavior for NiFi when receiving the stop command from the nifi.sh control script. There may be some additional details in nifi-bootstrap.log, but those few lines from nifi-app.log describe expected behavior. Regards, David Handermann On Mon, Jul 8, 2024

Re: ConsumeAMQP not delivering message from RMQ to Success

Hi Peter, and thank you for your response. You are right: I was trying to use Run Once. Does this prohibition against Run Once also apply to PublishAMQP? If Run Once should not be used for a processor, would folks consider disabling that processor menu option on ConsumeAMQP (and PublishAMQP,

Re: ConsumeAMQP not delivering message from RMQ to Success

Hi James, The logs show that the processor stopped just after it was started (within the same second: 17:23:39 UTC). If it is due to closing the channel by the broker prematurely, then there should be some error logs too. Could you please check if there are other log messages? You may be trying

Re: ConsumeAMQP not delivering message from RMQ to Success

Wanted to follow up in case it serves others in the future. I stepped through these changes before I got this to work: 1. My associate extended the heartbeat on the RMQ host. 2. I made two changes to NiFi's bootstrap.conf, restarting NiFi after editing the file to pick up these changes: .

RE: Containerizing, clustering, Registry - how to begin?

James, I run my own project at home that does this. Individual containers for each NiFi node, one for Registry, a zookeeper cluster of 3 containers and one container for nginx to proxy front end access. This to me is the Docker way of doing things. This then does look like a traditional NiFi

RE: Nifi Site to Site error message meaning

this is getting more common. I know both are long shots, since you have this working on all the other NiFi nodes, but at this point small details are worth checking.  Regards, Isha Van: David Early via users Verzonden: zaterdag 29 juni 2024 02:45 Aan: users@nifi.apache.org Onderwerp: Re: Nifi Site

Re: Nifi Site to Site error message meaning

Thanks, Isha for the first cut. We have a whole bunch of systems that are in an internal network that are all able to talk using site to site, so we are not unfamiliar with the connection, but after a long session of comparisons and changes, I still cannot this to work. I enabled DEBUG in

RE: Nifi Site to Site error message meaning

Hi David, This typically means one of two things: 1. that the DN of the (client) certificate does not match the user in the receiving NiFi instance *exactly*. Inspect the logs (I think it’s nifi-user.log) to find the DN that the sending NiFi is providing and edit the username in the

RE: Re: NiFi CLI in secure environment

apache.org Subject: [EXTERNAL] Re: NiFi CLI in secure environment Hi Brant, Thanks for describing the environment and including the version information. NiFi 2. 0. 0-M3 introduced support for the Client Credentials Grant Type in conjunction with OpenID Connect authentication, but did not include chan

Re: NiFi CLI in secure environment

Hi Brant, Thanks for describing the environment and including the version information. NiFi 2.0.0-M3 introduced support for the Client Credentials Grant Type in conjunction with OpenID Connect authentication, but did not include changes to the NiFi CLI. Support for Client Credentials could be

Re: Accessing File Size in ExecuteGroovyScript script

if fileSize is not visible in ExecuteGroovyScript, why don't you try to updateattribute before the ExecuteGroovyScript and get fileSize attribute into another attribute, like fileSize_readable = ${fileSize} in your code you read like this: def file_size = ff.getAttribute('fileSize_readable') On

Re: Accessing File Size in ExecuteGroovyScript script

It appears the best way to do this is to apply the java getSize() method to the ff object, like this: def ffSize = ff.getSize() This seems to output the file size to the log in bytes. def file_size = (ffSize != null) ? ffSize :0 if (file_size == 0) { log.error("file_size is undefined or

RE: [EXTERNAL] Accessing File Size in ExecuteGroovyScript script

I believe you are casting ff.size as an Integer. 8 GB is signifincantly larger than can be held in a 32 bit integer, which is just 2 GBs. Suggest you use a double or a big decimal. Whats happening is you are truncating the high order bits. From: James McMahon Sent: Monday, June 17, 2024 7:51

Re: Accessing File Size in ExecuteGroovyScript script

I should mention that I have also tried to access fileSize like this without success: //def file_size = (ff.size != null) ? (ff.size as Integer) : 0 def file_size = ff.getAttribute('fileSize') This returns null. I tried this approach based on a post in cloudera, which said this: |The default

Re: Nifi on RockyLinux

  Hello Deepak,   We have migrated all our nifi instances to Rocky Linux 8 and until now no got any issue.   Regards   Minh   Envoyé: vendredi 14 juin 2024 à 19:59 De: "Joe Witt" À: users@nifi.apache.org Objet: Re: Nifi on RockyLinux Deepak   In Apache we don't have

Re: FlattenJSON fails on large json file

James You may be able to use alternative JSON components such as those with record readers/writes. You could certainly write a nifi processor in either Java or Python that would do this and be super efficient. The processor you've chosen just isn't very flexible in regards to larger objects and

Re: FlattenJSON fails on large json file

Thanks Eric. So then this in the error message - java.lang.OutOfMemoryError - isn't really to be taken at face value. FlattenJson tried to index an array that exceeded the maximum value of an integer, and it choked. An 8 GB file really isn't that large. I'm hoping someone has encountered this

Re: FlattenJSON fails on large json file

Hi James, I don't have a solution for you off the top of my head. But I can tell you the failure is because you've got an array longer than the maximum value of an Int. So, memory is not the limiting factor. -Eric On Fri, Jun 14, 2024, 10:59 AM James McMahon wrote: > I have a json file,

Re: Nifi on RockyLinux

Deepak In Apache we don't have mechanisms to verify/validate that but indications are that it should work just fine. Thanks On Fri, Jun 14, 2024 at 10:47 AM Chirthani, Deepak Reddy < c-deepakreddy.chirth...@charter.com> wrote: > Hi, > > > > Writing this email to get a confirmation for if

RE: Who or what sets up NIFI_HOME as a system environment variable?

themselves.” Regards Steve Hindmarch From: Chris Debevec Sent: Wednesday, June 12, 2024 5:09 PM To: users@nifi.apache.org Subject: Re: Who or what sets up NIFI_HOME as a system environment variable? You don't often get email from christopherdebe...@gmail.com<mailto:christopherdebe...@gmail.

Re: Who or what sets up NIFI_HOME as a system environment variable?

What do you mean who or what? If I follow your question my understanding is that's a normal sys admin function. It's the responsibility of whoever is administering the system and expected to keep the application up. Essentially a requirement while someone is installing or maintaining NiFi on the

Re: Who or what sets up NIFI_HOME as a system environment variable?

I have an update on this question which remained quite rightly unanswered since it was my own peculiar problem. It resulted from the not-so-clever way our NiFi systemdservice was put together 6+ years ago which was avoided using /nifi.sh/ (and /nifi-env.sh/).NIFI_HOMEsimply did not exist once

Re: [EXTERNAL] Re: Re: writing to adls - NiFi on Azure

networks and IP addresses” > > > > Where can I see the full stack trace? > > > > Thanks > > > > *From:* Peter Turcsanyi > *Sent:* Thursday, June 6, 2024 1:39 AM > *To:* users@nifi.apache.org > *Subject:* [EXTERNAL] Re: Re: writing to adls - NiFi on Azure &

RE: [EXTERNAL] Re: Re: writing to adls - NiFi on Azure

Hi Peter, It is “Enabled from selected virtual networks and IP addresses” Where can I see the full stack trace? Thanks From: Peter Turcsanyi Sent: Thursday, June 6, 2024 1:39 AM To: users@nifi.apache.org Subject: [EXTERNAL] Re: Re: writing to adls - NiFi on Azure ATTENTION: This email

RE: Who or what sets up NIFI_HOME as a system environment variable?

Hi Russell, To set that variable up as a system environment variable requires the installer to do something, like add the export command to a file such as “/etc/environment”. That is what we do on our current project, and I can see it happening in an Ansible task. An out of the box

RE: Processor Python Creation

Hi Luis, I've observed similar behavior working with the python processors. > 1. Everytime I modify the python code of a processor and stop it, all > the dependencies are re-installed. Doesn't matter if I just changed code > or added any new library. Is that ok ? The modification

Re: [EXTERNAL] Re: writing to adls - NiFi on Azure

; > > Thanks > > > > *From:* Peter Turcsanyi > *Sent:* Friday, May 31, 2024 4:17 PM > *To:* users@nifi.apache.org > *Subject:* [EXTERNAL] Re: writing to adls - NiFi on Azure > > > > *ATTENTION:* This email originated from outside of GM. > > > > > H

Re: Nifi 2.0-M3 cannot set attributes

Thank you for the quick answer David. I guess the only option for now is to wait... Regards, LC El 05-06-24 a las 17:29, David Handermann escribió: Hi Luis, Thanks for reporting this problem and providing the background details. This is a known issue related to applying FlowFile

Re: Nifi 2.0-M3 cannot set attributes

Hi Luis, Thanks for reporting this problem and providing the background details. This is a known issue related to applying FlowFile attributes with the failure relationship, and it is being tracked in the follow Jira issue: https://issues.apache.org/jira/browse/NIFI-13324 Regards, David

Re: PutUDP using flowfile attribute in nifi 1.22.0

This is obviously help us in moving forward to our next step. Since we have to load-balance udp packets to multiple Nifi servers for that we use F5 BigIP load balancer. This adds one more problem to solve for us. However, we have solved that problem in our custom Java application which listens

Re: PutUDP using flowfile attribute in nifi 1.22.0

Hi Atul, To clarify, would your user case work if Hostname and Port properties were enhanced to support evaluating expression language using the flow files? Regards, Jim > On Jun 4, 2024, at 8:41 AM, Atul Saroha wrote: > > Hi All, > > We recently started using nifi for the last 6 months. We

RE: [EXTERNAL] Re: writing to adls - NiFi on Azure

Hi Peter, We tried that , still does not work. Same error. Thanks From: Peter Turcsanyi Sent: Friday, May 31, 2024 4:17 PM To: users@nifi.apache.org Subject: [EXTERNAL] Re: writing to adls - NiFi on Azure ATTENTION: This email originated from outside of GM. Hi Tahir, I tested it without

Re: Back pressure in a NiFi cluster

Thanks for the confirmation! Am Di., 4. Juni 2024 um 14:57 Uhr schrieb Pierre Villard < pierre.villard...@gmail.com>: > Hi Alexis, > > Backpressure is a node-level concept. If there is backpressure on one > node, it does not impact other nodes. So the statement "it could be that 1 > node is

RE: Back pressure in a NiFi cluster

Alexis, I see this often in some of the clusters I maintain. The restricted scheduling only applies to the node where the back pressure is occurring. The red and amber colours on the UI are there as a clue to the user that back pressure is occurring. You can test this for example by using the

Re: Back pressure in a NiFi cluster

Hi Alexis, Backpressure is a node-level concept. If there is backpressure on one node, it does not impact other nodes. So the statement "it could be that 1 node is slower and reaches the threshold while the others run normally" is correct. HTH, Pierre Le mar. 4 juin 2024 à 14:54, Alexis

Re: Single Batch Per Node and back pressure

Got it, thanks for the clarification. On Mon, 3 Jun 2024, 18:00 Michael Moser, wrote: > When ControlRate yields, it will yield for the full Yield Duration. So > your scenario, Alexis, will allow 10 files through in the first > half-second, and when the 11th arrives it will yield for 1 second

Re: Single Batch Per Node and back pressure

When ControlRate yields, it will yield for the full Yield Duration. So your scenario, Alexis, will allow 10 files through in the first half-second, and when the 11th arrives it will yield for 1 second (if Yield Duration = 1 sec). After that yield ends, it will allow the next 10 files through

Re: Single Batch Per Node and back pressure

Hi Jim, Thanks for the prompt response. I think that could work, but now that I look at it, the documentation says that accuracy can be increased "by decreasing the Yield Duration" - if I want, say, 10 files per second and 20 arrive evenly spread out within a second, does that mean that after

Re: Single Batch Per Node and back pressure

Hi Alexis, Yes, what you see in your experiments is the expected behavior. The NiFi documentation for FlowFileCurrency says: SINGLE_BATCH_PER_NODE When

RE: [JDK] NiFi 1.20.0 comaptibility with JDK21

do el: lunes, 3 de junio de 2024 14:00 Para: users@nifi.apache.org Asunto: Re: [JDK] NiFi 1.20.0 comaptibility with JDK21 NTT DATA Security Awareness - This is an incoming mail from an EXTERNAL SENDER (users-return-17480-pedro.soto.fernandez=nttdata@nifi.apache.org<mailto:use

Re: [JDK] NiFi 1.20.0 comaptibility with JDK21

Hi Pedro, It's hard to have a definitive answer on this as it also depends on what you're using in your flows but you may have some issues. I'd highly recommend using the latest of Apache NiFi 1.x (NiFi 1.26) if you want to run it with Java 21. Thanks, Pierre Le lun. 3 juin 2024 à 13:56, Pedro

RE: Single Batch Per Node and back pressure

My reading of the manual on this suggests that the batch size is determined by the contents of the queue upstream of the input node, not the downstream queue. "... the Input Ports will continue to ingest all data until all of the queues feeding the Input Ports have been emptied." Perhaps

Re: writing to adls - NiFi on Azure

Hi Tahir, I tested it without permissions and got a different error message: "code":"AuthorizationPermissionMismatch","message":"This request is not authorized to perform this operation using this permission. So the role/permissions should not be an issue in your environment. For your error

Re: writing to adls - NiFi on Azure

R, You can unsubscribe by sending an email to users-unsubscr...@nifi.apache.org . Best, Peter Turcsanyi On Fri, May 31, 2024 at 10:11 PM R wrote: > please remove me from this list > > On Fri, May 31, 2024 at 4:04 PM Peter Turcsanyi > wrote: > >> Hi Tahir, >> >> Did you configure

RE: [EXTERNAL] Re: writing to adls - NiFi on Azure

Yes, we configured managed identity for our VM. We provided Storage blob contributor role, also tried using Blob data owner. Thanks From: Peter Turcsanyi Sent: Friday, May 31, 2024 3:04 PM To: users@nifi.apache.org Subject: [EXTERNAL] Re: writing to adls - NiFi on Azure ATTENTION: This email

Re: writing to adls - NiFi on Azure

please remove me from this list On Fri, May 31, 2024 at 4:04 PM Peter Turcsanyi wrote: > Hi Tahir, > > Did you configure system-assigned or user-assigned managed identity for > your VM on the Azure portal? > Did you grant the right role (e.g. Storage Blob Data Owner) to that > managed identity?

Re: writing to adls - NiFi on Azure

Hi Tahir, Did you configure system-assigned or user-assigned managed identity for your VM on the Azure portal? Did you grant the right role (e.g. Storage Blob Data Owner) to that managed identity? Best regards, Peter Turcsanyi On Fri, May 31, 2024 at 8:10 PM Tahir Khan wrote: > Hi, > > We are

RE: Authorisation with multi-tiered groups

Hi all, I didn't get much traction when I raised this question a few weeks ago. Is there any appetite for re-addressing the Jira ticket mentioned? Regards Steve Hindmarch From: stephen.hindmarch.bt.com via users Sent: Friday, April 12, 2024 12:15 PM To: users@nifi.apache.org Subject

RE: [SSL] Can't reach remote site, SSL error

just gone. Thanks Emmanuel De : Isha Lamboo Envoyé : lundi 6 mai 2024 08:51 À : users@nifi.apache.org Objet : RE: [SSL] Can't reach remote site, SSL error CAUTION: This message originated from an outside organization. In case of suspicion, click on "Report to SAFRAN Security" from t

RE: Re: Re: Re: IMDSv2 + Hashicorp Vault

ted] From: David Handermann Sent: Wednesday, May 8, 2024 17:00 To: users@nifi.apache.org Subject: [EXTERNAL] Re: Re: Re: IMDSv2 + Hashicorp Vault Brant, Thanks for the additional details. Based on the description, it sounds like it would be worth raising an issue with Spring Vault. The NiFi impl

Re: Re: Re: IMDSv2 + Hashicorp Vault

dermann > *Sent:* Wednesday, May 8, 2024 14:38 > *To:* users@nifi.apache.org > *Subject:* [EXTERNAL] Re: Re: IMDSv2 + Hashicorp Vault > > > > Brant, Just for clarification, Spring Vault is a separate project from > Spring Framework, following its own version numbering strateg

RE: Re: Re: IMDSv2 + Hashicorp Vault

mann Sent: Wednesday, May 8, 2024 14:38 To: users@nifi.apache.org Subject: [EXTERNAL] Re: Re: IMDSv2 + Hashicorp Vault Brant, Just for clarification, Spring Vault is a separate project from Spring Framework, following its own version numbering strategy, so Spring Vault 3. 1.  1 is the latest versi

Re: Re: IMDSv2 + Hashicorp Vault

k background with green text Description automatically > generated] > > > > *From:* Patrick Timmins > *Sent:* Wednesday, May 8, 2024 11:45 > *To:* users@nifi.apache.org > *Subject:* [EXTERNAL] Re: IMDSv2 + Hashicorp Vault > > > > In my best Rosanne Rosanadana .. . never

RE: Re: IMDSv2 + Hashicorp Vault

2024 11:45 To: users@nifi.apache.org Subject: [EXTERNAL] Re: IMDSv2 + Hashicorp Vault In my best Rosanne Rosanadana .. . never mind .. . I see the only outlier for using the latest Spring is the spring-vault-core-3. 1. 0. jar !! On 5/8/2024 11: 20 AM, Brant Gardner wrote: We’re running 2. 0. 0

Re: IMDSv2 + Hashicorp Vault

gard...@solventum.com* *A black background with green text Description automatically generated *From:*Patrick Timmins *Sent:* Wednesday, May 8, 2024 11:00 *To:* users@nifi.apache.org *Subject:* [EXTERNAL] Re: IMDSv2 + Hashicorp Vault What version of NiFi are you using? I'm seeing Spring v5. 3. 30 in Ni

Re: IMDSv2 + Hashicorp Vault

From:*Patrick Timmins *Sent:* Wednesday, May 8, 2024 11:00 *To:* users@nifi.apache.org *Subject:* [EXTERNAL] Re: IMDSv2 + Hashicorp Vault What version of NiFi are you using? I'm seeing Spring v5. 3. 30 in NiFi 1. 24. On 5/8/2024 6: 32 AM, Brant Gardner wrote: Good morning, It appears that the Spring

RE: Re: IMDSv2 + Hashicorp Vault

To: users@nifi.apache.org Subject: [EXTERNAL] Re: IMDSv2 + Hashicorp Vault What version of NiFi are you using? I'm seeing Spring v5. 3. 30 in NiFi 1. 24. On 5/8/2024 6: 32 AM, Brant Gardner wrote: Good morning, It appears that the Spring 3. 1. 0 libraries that NiFi uses are unable to work with IMDSv2 o

Re: IMDSv2 + Hashicorp Vault

What version of NiFi are you using?  I'm seeing Spring v5.3.30 in NiFi 1.24. On 5/8/2024 6:32 AM, Brant Gardner wrote: Good morning, It appears that the Spring 3.1.0 libraries that NiFi uses are unable to work with IMDSv2 on AWS EC2 instances, so if your company requires IMDSv2 (which ours

RE: [SSL] Can't reach remote site, SSL error

or proprietary information and may be subject to export control laws and regulations. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. Unauthorize

RE: Restarting Nifi Cluster Systems to add new user

as Joe has pointed out. Regards, Isha Van: Joe Witt Verzonden: woensdag 1 mei 2024 00:42 Aan: users@nifi.apache.org Onderwerp: Re: Restarting Nifi Cluster Systems to add new user Thanks - take a look at your conf/authorizers file and see which authorizer is being used. Based on what you said

Re: Restarting Nifi Cluster Systems to add new user

Thanks - take a look at your conf/authorizers file and see which authorizer is being used. Based on what you said it sounds like org.apache.nifi.ldap.tenants.LdapUserGroupProvider There are properties related to how aggressively it will search for information from the directory server. The

Re: Restarting Nifi Cluster Systems to add new user

Hello Joe, It's through AD. But it isn't controlled via groups. I ended up having to add the user through the UI (which will normally be overwritten). I'm running version 1.23.2. Regards, *Shamsudeen Jameer*Data Operations managerpriorityshamsudeen.jam...@prth.como: (516) 345-5015 M: (917)

Re: Restarting Nifi Cluster Systems to add new user

Hello Can you share more about which authentication and authorization provider you're using with NiFi today? Also would be good to share which other authentication/authorization providers your organization could leverage as then it is a question of which ones are supported out of the box.

Re: Insufficient permissions on initial start up (NiFi 2.0)

No problem. Glad you got it sorted. Yet at the https URL in the browser, it still tells me it is insecure. > This is happening because the certificate is not issued by a trusted Certificate Authority. The certificate from TinyCert is valid (the connection works) but TinyCert is not a trusted CA

Re: Python Processor and relationships

Hi, Are you in a position to share the code of your python processor? Did you implement getRelationships(self) in your processor? Le ven. 26 avr. 2024, 06:52, Ashwini Kumar a écrit : > I created a Python Nifi Processor just as in the standard python > documentation. This is NOT an

Re: Insufficient permissions on initial start up (NiFi 2.0)

When I learned that the initial user in authorizers.xml must match the certificate *exactly*, I figured it would be an easy matter to use openssl to inspect the cert. I wanted to be *absolutely* certain I matched it correctly. Here is the command: /opt/nifi/config_resources/keys$ openssl pkcs12

Re: Insufficient permissions on initial start up (NiFi 2.0)

> > What is this Access Token it cites at top? > NiFi UI attempts to get the access token expiration. However, since you're authenticating with a certificate the endpoint returns an IllegalState because there was no token in the request. Looking at the logs and the supplied configuration it

Re: Insufficient permissions on initial start up (NiFi 2.0)

The identity you put for your initial admin is: C = US, ST = Virginia, L = Reston, O = C4 Rampart, OU = NIFI, CN = admin2 Which does not match the identity shown in the logs that is coming from your client cert: CN=admin2, OU=NIFI, O=C4 Rampart, L=Reston, ST=Virginia, C=US It is case and

Re: Insufficient permissions on initial start up (NiFi 2.0)

Looking at the nifi-user.log, I find I am getting a Conflict response, Access Token not found. more ./nifi-user.log 2024-04-25 00:23:49,329 INFO [main] o.a.n.a.FileUserGroupProvider Creating new users file at /opt/nifi/config_resources/users.xml 2024-04-25 00:23:49,352 INFO [main]

Re: Insufficient permissions on initial start up (NiFi 2.0)

James, If you check the nifi-user.log in the logs directory, you should see messages for the requests that are being rejected. In that log message you should see the identity that you're authenticated with. Can you compare that with the user that you've configured the policies for. Hopefully,

Re: Insufficient permissions on initial start up (NiFi 2.0)

I still cannot access my own NiFi 2.0 instance. I continue to get this rejection: Insufficient Permissions - home Unable to view the user interface. Contact the system administrator. The canvas flashes for an instant when I try to hit my secure URL, but is immediately replaced with this

Re: Insufficient permissions on initial start up (NiFi 2.0)

I'll review this closely once again when I get back to this system tonight - thanks very much for your reply, Isha. I also feel I need to look more closely in nifi.properties, at values I have set for keys nifi.security.identity.mapping.[value, transform, pattern].CN1 I noticed some odd behavior

RE: Insufficient permissions on initial start up (NiFi 2.0)

Hi James, Have you changed these settings in authorizers.xml since you first started NiFi? If so, you may need to delete users.xml and authorizations.xml. A new admin user will not be created if those files already exist. Otherwise, the trickiest part is usually that the user DN needs to match

Re: How to upload flow definition to new 2.0 instance?

Thank you Pierre. I appreciate your reply. I have not yet done this but intend to, as soon as I can figure out how to get my NiFi 2.0 instance to come up securely with certs and TLS. I do and did not want to load up my flows into a nonsecured NiFi instance, which is why I have taken so long to

Re: Unable to securely connect to NiFi 2.0 instance

> Regards, > > > > Isha > > > > > > *Van:* James McMahon > *Verzonden:* vrijdag 19 april 2024 01:17 > *Aan:* users > *Onderwerp:* Re: Unable to securely connect to NiFi 2.0 instance > > > > I started from scratch. Got nifi to start, no errors at

RE: Unable to securely connect to NiFi 2.0 instance

which CAs it will accept for client certs. Regards, Isha Van: James McMahon Verzonden: vrijdag 19 april 2024 01:17 Aan: users Onderwerp: Re: Unable to securely connect to NiFi 2.0 instance I started from scratch. Got nifi to start, no errors at all in my nifi-app.log. Configured the client

Re: Unable to securely connect to NiFi 2.0 instance

I started from scratch. Got nifi to start, no errors at all in my nifi-app.log. Configured the client certs in my Chrome browser, also added cacert.pem to my Root Trusted CAs. Tried to hit https://ec2-44-219-227-80.compute-1.amazonaws.com:8443/nifi , continue to get rejected with this message from

Re: How to upload flow definition to new 2.0 instance?

In NiFi 1.x, right click on process group, download flow definition. It'll give you a JSON file. In NiFi 2, drag and drop a process group on the canvas, and click the upload icon on the right of the name input. You'll be able to select your JSON file. HTH Le jeu. 11 avr. 2024 à 02:14, James

Re: Hit\Miss Writing to Syslog system

Hi Shamsudeen, Thanks for the reply and clarifying the use of the protocol. UDP does not offer any kind of delivery guarantees at the protocol level, so it is even less reliable than TCP for syslog. In other words, data loss can happen without any type of error being logged. If the data loss is

  1   2   3   4   5   6   7   8   9   10   >