Created on 04-05-2017 04:32 PM - edited 09-16-2022 04:25 AM
Error we are getting is below.
Created 04-05-2017 04:35 PM
when ading a key to hte keytab file with the kadmin, a error could be encountered:
Unsupported key table format version number while adding key to keytab
local file to which you want to export the key (/etc/krb5.keytab) is in an incorrect format. This is usually because you have tried to create an empty file (using touch or similar commands) beforehand, and then export the key into it.
To verify that this is indeed the case, try running klist on the existing file to which you are attempting to export the key (you should run it in the source and target environment where the file is originated/used):
example:sudo klist -k /etc/keytab
It should return
klist: Unsupported key table format version number while starting keytab scan
This usually happens when the local file to which you want to export the key (/etc/krb5.keytab) is in an incorrect format. The most common reason why this would happen is if you have tried to create an empty file (using touch or similar commands) beforehand, and then export the key into it.
To verify that this is indeed the case, try running kliston the existing file to which you are attempting to export the key:
sudo klist -k /etc/keytab
klist: Unsupported key table format version number while starting keytab scan
if this is not the cause, use another option:
execute kdestroy and generate a new ticket and krb5cache”
Created 04-05-2017 04:35 PM
when ading a key to hte keytab file with the kadmin, a error could be encountered:
Unsupported key table format version number while adding key to keytab
local file to which you want to export the key (/etc/krb5.keytab) is in an incorrect format. This is usually because you have tried to create an empty file (using touch or similar commands) beforehand, and then export the key into it.
To verify that this is indeed the case, try running klist on the existing file to which you are attempting to export the key (you should run it in the source and target environment where the file is originated/used):
example:sudo klist -k /etc/keytab
It should return
klist: Unsupported key table format version number while starting keytab scan
This usually happens when the local file to which you want to export the key (/etc/krb5.keytab) is in an incorrect format. The most common reason why this would happen is if you have tried to create an empty file (using touch or similar commands) beforehand, and then export the key into it.
To verify that this is indeed the case, try running kliston the existing file to which you are attempting to export the key:
sudo klist -k /etc/keytab
klist: Unsupported key table format version number while starting keytab scan
if this is not the cause, use another option:
execute kdestroy and generate a new ticket and krb5cache”
Created 04-05-2017 07:28 PM
Also, another option is to execute kdestroy and generate a new ticket and krb5cache.
The documentation you need for HDP 2.4: https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.4.0/bk_dataintegration/content/hive-jdbc-odbc-d...
Created 04-05-2017 07:31 PM
executed kdestroy and generated a new ticket and krb5cache” worked