About araujo

araujo · ‎02-28-2022

@Ros , I imagine that despite the error your connection is working fine, right? If that's the case, you can safely ignore the error messages. Andre

araujo · ‎02-28-2022

@yagoaparecidoti , Could explain which steps you took to generate your server.jks file? André

araujo · ‎02-28-2022

@myuintelli2021 , Good point! I hadn't noticed that. Alternatively, you can download the NiFi Toolkit and use the encrypt-config.bat to perform the key migration. Check this out: https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#sensitive-property-key-migration The toolkit contains a Windows version of the script (encrypt-config.bat). HTH, André

araujo · ‎02-28-2022

You should always use the fully qualified hostnames, instead of IP addresses. Although it's longer, it can prevent problems. If your cluster is using TLS, for example, the full hostnames are required. I imagine these logs that you shared are client logs, right? Can you check the Tablet Server logs and see if there are errors in them? Those would help understand the issue. André

araujo · ‎02-28-2022

@CookieCream , What do you mean by "made the http post empty"? I would suggest that you remove your NiFi directory and restart from scratch following these instructions: https://nifi.apache.org/docs/nifi-docs/html/getting-started.html#downloading-and-installing-nifi If you follow the exact instructions the installation should work without problems. Cheers, André

araujo · ‎02-27-2022

@SamarApple , Would you be able to share your authorizers.xml configuration and the full stack trace from nifi-app.log or nifi-user.log? Cheers, André

araujo · ‎02-27-2022

Hi @mehmetersoy , You can open a ticket with support and associate it with CDP. We can check if there are any Samba dependencies required for CDP and advise if the CVE applies to it or not. Cheers, André

araujo · ‎02-26-2022

@myuintelli2021 The NiFi binaries come with a run-nifi.bat in addition of nifi.sh. André

araujo · ‎02-26-2022

Hi @CookieCream NiFi in the latest version is deployed automatically with security and TLS enabled. You need to set the single user credentials and connect to port 8443 instead of 8080. Please check the documentation: https://nifi.apache.org/docs/nifi-docs/html/getting-started.html#i-started-nifi-now-what Cheers André

araujo · ‎02-24-2022

@wert_1311 , Kerberos issue can be a hard thing to troubleshoot. I've done a LOT of troubleshooting involving Kerberos and I still find myself stumped at times. What's in the krb5kdc.log rarely matters. The best way to find out what's going on is to look at the client log. Enable debug logging for your application and ensure you also toggle debug mode for the Kerberos modules with -Dsun.security.krb5.debug=true for your application. Look at and read the logs carefully, and google a lot 🙂 Kerberos debug logs are rarely intuitive. If you can share some of that here it might help us find some clues as to what is going on. If you can't, I understand. Good luck. André

Online	Offline
Last Visited	‎07-21-2025 10:25 PM

Member Since	‎06-26-2015 11:59 AM
Last Visited	‎07-21-2025 10:25 PM
Posts	515
Kudos received	138

Cloudera Community

Re: Is it possible to use Single User authenticati...

Re: Dynamically Assign an XSD File

Re: "error": "There is no mapped role for the grou...

Re: Read xml file content into an Attribute: How t...

Re: Nifi Lookup CSV values with SQL NULL values

Re: log4j error - com.cloudera.impala.jdbc42.inter...

Re: Cloudera Manager - javax.net.ssl.SSLException:...

Re: Changing nifi.sensitive.props.key value??

Re: KUDU NoLeaderFound Issue

Re: Nifi starts without error but cannot connect

Re: NIFI SAML Error

Re: Are samba packages necessary on Cloudera platf...

Re: Changing nifi.sensitive.props.key value??

Re: Nifi starts without error but cannot connect

Re: Kerberos Logging