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!

How to Find Missing Keytab Files in Cloudera Manager /var/run/cloudera-scm-agent/process/

avatar
Explorer

Hi,

 

I have enabled kerberos in my cloudera cluster using Cloudera Manager.

Kerberized cluster is running fine. But I'm unable to get the location of keytab files (eg. hdfs.keytab, yarn.keytab etc).

The keytab location property is also missing from the *-site.xml files.

 

Where can I get the location of those keytab files.

 

Regards,

Amit

1 ACCEPTED SOLUTION

avatar
Master Collaborator

The keytabs are pushed from a database to a runtime location at startup of services, what you are describing as a configuration is not really viable from what I understand. You will see /var/run/cloudera-scm-agent/process/ but this is ephemeral, next restart will have another locaiton. You could experiment with trying to provide the manual keytabs through safety valve to the necessary services.

View solution in original post

4 REPLIES 4

avatar
Expert Contributor

keytab files are managed by cloudera manager . you can find them in /var/run/cloudera-scm-agent/process

avatar
Visitor
export dirname=/var/run/cloudera-scm-agent/process/
sudo find $dirname -not -empty `-ls -l` | grep keytab
 

avatar

They will be in the process directory for the component. For example:

 

hive.keytab is in: 

/var/run/cloudera-scm-agent/process/*-hive_on_tez-HIVESERVER2

 

 

avatar
Master Collaborator

The keytabs are pushed from a database to a runtime location at startup of services, what you are describing as a configuration is not really viable from what I understand. You will see /var/run/cloudera-scm-agent/process/ but this is ephemeral, next restart will have another locaiton. You could experiment with trying to provide the manual keytabs through safety valve to the necessary services.