Member since
03-05-2021
19
Posts
3
Kudos Received
1
Solution
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 5928 | 07-22-2022 08:59 AM |
01-10-2023
06:10 PM
1 Kudo
Hi @edaley, I have a couple instances runnning on Windows and all of them rotates uses the TimeBasedRollingPolicy with the following configuration <appender name="APP_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<!-- file>${org.apache.nifi.bootstrap.config.log.dir}/nifi-app.log</file -->
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${org.apache.nifi.bootstrap.config.log.dir}/nifi-app_%d.log.zip</fileNamePattern>
<maxHistory>30</maxHistory>
</rollingPolicy>
<immediateFlush>true</immediateFlush>
<encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">
<pattern>%date %level [%thread] %logger{40} %msg%n</pattern>
</encoder> This configuration works over the nifi-app.log file and move it into a new file nifi-app_date.log.zip at midnight. Hope this helps.
... View more
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
07-12-2022
06:44 PM
Does the target URL hostname go to a LB that can route that request to any number of endpoint servers? I don't really know, but thing that this is the scenario. Perhaps not all those endpoint servers use the same serverAuth certificate or are not all signed by the same authority or an authority known the the truststore configured in the SSLContextService you have configured in your invokeHTTP processor. Is possible. I added the root certificate available on CA Authority to the keystore and will monitor the behavior.
... View more
07-12-2022
05:44 PM
Hi @araujo, Just today I detected more than 150 errors over around 400 HTTP request.
... View more
07-06-2022
12:38 PM
Hi, I am very frequently getting the following exception whenever I call the URL seen in the message. 2022-07-06 15:24:56,138 ERROR [Timer-Driven Process Thread-10] o.a.nifi.processors.standard.InvokeHTTP InvokeHTTP[id=33351c02-15ee-1ccc-6c00-dda0e16110ca] Routing to Failure due to exception: javax.net.ssl.SSLPeerUnverifiedException: Hostname creatorapp.zoho.com not verified (no certificates): javax.net.ssl.SSLPeerUnverifiedException: Hostname creatorapp.zoho.com not verified (no certificates)
javax.net.ssl.SSLPeerUnverifiedException: Hostname creatorapp.zoho.com not verified (no certificates)
at okhttp3.internal.connection.RealConnection.connectTls(RealConnection.kt:396)
at okhttp3.internal.connection.RealConnection.establishProtocol(RealConnection.kt:337)
at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:209)
at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:226)
at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:106)
at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:74)
at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:255)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
at okhttp3.internal.connection.RealCall.execute(RealCall.kt:154)
at org.apache.nifi.processors.standard.InvokeHTTP.onTrigger(InvokeHTTP.java:850)
at 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/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834) Some details about it: 1. The URL certificate is valid 2. The request is processed correctly on the second or third try and if several flowfiles are queued, the following messages may or may not present the same behavior. But usually the request is always processed. 3. I am using the self-signed certificate generated by Nifi. Thanks.
... View more
Labels:
- Labels:
-
Apache NiFi
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-29-2022
12:34 PM
Hi, An external process creates an error.file on certain events and updates the process log file. The process that I'm creating starts when the error.file is created and need to read the last 10 - 15 lines of the log.file. My problem is that the log.file does not rollover and just grows continually and neither follows a log standard in order to use SysLog processors. How can I get that last 10 - 15 lines of the log file? Something like ( "tail -15 log.file" ). Thanks in advance.
... View more
Labels:
- Labels:
-
Apache NiFi
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
03-03-2022
05:55 AM
Hi @araujo , Here you can find the nifi-app.log in Debug mode. This is the flowfile that was enqueue (just one flowfile when I checked) In the logs appears that the processor received the flowfile at 16:31:37,479 but almost instantly the process dyed -without clear reason- , and the mail only was send until 17:42:20,913 after I terminated/restarted the processor. The dump did not show anything different from my first post. As I can see, in the mean time the other Processor's task (Concurrent tasks = 2) continue working without problem. Also I noticed that while I was attempting to terminate the Processor the queue was appearing with one flow file enqueued, but when I tried to list the queue I got the message "The queue has no FlowFiles". I don't know if this is the normal behavior. Thanks
... View more
03-01-2022
08:16 AM
@araujo After month close, I have an approved manteinance window for tomorrow night. I tried to enable debug in in test instance, changing the root tag in the logback.xml <root level="DEBUG"> <appender-ref ref="APP_FILE" /> </root> But I got several hundreds of Mb in the log files in a few minutes. As I don't when the issue will appear; does exist some way to increase the log level in the nifi-app, but only for the PutEmail processor or its associate classes? I can see that related clasess to PutEmail are (until I can see): com.sun.mail.smtp jakarta.activation com.sun.mail.smtp jakarta.mail thanks
... View more