1. Get the node has keytab. Ex: I am using the node which belongs to impala daemon. 2. Go to /var/run/cloudera-scm-agent/process and ls, it will list the process 3. cd xxxxxx-impala-IMPALAD .. ## Run ls cmd and make sure it has impala.keytab 4. klist -kt impala.keytab ## This will list all the available and valid principals 5. kinit -kt impala.keytab <copy paste the valid principal from the above step> 6. klist ## make sure kinit initiated
I checked the logs and I saw that the error that I was getting on starting a service was caused from a certain process so I got in that directory and looked for the error on hdfs.keytab. When doing the klist -kt hdfs.keytab I got the principals list, tried to make a kinit with one of them and it worked well.
What I've seen is that the imported keytabs I was trying to klist were some old keytab files, modified few weeks ago, and the logs gave me the clue on which directory test the keytab files.
So we are at the same point, seems that krb5-workstation commands work fine, keytabs were generated right and the service keeps outputing the same error again and again.