Right. ... View more

Hi MattWho,   I am not able to access the NiFi UI. There its saying "This site can’t be reached". Below is the error that I am getting:     2023-07-31 14:01:24,921 ERROR [External Resource Provider Service - NAR Auto-Loader Provider - NAR Auto-Loader Provider - b1ef45bd-ef3f-4866-8f9e-5b4b1e38df8a] o.a.n.f.r.ConflictResolvingExternalResourceProviderWorker Error during polling for external resources javax.net.ssl.SSLException: readHandshakeRecord at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1309) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:435) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:197) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1567) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1495) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:352) at org.glassfish.jersey.client.internal.HttpUrlConnector._apply(HttpUrlConnector.java:409) at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:273) at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:300) at org.glassfish.jersey.client.JerseyInvocation.lambda$invoke$1(JerseyInvocation.java:675) at org.glassfish.jersey.client.JerseyInvocation.call(JerseyInvocation.java:697) at org.glassfish.jersey.client.JerseyInvocation.lambda$runInScope$3(JerseyInvocation.java:691) at org.glassfish.jersey.internal.Errors.process(Errors.java:292) at org.glassfish.jersey.internal.Errors.process(Errors.java:274) at org.glassfish.jersey.internal.Errors.process(Errors.java:205) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:390) at org.glassfish.jersey.client.JerseyInvocation.runInScope(JerseyInvocation.java:691) at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:674) at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:422) at org.glassfish.jersey.client.JerseyInvocation$Builder.get(JerseyInvocation.java:318) at org.apache.nifi.registry.client.impl.JerseyBundleVersionClient.lambda$getBundleVersions$2(JerseyBundleVersionClient.java:173) at org.apache.nifi.registry.client.impl.AbstractJerseyClient.executeAction(AbstractJerseyClient.java:103) at org.apache.nifi.registry.client.impl.JerseyBundleVersionClient.getBundleVersions(JerseyBundleVersionClient.java:156) at org.apache.nifi.registry.extension.NiFiRegistryExtensionRegistry.getExtensionBundleMetadata(NiFiRegistryExtensionRegistry.java:85) at org.apache.nifi.registry.extension.NiFiRegistryExternalResourceProvider.listResources(NiFiRegistryExternalResourceProvider.java:69) at org.apache.nifi.flow.resource.ConflictResolvingExternalResourceProviderWorker.poll(ConflictResolvingExternalResourceProviderWorker.java:113) at org.apache.nifi.flow.resource.ConflictResolvingExternalResourceProviderWorker.run(ConflictResolvingExternalResourceProviderWorker.java:86) at java.lang.Thread.run(Thread.java:748) Suppressed: java.net.SocketException: Broken pipe (Write failed) at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111) at java.net.SocketOutputStream.write(SocketOutputStream.java:155) at sun.security.ssl.SSLSocketOutputRecord.encodeAlert(SSLSocketOutputRecord.java:81) at sun.security.ssl.TransportContext.fatal(TransportContext.java:355) at sun.security.ssl.TransportContext.fatal(TransportContext.java:267) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:438) ... 28 common frames omitted Caused by: java.net.SocketException: Broken pipe (Write failed) at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111) at java.net.SocketOutputStream.write(SocketOutputStream.java:155) at sun.security.ssl.SSLSocketOutputRecord.flush(SSLSocketOutputRecord.java:251) at sun.security.ssl.HandshakeOutStream.flush(HandshakeOutStream.java:89) at sun.security.ssl.CertificateVerify$T12CertificateVerifyProducer.produce(CertificateVerify.java:769) at sun.security.ssl.SSLHandshake.produce(SSLHandshake.java:421) at sun.security.ssl.ServerHelloDone$ServerHelloDoneConsumer.consume(ServerHelloDone.java:182) at sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:377) at sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:444) at sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:422) at sun.security.ssl.TransportContext.dispatch(TransportContext.java:182) at sun.security.ssl.SSLTransport.decode(SSLTransport.java:152) at sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1392) at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1300) ... 29 common frames omitted 2023-07-31 14:06:24,946 ERROR [External Resource Provider Service - NAR Auto-Loader Provider - NAR Auto-Loader Provider - b1ef45bd-ef3f-4866-8f9e-5b4b1e38df8a] o.a.n.f.r.ConflictResolvingExternalResourceProviderWorker Error during polling for external resources javax.net.ssl.SSLException: readHandshakeRecord at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1309) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:435) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:197) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1567) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1495) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:352) at org.glassfish.jersey.client.internal.HttpUrlConnector._apply(HttpUrlConnector.java:409) at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:273) at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:300) at org.glassfish.jersey.client.JerseyInvocation.lambda$invoke$1(JerseyInvocation.java:675) at org.glassfish.jersey.client.JerseyInvocation.call(JerseyInvocation.java:697) at org.glassfish.jersey.client.JerseyInvocation.lambda$runInScope$3(JerseyInvocation.java:691) at org.glassfish.jersey.internal.Errors.process(Errors.java:292) at org.glassfish.jersey.internal.Errors.process(Errors.java:274) at org.glassfish.jersey.internal.Errors.process(Errors.java:205) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:390) at org.glassfish.jersey.client.JerseyInvocation.runInScope(JerseyInvocation.java:691) at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:674) at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:422) at org.glassfish.jersey.client.JerseyInvocation$Builder.get(JerseyInvocation.java:318) at org.apache.nifi.registry.client.impl.JerseyBundleVersionClient.lambda$getBundleVersions$2(JerseyBundleVersionClient.java:173) at org.apache.nifi.registry.client.impl.AbstractJerseyClient.executeAction(AbstractJerseyClient.java:103) at org.apache.nifi.registry.client.impl.JerseyBundleVersionClient.getBundleVersions(JerseyBundleVersionClient.java:156) at org.apache.nifi.registry.extension.NiFiRegistryExtensionRegistry.getExtensionBundleMetadata(NiFiRegistryExtensionRegistry.java:85) at org.apache.nifi.registry.extension.NiFiRegistryExternalResourceProvider.listResources(NiFiRegistryExternalResourceProvider.java:69)   Can you please help? Thank you.   ... View more

