About MattWho

DianaTorres · ‎11-29-2024

@pankajgaikwad As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks.

rajivswe_2k7 · ‎11-27-2024

Thank you @MattWho . Yes , Initially, i have designed the partial failure. Now , i have changed the design to captured on the failure flow files and send the alert on that. Thank you.

HenriqueAX · ‎11-27-2024

Running the restart shell script inside container did it for me! Thanks for the help @MattWho!

MattWho · ‎11-22-2024

@Armel316 Since you only have two user group providers (ldap and file), that means that both are returning user "xxx". If the ldap-user-group-provider is returning user "xxx" you don't want to define that same user through the file-user-group-provider. What this means is that the users.xml file that the file-user-group-provider is loading users from on startup contains user "xxx". The file-user-group-provider will ONLY generate a users.xml file if one does not already exist. If one already exist the file-user-group-provider will NOT make any modifications to an existing users.xml if you modify the provider configuration. Once a users.xml file exists, the expectation is that all future user/group modification happen via the UI. NOTE: The users.xml does not contain any users or group being loaded by other providers in to NiFi memory. So you have two options here: Rename the current users.xml file so a new one is created on startup with only the 3 defined node-identities. (this is preferred method) Manually modify the users.xml to remove all users that are being synced by the ldap-user-group-provider. Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt

BadKarma · ‎11-21-2024

For remote access to login page, just add to c:/windows/system32/drivers/etc/hosts your server IP and hostname same on linux, /etc/hosts

VidyaSargur · ‎11-20-2024

@s198, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future. However, if you still have concerns, please provide the information that @MattWho has requested.

ZNFY · ‎11-19-2024

Thank you for your reply. I just tried deploying a NiFi container without modifying the start.sh script, and I found that when I set NIFI_CLUSTER_IS_NODE to true, the container still gets stuck and then stops. I find this strange—if the container doesn’t support clustering, why does the official image allow this environment variable to be set? I think this is misleading. I noticed that version 2.0.0 supports setting nifi.cluster.leader.election.implementation to KubernetesLeaderElectionManager. Does this require NiFi to be deployed at the same level as Kubernetes, or does NiFi need to be deployed as a pod within Kubernetes? I look forward to your response. Thank you!

MattWho · ‎11-19-2024

@phadkev Would need to see more of the nifi-app.log to better understand what is going on here. Are you seeing the same org.apache.nifi.controller.StandardProcessorNode Timed out while waiting for OnScheduled exception for other components or just this executeScript processor? The exception itself is generic and could be thrown for any processor class. Are you ever seeing the log line telling you the NiFi UI is available at the following urls? If so NiFi is up. Are you seeing NiFi shut back down with some exception and stack trace in the nifi-app.log. What you shared implies NiFi is having issues scheduling this specific processor to execute. This could very well be caused by an issue with the custom script that was build and used in this processor. If you NiFi is really not coming up, you could modify the nifi.properties file by changing "nifi.flowcontroller.autoResumeState=true" to "nifi.flowcontroller.autoResumeState=false". This will allow you NiFi to start without starting any processors. You could then search the UI for the ExecuteScript component processor with id "acb441ba-c36b-1fdd-53f2-3a4821d43833". Disable it and start all your other processors. Restart your NiFi to see if you still have any issues. This isolates the issue to this processor and your script. Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt

nifier · ‎11-15-2024

@MattWho Thanks for your reply 👍

MattWho · ‎11-14-2024

@Ytch NiFi is designed to move data and the ListS3 processor is designed to list s3 objects/files and not directories. On the downstream side, NiFi does not have a processor that just create directories. Many out processors will create a missing directory if content is to be written must be written to a directory path that does not exist on the target. But without content those processor will not create any directories. I am clear on what yoru use case is here, but based on yoru description it is not something any of the stock processors would do. You would need to write something custom (either your own processor or some custom script you can execute via aNiFi scripting processor). Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt

Online	Online
Last Visited	‎01-26-2026 07:29 PM

Member Since	‎07-30-2019 10:41 AM
Last Visited	‎01-26-2026 07:29 PM
Posts	3,426
Kudos received	1627

Cloudera Community

Re: Best Practice for configuring registry flows

Re: Nifi 2.7.2 Start Problem

Re: Error importing NiFi workflow template from ve...

Re: Error importing NiFi workflow template from ve...

Re: How to elevate a default nifi user to admin - ...

Re: how to stop and start processor-group in NIFI ...

Re: Nifi : Implement Sleep Mechanism in nifi witho...

Re: Restart Nifi nodes without data loss

Re: No available buckets after secure Nifi connect...

Re: Access failed after apache nifi installation

Re: Replace ConsumeASB Processor with the InvokeHt...

Re: Can't enable cluster option for NIFI container

Re: Nifi not starting because of OnScheduled()

Re: NiFi for file movement

Re: Lists3 processor to fetch only one layer of su...