@irfangk1  You have not responded with the command output that we requested. So it is hard to guess what might be wrong. We see the errors as following:   org.postgresql.util.PSQLException: Connection to inairsr542007v3.ntil.com:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.     Possible Cause: 1. Either your Postgres DB is not running. 2. Postgres DB hostname Or Port is not correctly specified. 3. Postgres Ports are not accessible remotely.   So in order to isolate the issue and find out what might be causing the Postgres connection failure we will need the following informations.   I will repost my comment which needs to be looks up first. Please check the telnet / netstat commands which i shared in my previous update to findout if your Postgres DB is actually running fine or not and if that is accessible from the HiveMetastore/ HS2 instances or not?       ON Postgresd DB Host (Port Bind and listening Check / Firewall check) ---------------------------- # netstat -tnlpa | grep 5432 # netstat -tnlpa | grep $POSTGRES_PID # systemctl status firewalld # systemctl stop firewalld (OR) # service iptables stop ON HiveMetastore/HS2 host (Connection check) ---------------------------- # telnet $POSTGRES_DB_HOSTNAME 5432 # nv -v $POSTGRES_DB_HOSTNAME 5432       .   Also it will be best to see your PostgresDB logs if the issue persist. ... View more

@irfangk1   As we see : Connection to inairsr542007v3.xxxxxxx.com:5432 refused. So please check the telnet / netstat commands which i shared in my previous update to findout if your Postgres DB is actually running fine or not and if that is accessible from the HiveMetastore/ HS2 instances or not? ON Postgresd DB Host (Port Bind and listening Check / Firewall check) ---------------------------- # netstat -tnlpa | grep 5432 # netstat -tnlpa | grep $POSTGRES_PID # systemctl status firewalld # systemctl stop firewalld (OR) # service iptables stop ON HiveMetastore/HS2 host (Connection check) ---------------------------- # telnet $POSTGRES_DB_HOSTNAME 5432 # nv -v $POSTGRES_DB_HOSTNAME 5432 .   ... View more

@hassaniraj  Looks like the error reported in this thread could be due to the same reason mentioned on another thread of yours: https://community.cloudera.com/t5/Support-Questions/Hortonworks-sandbox-2-5-yum-update-not-working/m-p/278491 . It will be great to follow the same instructions mentioned on that thread to see if that fixes this issue. Specially   if you see some "dev2.hortonworks.com.s3.amazonaws.com" repos base URLs inside your "/etc/yum.repos.d" repos then please refer to the other thread and try to disable them and try again. You should set the  "enabled=0"   (this will disable the sandbox.repo) which has issue. As that is just development repo and might not be available always. https://community.cloudera.com/t5/Support-Questions/yum-install-error-please-help-me-out/m-p/203121 After removing the problematic repos try to perform a clean at yum level and then try again: # yum clean all # yum install python-pip . ... View more

