Member since
01-19-2017
3679
Posts
632
Kudos Received
372
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 809 | 06-04-2025 11:36 PM | |
| 1390 | 03-23-2025 05:23 AM | |
| 689 | 03-17-2025 10:18 AM | |
| 2490 | 03-05-2025 01:34 PM | |
| 1625 | 03-03-2025 01:09 PM |
10-12-2017
08:28 AM
1 Kudo
@forest lin The kdc.conf looks fine, but your initial and final krb5.conf don't look correct you forgot to add the entry in lowercase see below !. Please backup of your current krb5.conf on all the hosts and replace them with the below exactly as it is. [libdefaults]
renew_lifetime = 7d
forwardable = true
default_realm = ABC.COM
ticket_lifetime = 24h
dns_lookup_realm = false
dns_lookup_kdc = false
default_ccache_name = /tmp/krb5cc_%{uid}
#default_tgs_enctypes = aes des3-cbc-sha1 rc4 des-cbc-md5
#default_tkt_enctypes = aes des3-cbc-sha1 rc4 des-cbc-md5
[domain_realm]
abc.com = ABC.COM
.abc.com = ABC.COM
[logging]
default = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
kdc = FILE:/var/log/krb5kdc.log
[realms]
ABC.COM = {
admin_server = nn1-dev1-tbdp
kdc = nn1-dev1-tbdp
} Did you re-run the below to correctly setup the KDC and KDC Admin hostnames dpkg-reconfigure krb5-kdc Can you also validate that the host entries on all the hosts are the same and include the KDC server host entry? What the content of your kadm5.acl file? On the KDC server can you paste the output of the below command. Please obscure the domain name # kdestroy
# kadmin.local
Authenticating as principal root/admin@ABC.COM with password.
kadmin.local: listprincs After validating and changing the above restart the services service krb5-kdc restart
service krb5-admin-server restart Don't forget to enable auto-restart of kdc and kadmin use appropriate ubuntu command chkconfig krb5kdc on
chkconfig kadmin on Now try the Ambari--> Kerberos wizard again it should succeed The logs are in these directories on the KDC and Clients default = /var/log/krb5kdc.log
admin_server = /var/log/kadmind.log
kdc = /var/log/krb5kdc.log Please revert
... View more
10-11-2017
12:34 PM
@forest lin You need to change the REAL entry in your /etc/krb5.conf to be like below and distribute to all the nodes in the cluster [domain_realm]
abc.com = ABC.COM
.abc.com = ABC.COM Instead of [domain_realm]
ABC.COM = ABC.COM You must validate that the other files kdc.conf,kadm5.acl are correct
... View more
10-09-2017
09:21 AM
@Mustafa Kemal MAYUK, There are a couple of things that could be wrong,first step -re-run the Ambari UI kerberos wizard and ensure it regenerates the principals/keytabs without any error On the node where the services are running check that the keytabs were gerenerate in /etc/security/keytabs/* On the KDC server validate that the principals were created # kadmin.loca l
kadmin.local listprincs All the principals in question should be in the KDC database Check that the keytabs are mapped to the correct principal. # klist -kt /etc/security/keytabs/yarn.service.keytab
Keytab name: FILE:/etc/security/keytabs/yarn.service.keytab
KVNO Timestamp Principal
---- ------------------- ------------------------------------------------------
1 08/24/2017 15:42:24 yarn/{host_FQDN}@REALM
1 08/24/2017 15:42:24 yarn/{host_FQDN}@REALM
1 08/24/2017 15:42:24 yarn/{host_FQDN}@REALM
1 08/24/2017 15:42:24 yarn/{host_FQDN}@REALM
1 08/24/2017 15:42:24 yarn/{host_FQDN}@REALM Using the correct principal grab a kerberos ticket # kinit -kt /etc/security/keytabs/yarn.service.keytab yarn/{host_FQDN}@REALM Check that a valid ticket was issued # klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: yarn/{host_FQDN}@REALM
Valid starting Expires Service principal
10/09/2017 11:13:07 10/10/2017 11:13:07 krbtgt/REALM@REALM In ambari start that particular service in the above case YARN Please revert
... View more
10-09-2017
06:13 AM
@dsun I think nothing is wrong with the upgrade please run these 2 statements and it should resolve the problem grant all privileges on *.* to 'rangerdba'@'scregionm1.field.hortonworks.com' identified by '{ranger_password}';
grant all privileges on *.* to 'rangerdba'@'localhost'; Please revert
... View more
10-08-2017
06:49 PM
@dsun Did you create a dump of the ranger batabase before the upgrade? If not then create one,while looged in as mysql root user mysqldump ranger > ranger_db.sql It seems the below statement will fail as your current password is wrong. mysql -u rangerdba -p{password} Try the alternative to change the rangerdba password while logged on as mysql root user, below is an example update user set password=PASSWORD('your_new_password') where User='user-name-here';
flush privileges; Then use the new credentials in Ambari UI-->Ranger-->Configs--->Ranger Admin to test connection verify that it works Hope that helps
... View more
10-08-2017
06:01 PM
@dsun It looks your ranger database is up and running correctly, can you validate that the in Ambari UI-->Ranger-->Configs--->Ranger Admin that the test connection works especially check the JDBC connect string for a Ranger database and the Ranger DB password. Please let me know if you still encounter problems.
... View more
10-06-2017
05:20 PM
@Sam Red There could be a couple of reasons here. First make sure the KDC and Kadmin is running assuming you are on RHEL/Centos7 Check the current status these 2 deamons should be running # systemctl status krb5kdc.service
# systemctl status kadmin.service If they are not running please, enable them so at next reboot they autostart # systemctl enable kadmin.service
# systemctl enable krb5kdc.service Start the services # systemctl start krb5kdc.service
# systemctl start kadmin.service As the root user check that the principals are in the KDC database # kadmin.local
Authenticating as principal root/admin@RELAY.COM with password.
kadmin.local: listprincs First forcefully expire the current kerberos credentials, log on as user hdfs or whatever # kdestroy Validate that no credentials are cached # klist
klist: No credentials cache found (filename: /tmp/krb5cc_0) To see what keytab entries in that keytab file, use klist # klist -kte /etc/security/keytabs/spnego.service.keytab
Keytab name: FILE:/etc/security/keytabs/spnego.service.keytab
KVNO Timestamp Principal
---- ------------------- ------------------------------------------------------
1 08/24/2017 15:42:23 HTTP/hostname@RELAY.COM (aes256-cts-hmac-sha1-96)
1 08/24/2017 15:42:23 HTTP/hostname@RELAY.COM (des-cbc-md5)
1 08/24/2017 15:42:23 HTTP/hostname@RELAY.COM (arcfour-hmac)
1 08/24/2017 15:42:23 HTTP/hostname@RELAY.COM (aes128-cts-hmac-sha1-96)
1 08/24/2017 15:42:23 HTTP/hostname@RELAY.COM (des3-cbc-sha1) The grab a valid kerberos using the info above # kinit -kt /etc/security/keytabs/spnego.service.keytab HTTP/hostname@RELAY.COM Now retry
... View more
10-06-2017
01:05 PM
@D Giri Can you descript your cluster setup (master, Slave and Edge nodes) Okay what are the new components you are trying to install? You could be checking for the keytabs on the wrong host, can you rerun the below command # kadmin.local
Authenticating as principal root/admin@REALM with password.
kadmin.local: listprincs All the principals created should be visible in the KD database. If the principal for the component is present take note of the host and try to locate the keytabs in the below location of that node /etc/security/keytabs Please let me know
... View more
10-05-2017
04:36 PM
@Pooja Kamle That's is the desired presentation for a normal user. Unless you want your AD user(s) to have admin rights which will imply that your AD user can basically do anything in Ranger, delete,update etc which I don't think is your target. You can you log out from your AD account and log on using admin/admin then under Ranger_UI -->Settings---User under User List search for your AD user and change the role to Admin Logout of admin account and log in using your AD user you will see that you have access to all the tabs. Hope that answers you.
... View more