@Amit Kumar Please accept the answer, if this resolved your issue. ... View more

@Ganesh Raju With newer versions of maven you can disable the certificate validation of the maven http wagon temporarily to confirm if the certificate is indeed the source of the problem. -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true . As per Ambari Build Note the maven version should be "Apache Maven 3.0.5" Please see: https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development ... View more

@Rafael Menezes If the issue described in the original thread is resolved then please mark the answer as accepted. ... View more

@Amit Kumar It will be more of troubleshooting docker based n/w config. We may need to look from the docker side much... compared to ambari/hive side. ... View more

@Amit Kumar Not sure if there is anything special in the above mentioned docker instance. However if you would like to see Ambari's Docker instance / instructions then you might want to look at: https://cwiki.apache.org/confluence/display/AMBARI/Development+in+Docker https://github.com/apache/ambari/tree/trunk/dev-support/docker And https://github.com/sequenceiq/docker-ambari The above Github repo has more contributors and more Commits. This worked for me many times. ... View more

@Amit Kumar It is good that we have isolated the issue that the hosts are not able to even ping each other means the Host name is not resolvable. That's why you are getting the following error even after addign the /etc/hosts entries. [root@8c043e0d490c /]# ping 16aadcc9c315 ping: unknown host 16aadcc9c315 - So it looks like more of a Docker N/W config issue. - Can you please share more details about how did you configure your docker N/W Settings? ... View more

@Amit Kumar Have you already added the follwing 3 lines of entries in *every hosts* "/etc/hosts" file? And then tried Pinging? 172.20.0.2 8c043e0d490c 172.20.0.3 16aadcc9c315 172.20.0.4 b1ec39e6d58b . ... View more

@Amit Kumar Do you have the following entries mentioned in all your "/etc/hosts" file 172.20.0.2 8c043e0d490c 172.20.0.3 16aadcc9c315 172.20.0.4 b1ec39e6d58b . After the first two lines of the /etc/hosts file every node of your cluster should have the IP host name mapping. So that they can ping each other using the mentioned hostname. Means each host should be able to access each other with the mentioned hostnames. . ... View more

@Amit Kumar Have you configured the FQDN properly for all your hosts and are they able to access each other using the FQDN? Following command should show the hostname it should use. hostname -f Please see the following link to know why correct FQDN configuration is needed for communication and how to edit the " /etc/hosts" http://docs.hortonworks.com/HDPDocuments/Ambari-2.2.2.0/bk_Installing_HDP_AMB/content/_check_dns.html . ... View more

@jean rivera Additionally please check if the "/usr/hdp/current/oozie-server/libtools/oozie-tools-x.x.x.x.x.x.jar" JAR exist or not on the host where you added the component? Example: "/usr/hdp/current/oozie-server/libtools/oozie-tools-4.2.0.2.5.3.0-37.jar" This jar contains the class " org.apache.oozie.tools.OozieDBCLI". ... View more