@Saifullah Sajjad If cluster is managed by Ambari HDP.repo file is created by ambari agent during the HDP installation. This HDP.repo file need not to be created manually, even if created manually, this will be overwritten by Ambari. HDP.repo file is created as per your inputs provided during stack setup setup in Launch Install cluster wizard. ... View more

@bigdata.neophyte -t option seems to not available in 2.7.1 version which is included with HDP 2.4.2. This option is included in hadoop 2.7.3 which is available with HDP 2.5 Tech preview . [hdfs@hdp1 ~]$ hadoop version Hadoop 2.7.3.2.5.0.0-1133 Subversion git@github.com:hortonworks/hadoop.git -r 93bf28063ef319be6833d3d6f117d44e0b6b8fa9 Compiled by jenkins on 2016-08-03T11:38Z Compiled with protoc 2.5.0 From source with checksum 1aed9e48ca6f7cd4ada3a36b1cd5feb This command was run using /usr/hdp/2.5.0.0-1133/hadoop/hadoop-common-2.7.3.2.5.0.0-1133.jar [hdfs@hdp1 ~]$ hdfs dfs -ls -t -help -ls: Illegal option -help Usage: hadoop fs [generic options] -ls [-C] [-d] [-h] [-q] [-R] [-t] [-S] [-r] [-u] [<path> ...] [hdfs@hdp1 ~]$ hdp-select versions 2.5.0.0-1133 ... View more

@Eberhard Wagner Can you please accept the answer if it helped you to resolve the problem Thanks ... View more

@Davd Leh Host-only network will only allow network connectivity with host where sandbox is running. As accessing wikipedia needs internet access you have to use either NAT or Bridged type network on VMware guest. Once set to NAT/Bridged verify if you are able to ping en.wikipedia.org and then try wget. By default SandBox will have NAT network type for its adapter. ... View more

You would need to restart the services after adding the property to hdfs-site ... View more

@Rajib Mandal It looks that the port 50070 is listening on loopback IP , netstat -ntlup command shows that. Please make sure you have "dfs.namenode.http-address" property in hdfs-site.xml set to the <HostIPAddress>:50070 This can be set from Ambar Dashboard>Services>HDFS>Configs>Advanced>Advanced hdfs-site Look for property dfs.namenode.http-address and set it to <HostIPAddress>:50070 Restart the hdfs for this to take effect. It should look something like below [root@hdp1 ~]# netstat -an | grep 50070 tcp 0 0 192.168.56.10:50070 0.0.0.0:* LISTEN <<<<< tcp 0 0 192.168.56.10:50070 192.168.56.1:51147 ESTABLISHED tcp 0 0 192.168.56.10:50070 192.168.56.1:51144 ESTABLISHED Instead of this (which is in your case now) [root@hdp1 ~]# netstat -an | grep 50070 tcp 0 0 127.0.0.1:50070 0.0.0.0:* LISTEN tcp 1 0 ::ffff:192.168.56.10:55036 ::ffff:192.168.56.10:50070 CLOSE_WAIT tcp 1 0 ::ffff:192.168.56.10:55094 ::ffff:192.168.56.10:50070 CLOSE_WAIT ... View more

@Rajib Mandal Connection refused usually mean either service is not running or firewall is blocking the port. If namenode process is running on hdfs namenode host, please verify that you have correct firewall rules to allow required port. You can try to disable iptables and selinux on the hosts. #service iptables stop ... View more

@Rajib Mandal port 50070 is namenode UI port and 8088 is RM UI which should be accessible if namenode and yarn services are up. Please check if you can connect to port using telnet from ambari server #telnet <hostnameInError> 50070 Also on server where namenode is running verify if the port is in listen state, if it is not then namenode service has some problem(you can check the namenode logs to see if the the service exited for any reason). #netstat -ntalp | grep 50070 ... View more