@hassaniraj  1. Please try restarting the VM once. 2. Inside the sandbox do SSH login and then try to see if you are able to make the following curl call .. this is just to verify the repo accessibility. If the following URL does not work then please share the HTTP Header section output of the following curl commands here so that we can verify if there are some special headers like Network proxy ..etc. # curl -iLvk <a href="http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6/repodata/repomd.xml" target="_blank">http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6/repodata/repomd.xml</a> AND   # curl -iLvk <a href="http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6/repodata/7fcacadb44b1a860fb704795c187f549103e855a0a93ed31293a0b270a9022b4-primary.sqlite.bz2" target="_blank">http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6/repodata/7fcacadb44b1a860fb704795c187f549103e855a0a93ed31293a0b270a9022b4-primary.sqlite.bz2</a>   3. If above works fine then we will have to look from the YUM side. Please try to perform the yum cache cleanup and then retry:   # yum clean all # yum update   4. It will be also good to verify if the "/etc/yum.repos.d/" directory has any problematic repo. Can you please list them?   # ls -lart /etc/yum.repos.d/   For temporarily you can move some of the repo files from "/etc/yum.repos.d/" file to outside and then retry... this will help in isolating if there are any corrupted repo issue. 5. Recently have you made any changes to the "/etc/yum.conf" file like enabling/disabling any proxy setting ..? # cat /etc/yum.conf   Also if you see some "dev2.hortonworks.com.s3.amazonaws.com" repos URLs inside your "/etc/yum.repos.d" repos then please refer to the other thread and try to disable them and try again: https://community.cloudera.com/t5/Support-Questions/yum-install-error-please-help-me-out/m-p/203121 Example:   # cat /etc/yum.repos.d/sandbox.repo [sandbox] baseurl=<a href="http://dev2.hortonworks.com.s3.amazonaws.com/repo/dev/master/utils/" target="_blank">http://dev2.hortonworks.com.s3.amazonaws.com/repo/dev/master/utils/</a> name=Sandbox repository (tutorials) gpgcheck=0 enabled=0       . . If your question is answered then, Please make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@vsrikanth9  Looks like you are using MySQL as Non Default Database for your AmbariServer. So i am sure that you might have already performed the steps mentioned in the doc: https://docs.cloudera.com/HDPDocuments/Ambari-2.6.2.2/bk_ambari-administration/content/using_ambari_with_mysql.html It will be good to verify few things: ### Checks from MySQL host side: ### 1. On the MySQL Database host please verify if the MySQL Database is running fine and the port "3306" is listening? # netstat -tnlpa | grep 3306 NOTE: please take a look at your MySQL DB configs "/etc/my.cnf" to be double sure that it is configured to listen to 3306 port (default port) or configured to listen to some all interfaces and if it is using any other port? You can find the ports your mysql is listening to by passing the MySQL DB PID to the following command: # netstat -tnlpa | grep $MYSQL_PID 2. On the MySQL Database host please verify if the "firewall" /"iptables" is disabled so that from the Hive Metastore host the Postgres Post can be accessed. # systemctl status firewalld (OR) # service iptables status If iptables/firewalld is enabled then please make sure to allow MySQL DB port access from remote hosts (OR) disable it. ### Checks from AmbariServer host side: ### 3. From AmbariServer host please get the configured DB details (to verify if you are using correct MySQL host & port inside ambari.properties) ? # grep 'jdbc' /etc/ambari-server/conf/ambari.properties 4. Once the host & port of DB is verified to be correctly configured as above then please try to connect to MySQL host & port using telnet / netcat utilities. This will help us in isolating any Network / Port / Hostname issues. To verify whether the MySQL DB host & port to verify if at the network level the port is accessible ? # telnet $MYSQL_DB_HOSTNAME 3306 (OR) # nv -v $MySQL_DB_HOSTNAME 3306 5. From Ambari Server host please verify if you are using correct "mysql-connector-java.jar" driver JAR of correct version? (based on your MySQL version). 6. Please try to use the same connector JAR to establish the connection to MySQL DB from ambari server host using the following DB Connection checker utility to see if the db connection can be established. # /usr/jdk64/jdk1.8.0_112/bin/java -cp /usr/lib/ambari-server/resources/DBConnectionVerification.jar:/usr/share/java/mysql-connector-java.jar org.apache.ambari.server.DBConnectionVerification "jdbc:mysql://XXXXXXXXXXX/ambari" "ambari" "bigdata" com.mysql.jdbc.Driver Please change the MySQL DB URL / username and password based on your "ambari.properties" DB connection settings.   If Still we see Failure: If everything is fine still you are getting the error establishing connection to MySQL from AmbariServer. then please share the output of the above command along with the following details: 1. /var/log/ambari-server/ambari-server.log ----> We would like to see Full error from starting including the StackTrace. 2. Please try to restart MySQL Database once and notice if you see any error in MySQL DB logs?    Please also share the DB log and "/etc/my.cnf" . . If above update helps in finding the answer to your issue then, Please make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@irfangk1  Looks like you are using Postgres as Non Default Database for your Hive. It will be good to verify few things:   1. If you have setup your Postgres Database for Hive as mentioned in the doc: https://docs.cloudera.com/HDPDocuments/Ambari-2.7.3.0/administering-ambari/content/amb_using_hive_with_postgresql.html   2. On the Postgres Database host please verify if the Postgres Database is running fine and the port  " 5432" is listening?     # netstat -tnlpa | grep 5432       NOTE: please take a look at your postgres Db configs to be double sure that it is configured to listen to 5432 port.  You can find the ports your postgres is listening to by passing the Postgres PID to the following command:     # netstat -tnlpa | grep $POSTGRES_PID     3. On the Postgres Database host please verify if the "firewall" /"iptables" is disabled  so that from the Hive Metastore host the Postgres Post can be accessed.   4. From HiveMetastore host please try to telnet / netcat the Postgres DB host & port to verify if at the network level the port is accessible ?     # telnet $POSTGRES_DB_HOSTNAME 5432 (OR) # nv -v $POSTGRES_DB_HOSTNAME 5432      .   5. Regarding the "/hiveserver2" Zookeeper znode.... it will be available only when your HiveServer2 starts successfully without any issue.   So please verify the Hive Metastore and hive server2 logs first once they are running fine then you should see the Znode without any issue.   If you still face any issue then please share the above requested informations along with the Postgres Server log and the Hive Logs. If your question is answered then, Please make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@rajesh1972  The maven artifact : "hbase-common:1.1.2" which provides the following JAR does. not seems to contain that class "org.apache.hadoop.hbase.types.CopyOnWriteArrayMap" ... you can check this JAR .. https://repo1.maven.org/maven2/org/apache/hbase/hbase-common/1.1.2/hbase-common-1.1.2.jar   So can you please try changing the version of the artifact to 2.0.0 . (instead of 1.1.2) and then see if that works for you? Example:   <dependencies> <dependency> <groupId>org.apache.hbase</groupId> <artifactId>hbase-client</artifactId> <version>2.0.0</version> </dependency> <dependency> <groupId>org.apache.hbase</groupId> <artifactId>hbase-common</artifactId> <version>2.0.0</version> </dependency> </dependencies>   .   If your question is answered then, Please make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.     . ... View more

