- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
NiFi PutHDFS Login Failure using kerberos
- Labels:
-
Apache NiFi
Created ‎09-29-2017 07:15 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am getting a login failure when trying to use the PutHDFS processor.
These are the things I have verified:
- nifi.kerberos.krb5.file is set correctly
- nifi account has read permissions to keytab and krb5.conf
- I am able to kinit using the keytab/principal from the nifi account
Environment is HDF 3.0.1 (NiFi 1.2) to HDP 2.6.x
Is there something I am missing?
Created ‎11-15-2017 06:07 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you get this resolved? I'm facing the exact same issue as you are in this thread.
Created ‎11-15-2017 07:00 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, it was resolved. But I don't have a good explanation. It actually resolved itself by simply restarting the NiFi process on all nodes. After the restart they all connected and worked as expected.
Created ‎11-15-2017 07:41 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Interesting. I performed several restarts and kept receiving the error "Unable to obtain password from user". I then decided to perform a full stop, wait a couple minutes, then start (I have 2 NiFi nodes) and now its working. Very strange...
Created ‎08-03-2018 09:44 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Benjamin Hopp @Chad Woodhead
I had the exact same issue and tried bringing down both of my two NiFi nodes, waiting a few minutes, and brought them back online. Then I tried turning on the PutHDFS processor and it worked properly.
Has anyone figured out why this solves the issue or what is causing this problem?

- « Previous
-
- 1
- 2
- Next »