@LuisLeite Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks. ... View more

@Kilynn  So as i mentioned in my last response, once memory usage go to high, OS level OOM Killer was most likely killing the NiFi service to protect the OS.  The NiFi bootstrap process would have detected the main process died and started it again assuming OOM killer did not kill the parent process. ... View more

@techNerd  I think your scenario may need a bit more detail to understand what you are doing and what it is doing versus what you want the flow to do.   The ListFile only listed information about file(s) found in the target directory. It then generates a one of more FlowFiles from the listing that was performed.  A corresponding FetchFile processor would actually retrieve the content for each of the listed files. From the sounds of your scenario, you have instituted a 20 sec delay somehow between that ListFile and FetchFile processor? Or you have configured the run schedule on the ListFile processor to "20 secs"? Setting the run schedule only tells the processor how often it should request a thread from the NiFi controller that can be used to execute the processor code.  Once the processor gets its thread, it will execute.  The ListFile processor will list all files present in the target source directory based on the configured file and path filters.  For each File listed it will produce a FlowFile.  Run schedule does not mean it executes for a full 20 seconds continuously checking the input directory to see if new files arrive.  The run schedule also not impacted by how long it takes a listing to complete.  It will request a thread every 20 seconds (00:00:20, 00:00:40, 00:01:00, etc...).  The configured "concurrent tasks" controls whether the processor can execute multiple listing in parallel.  Let say the thread that was executed at 00:01:00 was still executing 20 seconds later. Since that thread is still using the default 1 concurrent task, the listFile would not be allowed to request another thread from the controller at that time. Since the run schedule is independent of the thread execution duration, there is no way to dynamically alter the schedule. There is also no way for a new file to get listed at same time as a previous file (unless both were already present at time of listing) within the same thread execution.  The listFile use the configured "Listing Strategy" to control how it handles listing of files.  A "tracking" strategy is used to prevent the ListFile processor from listing the same file twice by recording some information in a state provider or a cache.  If "No Tracking" is configured, the listFile will list all found files every time it executes.  ListFile does not remove the source file from the directory.  Removal of the source file is a function optionally handled by the corresponding FetchFile processor. If this is not clear, share more details around your use case and flow design specific so I can provide more direct feedback. Here is the documentation around processor scheduling (works the same no matter which processor is being used): https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#scheduling-tab If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Matt ... View more

@Saraali  I'd love to help, but I have never done any scripting to convert to excel format.  All I can tell you is there is no native processor available in NiFi that does this conversion. I'd recommend raising a new feature request jira in apache for NiFi: https://issues.apache.org/jira/projects/NIFI/issues/ Perhaps others in the community may be looking for the same capability who are willing to contribute code? Thanks, Matt ... View more

Many thanks @MattWho It seems that I started NIFI based on the old flow.xml.gz. I successfully granted all access for myself. ... View more

@armensano  Just to make sure we are clear on your ask here. You have a secured NiFi and NiFi-Registry installation that uses user/client certificates to authenticate your user via the mutual TLS handshake? If that is the case, you should not be seeing a NiFi/NiFi-registry login window. Can you share screenshots? What do you see in the nifi-user.log when you attempt to access NiFi? Thanks, Matt ... View more