@rajesh1972  Can you please share your  "pom.xml" file so that we can check the dependencies which you are including here?   Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.hbase.types.CopyOnWriteArrayMap   The problematic/missing class "org.apache.hadoop.hbase.types.CopyOnWriteArrayMap" is part of " hbase-common.jar" JAR so please make sure that your "pom.xml" file contains the dependency to that maven artifact as well.  The "hbase-server" artifact provides the dependency to hbase-common jar. Example:   <dependencies> <dependency> <groupId>org.apache.hbase</groupId> <artifactId>hbase-server</artifactId> <version>${hbase.version}</version> </dependency> <dependency> <groupId>org.apache.hbase</groupId> <artifactId>hbase-client</artifactId> <version>${hbase.version}</version> </dependency> <dependency> <groupId>org.apache.hadoop</groupId> <artifactId>hadoop-client</artifactId> <version>${hadoop.version}</version> </dependency> <dependency> <groupId>org.apache.hadoop</groupId> <artifactId>hadoop-common</artifactId> <version>${hadoop.version}</version> </dependency> </dependencies>     Please Notice:     <dependency> <groupId>org.apache.hbase</groupId> <artifactId>hbase-server</artifactId> <version>${hbase.version}</version> </dependency> (OR) <dependency> <groupId>org.apache.hbase</groupId> <artifactId>hbase-common</artifactId> <version>${hbase.version}</version> </dependency>       You can refer to a working pom.xml in my Github repo: https://github.com/jaysensharma/MiddlewareMagicDemos/tree/master/HDP_Ambari/HBase/HBase_Client   hbase-server maven artifact provides the dependency to hbase-common so please include the dependency    # mvn dependency:tree | grep -B3 hbase-common [INFO] +- org.apache.hbase:hbase-server:jar:1.1.2.2.5.3.0-37:compile [INFO] | +- org.apache.hbase:hbase-common:jar:1.1.2.2.5.3.0-37:compile     .   .       ... View more

@TJP  When your developer mentioned that " he was not able run hive query on beeline.,"   then did he receive any error? Can you please share the complete error stacktrace ?    ... View more

@TechAven  Looks like you just updated your post with the error . . We see the Error   Failed to run the Ambari Server org.apache.ambari.server.AmbariException: Current database store version is not compatible with current server version, serverVersion=2.7.0.0, schemaVersion=2.4.3 at     This indicates that you are running Ambari Binary 2.7.0.0 version But your Ambari DB schema is 2.4.3   You might not have performed the following command after upgrading your Ambari Binaries.   # ambari-server upgrade     Please check the following link . Step 14. " Upgrade Ambari Server database schema"    if you have missed to do that: https://docs.cloudera.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-upgrade/content/upgrade_ambari.html . Can you please confirm if you have installed the Ambari Server binaries recently?  What is the output of the following command.     # rpm -qa | grep ambari       ... View more

@TechAven  If you can share the Full logs then we can help you better. /var/log/ambari-server/ambari-server.out /var/log/ambari-server/ambari-server.log So far whatever you have shared in this thread is just the outcome of the failure.  If we want to find out the Cause of that failure then you should share the detailed Error/StackTrace ... that you will find in the above mentioned files. So better if you can attach those files here. ... View more

@Srm    As we see that the telnet from amabri server host to DB host/port is failing to connect. Also we see that the DB host does not show any port 5432 in LISTENING state.  So it indicates that your PostgresDB is not listening on 5432 port or it might not be running successfully.   So one thing is confirmed that it is not an issue from Ambari Side.   Form Postgres side please check and share the Postgres Logs and Postgres Configs and the output of the following command so that we can see why it is not listening to 54323 port.  Or if it is listening to some other port Or if it is failing to start successfully.   ... View more

