@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

@ThanhP  Good to know that the issue is resolved.   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

@ThanhP The following error indicates that Ambari is not able to connect to the MySQL DB instance. Caused by: com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. Most possible cause might be either there is some network issue of your MySQL might not be running properly (running with errors). We might need to review Mysql side log as well.   Checks from AmbariServer Host side So can you please check if you have entered correct DB url in ambari.properties? Can you please share the following output? # grep 'jdbc' /etc/ambari-server/conf/ambari.properties In the output of the above command we shoudl be able to see the MySQL DB details like user/URl/driver ..etc Can you please try running the following simple JDBC connectivity check from Ambari DB host to the MySQL instance? # /usr/jdk64/jdk1.8.0_112/bin/java -cp /var/lib/ambari-server/resources/DBConnectionVerification.jar:/usr/share/java/mysql-connector-java.jar org.apache.ambari.server.DBConnectionVerification "jdbc:mysql://xxxxxxxxx/ambari" "ambariDBUser" "ambariDBPassword" com.mysql.jdbc.Driver You will need to change the 'ambariDBUser'/ 'ambariDBPassword' and DB url based on the ambari.properties entries. Also from the ambari server host can you please check if the MySQL host&port is accessible without any issue? This is to isolate if the MySQL host & port is accessible from Ambari server host? # telnet $MYSQL_HOSTNAME 3306 (OR) # nc -v $MYSQL_HOSTNAME 3306   Checks from MySQL DB side Please try to restart MySQL DB once. Check if the MySQL is listening to the correct port ? (default port is 3306) # ps -ef | grep mysql # netstat -tnlpa | grep 3306 # netstat -tnlpa | grep `cat /var/run/mysqld/mysqld.pid` For any errors on Mysql side we can check the MySQL log like '# less /var/log/mysqld.log' ... 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

@Manoj690    We see the failure is because of the following cause:     ERROR tool.ImportTool: Import failed: org.apache.hadoop.mapred.FileAlreadyExistsException: Output directory hdfs://gaian-lap386.com:8020/user/gaian/emp already exists   You already have the output directory in HDFS "hdfs://gaian-lap386.com:8020/user/gaian/emp" existing hence it is failing.   You can easily check it as   # su - hdfs -c "hdfs dfs -ls /user/gaian/emp"     So either specify a different table / target dir OR specify the following property in your SQOOP command. "--delete-target-dir Delete the import target directory if it exists" Please refer to the mentioned doc to know what it actually does and if it is feasible for you or not? OR you can try defining a different "--target-dir" (to define another HDFS destination dir) in the command line. https://sqoop.apache.org/docs/1.4.4/SqoopUserGuide.html ... View more

@sonalidive786    Following doc talks about installing and setting up Ranger via Ambari. https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.0/installing-ranger/content/installing_ranger_using_ambari.html   Once the setup is done then you can enable ranger plugins for various services as mentioned in : https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.0/installing-ranger/content/ranger_install_ranger_plugin_settings.html   You can also refer to Hortonworks Youtube Channel: Comprehensive Hadoop Security with Apache Ranger and Apache Knox (it is for HDP 2.2 however it will give a good QuickStart) https://www.youtube.com/watch?v=2Ya4jSLvX-o ... View more

@Manoj690  I think for Ambari Server issue you have already raised a separate topic:  https://community.cloudera.com/t5/Support-Questions/ambari-server-issue-its-not-running/m-p/269593#M206953   The current thread is for Sqoop command failure. ... View more

@Manoj690  Is this issue resolved ?  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

@yvettew  One thing is for sure here is that Ambari is not giving 502 bad gateway error here. Ambari server runs on Jetty Server (Not on nginx)  So definitely the error which you are getting in your browser is not coming from ambari server.     It mist be coming from some nginx server as we see 502 Bad Gateway nginx/1.15.7 . Whatever output was generated from the curl command can you share that same.  Even if it is blank output can you please share the screenshot of the error or the browser debugger console output ? # curl -iLv -u admin:admin -H "X-Requested-By: ambari" -X GET http://$AMBARI_HOSTNAME:8080/api/v1/check     . ... View more