About saranvisa

saranvisa · ‎12-20-2016

Since you update nameservice just now, it may require a restart! not sure... pls query after cluster restart! it may help

saranvisa · ‎12-20-2016

I still didn't get answer for describe formatted tablename!!

saranvisa · ‎12-20-2016

To make it more easier CM -> HDFS -> Configuration -> NameNode Nameservice I assume it was "nameservice1" before and "zeus.corpdom.com now". Also did you check the location from "describe formatted tablename" in Hive. If the location refers to nameservice1 then change either NameNode Nameservice name or Hive table location. If you have very less tables, then I would recommand to change the hive table location to match with NameService. Hope this helps!

saranvisa · ‎12-20-2016

Did you enable High Availability by any chance? Did you chance your dfs.nameservices by any chance?

saranvisa · ‎12-20-2016

@cpuengr Did you rename your cluster as part of upgrade? By default the name is nameservice1. Did you modify it as zeus.corpdom.com by any chance? Login to CM -> Left Top green button name Also check your table location from the below command. describe formatted tablename; Thanks Kumar

saranvisa · ‎12-17-2016

@cpuengr Pls check with your admin that any security implemented as part of upgrade. I can see the keyword sentry in your hdfs path. so you might need a proper role level access to query your table. Also + denotes ACL implemention. Are you using same login for your hive and hdfs? In case if you are using Hue for Hive You will get very highlevel information about security in this path https://community.cloudera.com/t5/Security-Apache-Sentry/Hadoop-Security-for-beginners/m-p/48576 Thanks Kumar

saranvisa · ‎12-14-2016

Issue fixed!! My bad! From our list of nodes, i know either node01 or node02 has krb5-server. So I randomly pick the node01 and applied kadmin.local command, it worked, so started applying change password and endup with failure (Note: kadmin.local command is working in both node01 and node02). Latter realized node02 is our krb5-server from the below configuration. so login to node02 and delete & recreated the principal. it is working fine now from all our nodes... cat /etc/krb5.conf [realms] *** = { kdc = node01:88 kdc = node02:88 admin_server = node02:749 default_domain = *** max_renewable_life = 7d max_life = 7d } Thanks Kumar

saranvisa · ‎12-14-2016

Issue resolved...I made few mistakes and resolved one by one 1. The below file is a temporary keytab which will be generated automatically everytime we try CM -> Administration -> Setting -> Import KDC Account Manager Credentials This will be automatically removed after every attempt and will not be available for our manual reference. This is NOT an issue /var/run/cloudera-scm-server/cmf4310122296840901236.keytab 2. If you are planning to import KDC account using Wizard then no need to manually enter any service related principal kadmin.local: listprincs oozie/<Master_Domain>@AWS.COM oozie/<Master_hostname>@AWS.COM 3. # Cloudera Manager -> Administration -> Security -> Kerberos Credentials -> Configuration a. Update REALM.COM b. Update Host c. Update Encryption Type and few more corrections made and working fine Thanks Kumar

saranvisa · ‎12-13-2016

One of our user lost her kerberos password and I am trying to reset the password using below steps kadmin.local: kadmin.local: change_password user@REALM.COM Enter password for principal "user@REALM.COM": Re-enter password for principal "user@REALM.COM": Password for "user@REALM.COM" changed. kadmin.local:q Trying to login with new password after that but getting the below error kinit user@REALM.COM Password for user@REALM.COM: kinit: Password incorrect while getting initial credentials So I drop the user principal using delprinc and recreated with new password but still getting the same error Then I've created a keytab and tried to access user using keytab, it is working kadmin.local:xst -norandkey -k /tmp/user.keytab user@REALM.COM $kinit user@REALM.COM -k -t /tmp/user.keytab But the below command still shows the error. $kinit user@REALM.COM kinit: Password incorrect while getting initial credentials Can someone help me on this? Thanks Kumar

saranvisa · ‎12-10-2016

It seems you are enabling Kerberos using Cloudera Manager Wizard. Generally we may get into two different issue for KDC while Import KDC Account Manager Credentials. Let me give tips for both of them Pre-request: a. Make sure all the configuration files are updated with proper REALM b. Make sure kerberos DB has been created c. Make sure principals are created 1. Issue: kinit: Cannot contact any KDC for realm 'REALM NAME' while getting initial credentials Ans: Start the required services as follows service kadmin start service krb5kdc start 2. Issue: kinit: Cannot find KDC for requested realm while getting initial credentials Ans: Before press the "Import KDC Account Manager Credentials" button. Make sure the configuration files are updated in Cloudera Manager (Note: This is different from the configuration file update that i've mentioned in the prerequest section. This is a direct update in CM) CM -> Adminstration-> Setting -> REALM = REALM Name CM -> Adminstration-> Setting -> KDC SERVER HOST = HOST Name Thanks Kumar

Online	Offline
Last Visited	‎08-10-2019 05:12 PM

Member Since	‎09-02-2016 11:35 AM
Last Visited	‎08-10-2019 05:12 PM
Posts	523
Kudos received	96

Cloudera Community

Re: Promoting Metadata

Re: Mix on premise and cloud nodes

Re: impala-shell

Re: How do I see user usage stats by table in Impa...

Re: Replica Not FoundException

Re: Cannot select * from tables in hive

Re: Cannot select * from tables in hive

Re: Cannot select * from tables in hive

Re: Cannot select * from tables in hive

Re: Cannot select * from tables in hive

Re: Cannot select * from tables in hive

Re: Kerberos change password is not working (from ...

Re: Eable Kerberos via Cloudera Manager wizard fai...

Kerberos change password is not working (from kadm...

Re: kinit: Cannot contact any KDC for realm ‘CLOUD...