@Srm  Can you please share the output of the following commands : From Ambari Server host can you please try running the DB connection checker utility to verify if we see the same error? Example:   # /usr/jdk64/jdk1.8.0_112/bin/java -cp /var/lib/ambari-server/resources/DBConnectionVerification.jar:/usr/lib/ambari-server/postgresql-42.2.2.jar org.apache.ambari.server.DBConnectionVerification jdbc:postgresql://user-172.16.1.30:5432/ambari ambari bigdata org.postgresql.Driver Connected to DB Successfully!   Please change the DB password and user name based on your setup. Like in above case following are the values which might be different in your case. Also according to your ambari version the postgres driver jar name might be slightly different. "/usr/lib/ambari-server/postgresql-42.2.2.jar"   DB URL: jdbc:postgresql://user-172.16.1.30:5432/ambari DB USername: ambari DB Password: bigdata   (OR) If you have postgressql client installed on AmbariServer host then try to connect to the DB using it to verify the connectivity.   # psql -h user-172.16.1.30 -p 5432 -U <username> -W <password> <database>   If you do not get the "Connected to DB Successfully!" message which means there is some possibilities like following:   Checks From Ambari Server Host side   Checks-1). The JDBC Url might be in incorrect format. So please verify the JDBC settings defined inside the "ambari.properties". Please share the output of the following:   # grep 'jdbc' /etc/ambari-server/conf/ambari.properties Example: server.jdbc.connection-pool=internal server.jdbc.database=postgres server.jdbc.database_name=ambari server.jdbc.driver=org.postgresql.Driver server.jdbc.hostname=user-172.16.1.30 server.jdbc.port=5432 server.jdbc.postgres.schema=ambari server.jdbc.rca.driver=org.postgresql.Driver server.jdbc.rca.url=jdbc:postgresql://user-172.16.1.30:5432/ambari server.jdbc.rca.user.name=ambari server.jdbc.rca.user.passwd=/etc/ambari-server/conf/password.dat server.jdbc.url=jdbc:postgresql://user-172.16.1.30:5432/ambari server.jdbc.user.name=ambari server.jdbc.user.passwd=/etc/ambari-server/conf/password.dat     Checks-2). If the entries are correct inside the ambari.properties then may be the DB host/port is not accessible. So can you please try running the following commands from ambari server host to see if the connection to DB is allowed or not?   # telnet user-172.16.1.30 5432 (OR) # nc -v user-172.16.1.30 5432   If the above is not connecting to the DB on mentioned host & port then first of all please check if the DB hostname / IP mapping is correct? To verify if "user-172.16.1.30" is actually the DB hostname or not and if it is mapped to the correct IP Address ?   On ambari server host please check if the "/etc/hosts" file has correct entry to the mentioned DB host?   # cat /etc/hosts | grep user     Checks From DB side Checks-3). Please match the "/etc/hosts" file entry to verify if the IP / Hostname mapping is correct? # cat /etc/hosts | grep user # hostname -f Checks-4). Please verify if the IPTables/ Firewalld is disabled on the DB? Please check the status of firewalld / iptables if they are stopped?   # systemctl status firewalld (OR) # service iptables status   Checks-5). Verify if the Port 5432 is listening to all the listen addresses or on a specifific Interface/address? Example:   # netstat -tnlpa | grep 5432 tcp 0 0 0.0.0.0:5432 0.0.0.0:* LISTEN 10290/postgres tcp6 0 0 :::5432 :::* LISTEN 10290/postgres   Checks-6). Please try restarting your PostgresDB once ... If you still face the same Error "PSQLException: Connection to user-172.16.1.30:5432 refused." then please share the postgres config / logs. . . ... View more

@shyamshaw  How to see your Current Grafana Version? When you login to your Grafana UI and click on the "Sign In" button then in the Page "http://$GRAFANA_HOST:3000/login" You should see the Grafana Version that you are using.   For example with Ambari 2.7.3 (or Ambari 2.6.2 ..etc) repo you should get the "Grafana version: 2.6.0" . But the feature which you are looking out "For monitor NFS" https://grafana.com/grafana/dashboards/6257 Has a Dependency listed as "Grafana 4.2.0" you can check the right panel "Dependencies" section on the same link. So you are expecting a More advanced feature from Older version Grafana. . If your question is answered then, Please make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more