@Kunal Kumar As we see the message as following in your "ambari-server.log" Host: hdpnode1.hortonworks.com Can not be determined . Which means your ambari server hosts "/etc/hosts" file does not have mapping for the "hdpnode1.hortonworks.com" Also as we see that you are using Sandbox which is suitable for a Single Node cluster only (as it runs inside a docker container hence all the ports of it are not exposed externally) Hence please make sure that from ambari agent host you can access ambari server host and port 8440 / 8080 Also the "/etc/hosts" file on ambari server host contains the IP and host mapping for "hdpnode1.hortonworks.com" ... View more

@Kunal Kumar The problem seems to be the incorrect "SSH Private Key". Based on screenshot "screenshot-from-2018-12-28-18-23-15.png" looks like you are pasting the "Public" key content there instead of "Private Key" of the host "hdpnode1.hortonworks.com" For example the following will be the Private Key: "~/.ssh/id_rsa" adn the content of private key file looks something like following which BEGIN and END marks: Example: -----BEGIN RSA PRIVATE KEY----- ANCDEFGHIJKLMNOPoCUhgGazht5XrPbvkcD ....... QRSTUVWXYZasdoeruoijlcsd,fns,cjsdklfjo= -----END RSA PRIVATE KEY----- Usually Public key file name is "~/.ssh/id_rsa.pub" Also the Ambari API call is showing 404 because you will need to replace the "$name" with your clustername. You can get your ambari cluster name using the following API call. http://192.168.1.190:8080/api/v1/clusters . ... View more

@Kunal Kumar Ownership of the "~/.ssh" directory and the keys files should be something like following: # ls -l ~/.ssh/ total 20 -rw-------. 1 root root 818 Sep 12 08:03 authorized_keys -rw-------. 1 root root 1679 May 22 2018 id_rsa -rw-------. 1 root root 406 May 22 2018 id_rsa.pub -rw-r--r--. 1 root root 1174 Sep 12 08:36 known_hosts [root@newhwx1 ~]# [root@newhwx1 ~]# [root@newhwx1 ~]# ls -ld ~/.ssh/ drwx------. 2 root root 91 Sep 12 08:42 /root/.ssh/ . Please check if you are able to do passwordless SSH to the mentioned host properly or not without suppliying the password (except for the first time) You can also use the "ssh-copy-id" command to make sure that your correct public key is setup # ssh-copy-id -i ~/.ssh/id_rsa.pub root@hdpnode1.hortonworks.com . Then try using the passwordless SSH to see if it works? # ssh root@hdpnode1.hortonworks.com . Regarding your query: how to replace " $name" with my clustername. The API calls the cluster name in your case is "Sandbox" so the correct Hosts call will be as following to list the hosts added to the cluster (Sandbox) http://192.168.1.190:8080/api/v1/clusters/Sandbox/hosts . Also pelase verify if you have the FQDN setup correctly for your Ambari Server host as well as for the host which you are adding recently to the cluster: # hostname -f # cat /etc/hosts . If you still face any issue while doing host registration then please share the "Operation log" (the Complete error which you see in the ambari UI for failure) ... View more

@Divya Thaore Looks like you are running Oracle 10g database on your localhost. Oracle 10g DB also uses port 8080 as default port. Please stop Oracle Database and then you should be able to access Ambari port 8080 if needed please restart your Sandbox after stopping Oracle Database on your laptop. ... View more

@Leonardo Araujo The Sandbox is a docker container runs inside the VM. So if you want to login to login to the VM where the Docker container is started then you will need to use the SSH Port 2122 But if you want to actually login to the Sandbox Docker container where the HDP components/services are present then you will need to do SSH on port 2222 . You will find the Sandbox Port mapping info here: https://hortonworks.com/tutorial/hortonworks-sandbox-guide/section/3/ Sandbox Architecture: https://hortonworks.com/tutorial/sandbox-architecture/ ... View more

@Harish More Can you please check if you have set the "ranger.usersync.unix.backend=nss" property inside the "ranger-ugsync-site.xml" file after setting up the SSSD? Please refer to the following article to get more details about this property followed by a usersync restart. https://community.hortonworks.com/content/supportkb/222504/unable-to-sync-ranger-user-from-local-unix-nss.html ... View more