Member since
09-26-2024
31
Posts
8
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
181 | 04-29-2025 08:18 AM | |
147 | 04-16-2025 02:59 AM | |
184 | 03-27-2025 11:41 PM |
04-29-2025
08:18 AM
Referred to my older thread for the fix https://community.cloudera.com/t5/Support-Questions/NiFi-file-transfer-report/m-p/407109#M252612
... View more
04-29-2025
08:15 AM
@Shelton We just followed Steps 1,3 4 and 5 to generate the automated report to Elasticsearch. It was pretty straight forward. Only things is we had to do was enable firewall in our Docker container and update Input Port's Access Policies. Thanks
... View more
04-27-2025
10:56 PM
1 Kudo
The issue has been fixed.
... View more
04-27-2025
10:54 PM
1 Kudo
Sorry for very late reply, your response helped us a lot to set up Provenance Thank you so much.
... View more
04-26-2025
10:19 AM
We are able to get past all the SSL related errors, there were changes required in nifi.properties. Now we don't see any errors on the SiteToSiteReportingRecordSink service. However we still don't see any data coming on he Input Port
... View more
04-25-2025
09:15 AM
Hi We are using SiteToSiteReportingRecordSink to generate file transfer report with below setting We are trying to send the data to the same server where we have added input port processor. Below is the nifi.property setting, do we need to change anything here ?? # Site to Site properties
nifi.remote.input.host=52564f1f10ff
nifi.remote.input.secure=true
nifi.remote.input.socket.port=10000
nifi.remote.input.http.enabled=true
nifi.remote.input.http.transaction.ttl=30 sec
nifi.remote.contents.cache.expiration=30 secs
# web properties #
#############################################
# For security, NiFi will present the UI on 127.0.0.1 and only be accessible through this loopback interface.
# Be aware that changing these properties may affect how your instance can be accessed without any restriction.
# We recommend configuring HTTPS instead. The administrators guide provides instructions on how to do this.
nifi.web.http.host=
nifi.web.http.port=
nifi.web.http.network.interface.default= we are getting below warning continuously, is this something do do with SSL cert ? Thanks
... View more
Labels:
- Labels:
-
Apache NiFi
04-16-2025
02:59 AM
@MattWho Was able to resolve the issue. The issue was with the request we are sending which was missing the "Password" value. Sorry for ticket.
... View more
04-15-2025
08:47 PM
@MattWho We create all our processors using NiFi API. For ListSFTP we pass remote SFTP user credential in our REST POST API process-groups/{id}/processors Looks like "Password" property which we pass in the POST request is not getting set correctly. Thanks
... View more
04-15-2025
10:51 AM
Hi We are using NiFi API to create ListSFTP processor. When trying to connect to remote host we get below error. Caused by: net.schmizz.sshj.userauth.UserAuthException: Exhausted available authentication methods When we update the "Password" manually in the processor it works fine. We validated that the password value is sent with correct data but for some reason its not getting set using API. Do we need to do anything extra for setting the password using API, Thanks
... View more
Labels:
- Labels:
-
Apache NiFi
04-14-2025
08:12 AM
Thanks @MattWho for your response.
... View more