Created 09-21-2017 07:37 AM
I have installed HDP Sandbox 2.6 on oracle Virtual-box.When I am opening Pig View in ambari webhcat and userhome directory test are failed. So i am unable to work on pig scripts.can anybody help?
Created 09-21-2017 07:43 AM
If you are logging in to the sanobox and trying to access PigView with a user named as 'admin' then you should create a directory in HDFS as a prerequisite for that user as following:
[root@sandbox ~]# su - hdfs [hdfs@sandbox ~]$ hdfs dfs -mkdir /user/admin [hdfs@sandbox ~]$ hdfs dfs -chown admin:hadoop /user/admin
Else you will see following kind of error: https://docs.hortonworks.com/HDPDocuments/Ambari-188.8.131.52/bk_ambari-views/content/setup_HDFS_user_dir...
Service 'userhome' check failed: File does not exist: /user/admin
If you are logging in to the Ambari UI using some other user like "testuser" then you will need to create the HDFS directory for that user and need to run chown accordingly.
For WebHCat Check failure you will need to make sure that you are creating the "Proxyusers" properly as mentioned in: https://docs.hortonworks.com/HDPDocuments/Ambari-184.108.40.206/bk_ambari-views/content/setup_WebHCat_proxy...
hadoop.proxyuser.hcat.groups=* hadoop.proxyuser.hcat.hosts=* webhcat.proxyuser.root.groups=* webhcat.proxyuser.root.hosts=*
Created 09-21-2017 10:02 AM
Thank you for the response..
The above all are set.
These are the actual errors i am getting.
Service 'webhcat' check failed: Connection refused (Connection refused)
Service 'userhome' check failed: sandbox.hortonworks.com:50070: Connection refused (Connection refused)
How to make the connection active.
Created 09-21-2017 11:21 AM
Please check if your NameNode is running fine and and listening to port 50070
# netstat -tnlpa | grep 50070
Created 09-23-2017 03:06 PM
Created 09-24-2017 01:11 AM
As we see that your NameNode port 50070 is not opened yet, Means you need to start your NameNode first.
sandbox.hortonworks.com:50070: Connection refused (Connection refused)
If your NameNode is not coming up or if it is going down immediately after coming up then it might be a different issue which we will need to investigate by looking at the NameNode logs.
So for now you will need to make sure that your NameNode is running fine without any issue and then only you should attempt to access the Views , else you will get the "Connection Refused" Error.