@Vij    Can you share your share your zookeeper_client_jaas.conf and zookeeper_jaas.conf they should be look like below zookeeper_client_jaas.conf Client { com.sun.security.auth.module.Krb5LoginModule required useKeyTab=false useTicketCache=true; }; zookeeper_jaas.conf Server { com.sun.security.auth.module.Krb5LoginModule required useKeyTab=true storeKey=true useTicketCache=false keyTab="/etc/security/keytabs/zk.service.keytab" principal="zookeeper/<host>@[REALM]"; };   Please compare and let me know    ... View more

@saivenkatg55    I can see your name node is in safe mode can you do the following As root # su - hdfs # Check  to validate what I saw in the log $ hdfs dfs -safemode get # Resolve the lock out $ hdfs dfs -safemode leave # Validate safe mode is off $ hdfs dfs -safemode get That should resolve the issue! Then also send me Share /var/log/kadmind.log and /var/log/kadmind.log ... View more

@saivenkatg55  Share /var/log/kadmind.log and /var/log/kadmind.log .. you can use Big file Transfer ... View more

@saivenkatg55  What do you mean by local (MIT) if I guess right you are accessing the HDP cluster from a client laptop or edge node where you installed the Kerberos client libraries. To communicate with secure Hadoop clusters that use Kerberos authentication, known as Kerberized clusters, a client uses the Kerberos client utilities. You MUST install these utilities on the same system where you are connecting from. For Linux desktops here are the different options Ubunt: # apt install krb5-user RHEL/Centos: # yum install -y krb5-server krb5-libs krb5-workstation These packages deliver the krb5.conf that the client should configure to connect to a kerberized cluster, the easier and recommended way is to copy the krb5.conf from the kdc server to all clients that need to connect to the Kerberized cluster in RHEL/CentOS it's located in /etc/krb5.conf. This file has the pointer to the REALM, KDC and ADMIN server Here is an example [logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log [libdefaults] default_realm = REDHAT.COM dns_lookup_realm = false dns_lookup_kdc = false ticket_lifetime = 24h renew_lifetime = 7d forwardable = true [realms] REDHAT.COM = { kdc = KDC.REDHAT.COM admin_server = KDC.REDHAT.COM } [domain_realm] .redhat.com = REDHAT.COM redhat.com = REDHAT.COM Else share /var/log/kadmind.log and /var/log/kadmind.log   HTH ... View more

@irfangk1    That means you didn't install MySQL. Can I ask you one question? What documentation are you using as a reference?The basic steps are described when you are preparing the environment. To me it seems you launched the deployment using the embedded database Postgresql but now you want to switch to MySQL. To do that you need to install mysql and pre-create the ambari database before launching the Ambari server setup, that explains why you are getting all those errors. I can send you a procedure in 9 hours ... View more

@irfangk1  Can you share the screenshot of your Ambari Hive config  because when I see "jdbc:mysql://host.com/metastore" "hive"   that means you dont have  not The default  TCP port  for PostgreSQL is usually 5432 see in the postgresql.conf ... View more

@irfangk1  If you switched to Mysql why do you have these entries in your ambari.properties   server.jdbc.database=postgres server.jdbc.database_name=ambari server.jdbc.postgres.schema=ambari   Can you share the output of  # cat /etc/ambari-server/conf/ambari.properties | grep mysql Why is that in the log again I see  "jdbc:mysql://host.com/metastore" "hive"  where is the PORT  number?   ... View more

@irfangk1    This line in your error log says it all org.apache.ambari.server.DBConnectionVerification "jdbc:mysql://host.com/metastore" "hive" The format should be jdbc:mysql://host-name: port usually for Mysql it's 3306 to initiate any database connectivity you need to know the port at which the database is waiting for connections   Ambari.properties # cat /etc/ambari-server/conf/ambari.properties | grep mysql custom.mysql.jdbc.name=mysql-connector-java.jar previous.custom.mysql.jdbc.name=mysql-connector-java.jar server.jdbc.database=mysql server.jdbc.driver=com.mysql.jdbc.Driver server.jdbc.rca.driver=com.mysql.jdbc.Driver server.jdbc.rca.url=jdbc:mysql://your_host:3306/ambari server.jdbc.url=jdbc:mysql://your_host:3306/ambari Backup these files  Verification jar # mv /var/lib/ambari-agent/cache/DBConnectionVerification.jar /var/lib/ambari-agent/cache/DBConnectionVerification.jar.bck MySql connector  # mv /var/lib/ambari-agent/cache/mysql-connector-java.jar  /var/lib/ambari-agent/cache/mysql-connector-java.jar.bck Then restart Ambari and the agent    ... View more

@vsrikanth9    Great, it worked but you should recognize even if you had modified the    /var/kerberos/krb5kdc/kadm5.acl still  krb5.conf was wrong and your Ambari UI  was wrong so you still wouldn't have resolved it 🙂  Happy hadooping  ... View more