@Alex Raj Check to see if the following helps. ... View more

@Rich Raposa Thank again for looking into this! ... View more

@drussell Sure, thank you for looking into this! ... View more

@Sridhar Bandaru It would be a good idea to create a backup of the Ambari database before proceeding. http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_reference_guide/content/_back_up_current_data.html Please check the response you are getting when you run the below command. # curl -u admin:admin -i -H 'X-Requested-By: ambari' -X GET http://sandbox.hortonworks.com:8080/api/v1/clusters/Sandbox/services/FALCON ... View more

@saurabh saurabh When you click on ResourceManager UI, navigate to specific application's link. On the application page, you should see links to all your individual application attempts. If you review the logs for individual task attempts, you should see it displays the log of both the standard output as well as the standard error. ... View more

@Abiel Flrs Check the OS level user/group mapping as well. # id hue # grep hue /etc/passwd # grep hue /etc/group ... View more

@Amit Sharma 1. Confirm from Ambari that the DataNode process is down. 2. Ensure there are no stale DataNode processes running. # ps -ef | grep datanode | grep -v grep 3. Check that no other program/service is listening on port 50010. # netstat -anp | grep '0.0.0.0:50010' 4. Check that there are no leftover PIDs remaining. Remove the PID file if it exists. # cat /var/run/hadoop/hdfs/hadoop-hdfs-datanode.pid 5. While starting the DataNode from Ambari, tail the log file to review startup messages and related errors/warnings. # tailf /var/log/hadoop/hdfs/hadoop-hdfs-datanode-[hostname].log ... View more