Member since
01-19-2017
3676
Posts
632
Kudos Received
372
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 609 | 06-04-2025 11:36 PM | |
| 1175 | 03-23-2025 05:23 AM | |
| 579 | 03-17-2025 10:18 AM | |
| 2183 | 03-05-2025 01:34 PM | |
| 1373 | 03-03-2025 01:09 PM |
09-01-2017
05:34 AM
@Sam Red 2 things to do can you first restart the cluster and see if it persists. What is the value for WebHDFS Authentication in the views ? From the stack trace the problem is due to the mapping from full Kerberos principal name to short username. This mapping is driven by the following configuration property in core-site.xml. <property>
<name>hadoop.security.auth_to_local</name>
<value></value>
<description>Maps kerberos principals to local user names</description>
</property> Please revert
... View more
08-31-2017
10:13 PM
@Sam Red The bold part obscured above should be part Authentication part in the File/hive view hadoop.proxyuser.ambari-server-xxxx.hosts hadoop.proxyuser.ambari-server-xxxx.groups In the part of the views WebHDFS Authentication : auth=KERBEROS;proxyuser=ambari-server-xxxx@REALM
... View more
08-31-2017
09:54 PM
1 Kudo
@Sam Red Then you have to use hadoop.proxyuser.root.groups=*
hadoop.proxyuser.root.hosts=* hadoop.proxyuser.ambari-server.groups=*
hadoop.proxyuser.ambari-server.hosts=*
... View more
08-31-2017
09:45 PM
@Sam Red Here we are talking of the user running the ambari processes check like below # ls -al /etc/ambari-server/conf/ Regards
... View more
08-31-2017
09:29 PM
@Sam Red Can you also check this values If you are running Ambari Server as root user then add below properties hadoop.proxyuser.root.groups=*
hadoop.proxyuser.root.hosts=* .If you are running Ambari server as non-root user then please add below properties in core-site.xml hadoop.proxyuser.<ambari-server-user>.groups=*
hadoop.proxyuser.<ambari-server-user>.hosts=* Please replace <ambari-server-user> with user running Ambari Server in above example. . Your ambari server principal is ambari-server@REALM.COM, if not then please replace 'ambari-server' with your principal's user part. hadoop.proxyuser.ambari-server.groups=*hadoop.proxyuser.ambari-server.hosts=* . We already created user directory on hdfs for the user accessing hive view admin user to access hive and hdfs view. .As hdfs user we did already the first 2 run the last one chmod $ hdfs hadoop fs -mkdir /user/admin
$ hdfs hadoop fs -chown admin:hdfs /user/admin
$ hdfs hadoop fs -chmod 755/user/admin Revert
... View more
08-31-2017
08:54 PM
@Sam Red Whats the values of the ambari-server filter for hive and hdfs HIVE webhcat.proxyuser.ambari-server-xxxx.groups=*
webhcat.proxyuser.ambari-server-xxxx.hosts=* HDFS hadoop.proxyuser.hcat.groups=*
hadoop.proxyuser.hcat.hosts=*
hadoop.proxyuser.hdfs.groups=*
hadoop.proxyuser.hdfs.hosts=* Revert
... View more
08-31-2017
07:36 PM
@Sam Red 1.You will need to create a user home for the one running the view in this case admin as root # su - hdfs
$hdfs dfs -mkdir /user/admin
$hdfs dfs -chown admin:hdfs /user/admin That should resolve the "'userhome' check failed: Authentication required " 2. For the kerberos authentication for both hive and the file, view create a new view and l WebHDFS Authentication = auth=KERBEROS;proxyuser=ambari-server-$cluster@REALM To configure the views hive/files create a new view see below example Instance name = Test2 Displayname =Test2 Description =Test Files or hive Keep all the other parameters as is and only change the WebHDFS Authentication see attached screenshot the value for proxyuser should be the values obtained in the screenshot 1 using the filter ambari-server for hive and hdfs are identical Please let me know if that helped
... View more
08-31-2017
09:40 AM
@Joshua Adeleke This is what it means " The 401 Unauthorized error is an HTTP status code that means the page you were trying to access cannot be loaded until you first log in with a valid user ID" How to Fix the 401 Unauthorized Error
Check for errors in the URL. It's possible that the 401 Unauthorized error appeared because the URL was typed incorrectly or the link that was clicked on points to the wrong URL - one that is for authorized users only. If you're sure the URL is valid, visit the website's main page and look for a link that says Login or Secure Access. Enter your credentials here and then try the page again. If you don't have credentials, follow the instructions provided on the website for setting up an account. If you're sure the page you're trying to reach shouldn't need authorization, the 401 Unauthorized error message may be a mistake. At that point, it's probably best to contact the webmaster or other website contact and inform them of the problem. Tip: The webmaster of some websites can be reached via email at webmaster@website.com, replacing website.com with the actual website name.
The 401 Unauthorized error can also appear immediately after login, which is an indication that the website received your username and password but found something about them to be invalid (e.g. your password is incorrect). Follow whatever process is in place at the website to regain access to their system.
... View more
08-30-2017
11:24 AM
@pooja shrivastava Have you resolved the issue.
... View more