Member since
03-05-2021
19
Posts
3
Kudos Received
1
Solution
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 3565 | 07-22-2022 08:59 AM |
01-11-2023
02:48 PM
Thank you very much for the response and suggestion. I tried to implement this in our test environment, which resulted in a nifi-app_2023-01-11.log file being created, but nifi-app.log is never created. I tried changing the timestamp format of fileNamePattern to %d{yyyy-MM-dd_HH_mm} to trigger rollovers every minute. Again, log files including the timestamps are created, but nifi-app.log is not. I tried uncommenting the <file> line. Now, nifi-app.log is created, but rollover is no longer working - nifi-app.log is the only file that is created. It feels like I can either get nifi-app.log or rollover working at any one time, but never both at the same time. Any way to get both working at the same time?
... View more
10-06-2022
03:00 PM
Hi, This week I started facing an issue with a PutFile processor that was running for over a year without problems. This processor is getting blocked and start enqueuing flowfiles. When I tried to terminate the process inside Nifi it ends; but no matter how many times i try to restart it, the processor never works again. My next step is to shutdown Nifi. The shutdown process ends OK, but the Windows process never ends and kept temporary files locked and RAM memory allocate. But the worse part is that this process is impossible to kill. I tried to kill it from the task manager and got access error. Also tried to kill it from cmd (as administrator) using taskkill and wimc commands but the process does not died. Until now, the only solution that I have found is to restart the server. But even this solution works half way, because if I send the reboot from the server; this one stays (I guess) trying to kill the process and doesn't shut down. The only thing that has worked is to send the reboot from the administration console of my hosting provider. The following is the nifi-dump log: "Timer-Driven Process Thread-1 <Terminated Task>" Id=61 RUNNABLE (in native code)
at java.base@11.0.15/sun.nio.fs.WindowsNativeDispatcher.CreateFile0(Native Method)
at java.base@11.0.15/sun.nio.fs.WindowsNativeDispatcher.CreateFile(WindowsNativeDispatcher.java:71)
at java.base@11.0.15/sun.nio.fs.WindowsChannelFactory.open(WindowsChannelFactory.java:308)
at java.base@11.0.15/sun.nio.fs.WindowsChannelFactory.newFileChannel(WindowsChannelFactory.java:168)
at java.base@11.0.15/sun.nio.fs.WindowsFileSystemProvider.checkReadAccess(WindowsFileSystemProvider.java:330)
at java.base@11.0.15/sun.nio.fs.WindowsFileSystemProvider.checkAccess(WindowsFileSystemProvider.java:367)
at java.base@11.0.15/sun.nio.fs.AbstractFileSystemProvider.exists(AbstractFileSystemProvider.java:151)
at java.base@11.0.15/java.nio.file.Files.exists(Files.java:2435)
at org.apache.nifi.processors.standard.PutFile.onTrigger(PutFile.java:315)
at app//org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1202)
at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
at java.base@11.0.15/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base@11.0.15/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base@11.0.15/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base@11.0.15/java.lang.Thread.run(Thread.java:829)
Number of Locked Synchronizers: 1
"Timer-Driven Process Thread-10" Id=84 RUNNABLE (in native code)
at java.base@11.0.15/java.io.WinNTFileSystem.list(Native Method)
at java.base@11.0.15/java.io.File.normalizedList(File.java:1165)
at java.base@11.0.15/java.io.File.listFiles(File.java:1258)
at org.apache.nifi.processors.standard.GetFile.performListing(GetFile.java:321)
at org.apache.nifi.processors.standard.GetFile.onTrigger(GetFile.java:386)
at app//org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1202)
at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
at java.base@11.0.15/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base@11.0.15/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base@11.0.15/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base@11.0.15/java.lang.Thread.run(Thread.java:829)
Number of Locked Synchronizers: 2
- java.util.concurrent.locks.ReentrantLock$NonfairSync@6d7d76f3
- java.util.concurrent.ThreadPoolExecutor$Worker@153e2f2f
"Timer-Driven Process Thread-11" Id=6746 WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@6bb8fee2
at java.base@11.0.15/jdk.internal.misc.Unsafe.park(Native Method)
at java.base@11.0.15/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
at java.base@11.0.15/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)
at java.base@11.0.15/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1177)
at java.base@11.0.15/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base@11.0.15/java.lang.Thread.run(Thread.java:829)
"Timer-Driven Process Thread-12 <Terminated Task>" Id=6750 RUNNABLE (in native code)
at java.base@11.0.15/sun.nio.fs.WindowsNativeDispatcher.CreateFile0(Native Method)
at java.base@11.0.15/sun.nio.fs.WindowsNativeDispatcher.CreateFile(WindowsNativeDispatcher.java:71)
at java.base@11.0.15/sun.nio.fs.WindowsChannelFactory.open(WindowsChannelFactory.java:308)
at java.base@11.0.15/sun.nio.fs.WindowsChannelFactory.newFileChannel(WindowsChannelFactory.java:168)
at java.base@11.0.15/sun.nio.fs.WindowsFileSystemProvider.checkReadAccess(WindowsFileSystemProvider.java:330)
at java.base@11.0.15/sun.nio.fs.WindowsFileSystemProvider.checkAccess(WindowsFileSystemProvider.java:367)
at java.base@11.0.15/sun.nio.fs.AbstractFileSystemProvider.exists(AbstractFileSystemProvider.java:151)
at java.base@11.0.15/java.nio.file.Files.exists(Files.java:2435)
at org.apache.nifi.processors.standard.PutFile.onTrigger(PutFile.java:315)
at app//org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1202)
at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
at org.apache.nifi.controller.scheduling.AbstractTimeBasedSchedulingAgent.lambda$doScheduleOnce$0(AbstractTimeBasedSchedulingAgent.java:63)
at org.apache.nifi.controller.scheduling.AbstractTimeBasedSchedulingAgent$$Lambda$1526/0x0000000800f54040.run(Unknown Source)
at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
at java.base@11.0.15/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base@11.0.15/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base@11.0.15/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base@11.0.15/java.lang.Thread.run(Thread.java:829)
Number of Locked Synchronizers: 1
- java.util.concurrent.ThreadPoolExecutor$Worker@bbdcc1d
"Timer-Driven Process Thread-13" Id=6751 WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@6bb8fee2
at java.base@11.0.15/jdk.internal.misc.Unsafe.park(Native Method)
at java.base@11.0.15/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
at java.base@11.0.15/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)
at java.base@11.0.15/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1177)
at java.base@11.0.15/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
at java.base@11.0.15/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base@11.0.15/java.lang.Thread.run(Thread.java:829) In the Nifi-app.log does not exists a related message. As I mentioned before, this processor (or its process) has no had changes recently. But a new process that has several PutFile processor with high usage was recently deployed on the Nifi instance. However this new process is not having issues and is working without problem while the old process is having the described problem. I'll appreciate your help -------------------------- Nifi 1.14.0 OpenJDK 64-Bit Server VM Microsoft-32930 (build 11.0.15+10-LTS, mixed mode) Windows Server Std 2016 (10.0.14.393 b 14393) Allocate RAM 8G
... View more
Labels:
- Labels:
-
Apache NiFi
07-22-2022
08:59 AM
Hi All, The problem was on the JDK version. We were using OpenJDK 11.0.2 which had a bug in the TLS handshake. Solution: Upgrade JDK (now using 11.0.15).
... View more
04-02-2022
02:14 PM
Hi André, It works, however I'm still facing problems to start the MiNiFi, now I'm seeing the following errors in the nifi-app.log 2022-04-02 17:25:56,124 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 22, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,140 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 75, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,140 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 126, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,140 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 177, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 212, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 242, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 277, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 359, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 407, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,155 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 446, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,171 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 486, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,171 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 549, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,171 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 612, col 29: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
2022-04-02 17:25:56,191 WARN [main] org.apache.nifi.util.FlowParser Schema validation error parsing Flow Configuration at line 680, col 28: cvc-complex-type.2.4.a: Invalid content was found starting with element 'networkInterface'. One of '{inputPort, outputPort}' is expected.
2022-04-02 17:25:56,311 INFO [main] o.a.nifi.headless.HeadlessNiFiServer Loading Flow...
2022-04-02 17:25:56,343 WARN [main] o.a.nifi.headless.HeadlessNiFiServer Failed to start headless server... shutting down.
java.lang.Exception: Unable to load flow due to: java.lang.IllegalArgumentException: NiFi Sensitive Properties Key [nifi.sensitive.props.key] is required
at org.apache.nifi.headless.HeadlessNiFiServer.start(HeadlessNiFiServer.java:166)
at org.apache.nifi.minifi.MiNiFi.<init>(MiNiFi.java:163)
at org.apache.nifi.minifi.MiNiFi.<init>(MiNiFi.java:64)
at org.apache.nifi.minifi.MiNiFi.main(MiNiFi.java:265)
Caused by: java.lang.IllegalArgumentException: NiFi Sensitive Properties Key [nifi.sensitive.props.key] is required
at org.apache.nifi.encrypt.PropertyEncryptorFactory.getPropertyEncryptor(PropertyEncryptorFactory.java:42)
at org.apache.nifi.headless.HeadlessNiFiServer.start(HeadlessNiFiServer.java:125)
... 3 common frames omitted
2022-04-02 17:25:56,343 INFO [Thread-1] org.apache.nifi.minifi.MiNiFi Initiating shutdown of MiNiFi server...
2022-04-02 17:25:56,343 WARN [Thread-1] o.a.nifi.headless.HeadlessNiFiServer Problem occurred ensuring flow controller or repository was properly terminated due to java.lang.NullPointerException
2022-04-02 17:25:56,343 ERROR [Thread-1] org.apache.nifi.BootstrapListener Failed to communicate with Bootstrap. Bootstrap may be unable to issue or receive commands from MiNiFi
2022-04-02 17:25:56,343 INFO [Thread-1] org.apache.nifi.minifi.MiNiFi MiNiFi server shutdown completed (nicely or otherwise). About the warnings I could not find which processors in the flow has the maxconcurrentask unset, all have one as value (1). About the network interface, input and output ports warnings I suppose that it refers to the remote process group. In this point, I understand that, at least the network interface, is an optional parameter. The final error, nifi.sensitive.props.key. I seted this property but when minifi try to starts set the value to empty again and then fails. Thanks again.
... View more
03-31-2022
10:06 AM
1 Kudo
Hi André, That is what I needed. Thanks a lot. For those who are facing the same problem in windows; @araujo's solution also works with Powershell
... View more
03-03-2022
06:07 PM
1 Kudo
Hi @araujo , It is major head ache for me your findings as this is a crucial step in the process. But, at least I know what is happening. I will try to use another smtp server to check if the problem decreases. Unfortunately we don't have Cloudera support. I just opened the issue NIFI-9758 Thanks a lot for your help. Regards, Javier
... View more
06-10-2021
03:02 PM
Issue still present in 1.13.2. No workaround yet. It appears that will be fixed in 1.14 according to Jira NIFI-8400
... View more
06-09-2021
06:18 PM
Thanks for this excellent post, it works almost perfect in 1.13.0 version. The only problem I had was when did the last step (13) and the ConvertRecord processor became invalid with the following message: I found the solution to this issue in this post of @pvillard where he updates the schema.name property before de ConvertRecord processor. I didn't complete understand the reason but it works.
... View more