@Kiranq  What version of Java is your NiFi using? Sharing the output for your NiFi-Registry configured keystore and truststore in the nifi-registry.properties file would help. Sharing the keystore and truststore configured in your NiFi registry client would help as well. ./keytool -v -list -keystore <keystore or trustsore> You can also use openssl to see what is sent from the server (NiFi-Registry) to client (NiFi) in the initial TLS exchange. ./openssl s_client -connect <nifi-regisry hostname>:<NiFi-Registry port> -showcerts Matt ... View more

@Sivaluxan NiFi exposes APIs for a lot of endpoints.  So not really sure what you are trying to accomplish in your use case.  If you want to use a third party app to access info exposed by NiF that is possible.  Or are you trying to setup some custom endpoint to expose some custom data? Here you can find NiFi Rest-Api documentation for the latest NiFi release: https://nifi.apache.org/docs/nifi-docs/rest-api/index.html You can also find the NIFi rest-api documentation for your installed release directly in the application via the global menu ( 3 horizontal lines upper right corner of UI) --> help.   If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more

@Fabricio 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

@Phil_I_AM  Always best tot start a new question rather than commenting on an old post.  Will get you better traction that way from the community. The reason NiFi does not have native processor that can handle rar files is because there does not appear to be java native libraries available to do this. https://issues.apache.org/jira/browse/NIFI-8391   You may consider filtering and writing your rar files to a flow specific directory on disk and then use the ExecuteStreamCommand processor to unpack that rar in that directory.  You could have a new flow that uses the listFile (configured to ignore files with rar extension) and FetchFile processor to monitor that directory for new files and consume them for further processing. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more

Hello, I am also trying same think i am trying to get data from another tool using invokeHttp process but where i need to pass access token and parameter i am not able to understand it if you have resolve it please help me.   Thank you Digambar ... View more

@SowmyaP  I am not clear on what you are trying to accomplish by specific order of restarts, starts and stops. Can you provide some details around the use case you are trying to implement and why? In a NiFi cluster the cluster roles "Primary" node and "Cluster Coordinator" node are elected by Zookeeper. Other nodes on the cluster have no specific assigned role.  Which node is assigned to these roles can change at anytime, so I am not clear on the importance of specific restart order.  If you have designed dataflows around a requirement that a specific node is always the "Primary" elected node, that can't be guaranteed.  In your first "Restart" scenario, assuming that what you mean by "secondary nodes" is any node that is not elected the "Primary" role,  each secondary node will restart and rejoin the cluster. If one of those secondary nodes was elected the "Cluster Coordinator" role, that role will switch to another node still running in the cluster.  The node elected the "primary" role should retain that role; however, when you then restart the "Primary" node, the "Primary" role will be elected to one of the other nodes in the cluster.  When the previous elected "Primary" node rejoins cluster, it will NOT reassume the "Primary" node role. In your second "start" scenario, assuming all nodes are currently stopped, you can start just the node you want to be elected the "primary" role and wait for that node to completely start and get elected with both the "primary" and "cluster coordinator" roles.  Essentially if you access the cluster UI at this point it would show 1 of 1 connected nodes.  Then you can start your secondary nodes and they will join the already established cluster. Third "Stop" scenario, it really does not matter which node you stop first.  They get their roles assigned by Zookeeper. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more

@Diga  In a scenario like this, the first thing to ask yourself is "How would I do this outside of NiFi?".  If you were to use curl from command line, how would you handle authentication with the Polarion ALM rest-api endpoints?  The answer there would help with how you would handle it within NiFi and assist in getting a better response in the community.  @SAMSAL provided some great suggestions of possible methods. Matt ... View more