Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

Generate missing credetials - KDC

avatar
New Contributor

Hello, 

Im currently setting new cluster.  When I try to start some role I get notifications that: 
Role is missing Kerberos keytab. Go to the Kerberos Credentials page and click the Generate Missing Credentials button.

So I try to Generate Missing credentials and I got:

 

failed script:/opt/cloudera/cm/bin/merge_credentials.sh due to:/opt/cloudera/cm/bin/merge_credentials.sh failed with exit code 1 and output of <<
+ export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/usr/kerberos/bin:/usr/kerberos/sbin:/usr/lib/mit/sbin:/usr/sbin:/usr/lib/mit/bin:/usr/bin
+ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/usr/kerberos/bin:/usr/kerberos/sbin:/usr/lib/mit/sbin:/usr/sbin:/usr/lib/mit/bin:/usr/bin
+ KEYTAB_OUT=/var/run/cloudera-scm-server/cmf-merged-out15742810764060677617.keytab
+ shift
+ ktutil
+ chmod 600 /var/run/cloudera-scm-server/cmf-merged-out15742810764060677617.keytab
chmod: cannot access '/var/run/cloudera-scm-server/cmf-merged-out15742810764060677617.keytab': No such file or directory

 

 What am I missing here ? 

 

1 ACCEPTED SOLUTION

avatar
New Contributor

I found a solution for this trouble. I removed kerberos DB with kdb5-util destroy and I recreate it again kdb5-util create -s.

Other thing what I found was that, when I firstly created admin cloudera principal I used cloudera-scm instead of cloudera-scm/admin. I am not sure if this could caused problem, but after destroying old DB and created cloudera-scm/admin, generating is working properly. 

 

View solution in original post

4 REPLIES 4

avatar
Community Manager

@davdop Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our CDP experts @venkatsambath @abdulpasithali  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.


Regards,

Diana Torres,
Senior Community Moderator


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community:

avatar
Master Collaborator

Hi @davdop 

Could you please check if you are able to run kadmin remotely from your Cloudera Manager host and manage KDC ? It looks like a communication issue with KDC server

avatar
New Contributor

Hello, @shubham_sharma 

you mean use kadmin without .local ? I have KDC installed on different host than CM. 

avatar
New Contributor

I found a solution for this trouble. I removed kerberos DB with kdb5-util destroy and I recreate it again kdb5-util create -s.

Other thing what I found was that, when I firstly created admin cloudera principal I used cloudera-scm instead of cloudera-scm/admin. I am not sure if this could caused problem, but after destroying old DB and created cloudera-scm/admin, generating is working properly.