Reply
Explorer
Posts: 19
Registered: ‎12-02-2014

NameNode URL not accesible on Kerberos Cluster

 Hi Community,

 

I have a few of CDH clusters with Kerberos enabled but I've been facing issue to not able to access the NN URL. Here is error message:

=================

HTTP ERROR 401

Problem accessing /index.html. Reason:

    Authentication required

 

Powered by Jetty://

=================

 

 

However, Yarn NM, Job history and Spark URLs are just working fine. I've checked with my team who are using both Windows and Mac laptops and they are facing same issue. THis issue still happens with latest CDH5.10

 

Is there a workaround to address this issue for Mac OS?

 

Thanks,

Silaphet 

 

 

Posts: 341
Topics: 0
Kudos: 35
Solutions: 27
Registered: ‎08-16-2016

Re: NameNode URL not accesible on Kerberos Cluster

You have HTTP Authentication turned on for HDFS.

CM > HDFS > Configuration > Enable Kerberos Authentication for HTTP Web-Consoles.

You can turn it off if you don't require it.

Or you can follow the below link to configure your browser to auth for the site.

https://www.cloudera.com/documentation/enterprise/5-6-x/topics/cdh_sg_browser_access_kerberos_protec...
Explorer
Posts: 19
Registered: ‎12-02-2014

Re: NameNode URL not accesible on Kerberos Cluster

Hi,

 

I have been looking to configure the "Google Chrome" on my Mac laptop by the command does not work. Could you please validate the command and I can give it another try?

 

I don't want to turn off the HTTP web-consoles if possible.

 

Thanks,

SIlaphet 

Posts: 341
Topics: 0
Kudos: 35
Solutions: 27
Registered: ‎08-16-2016

Re: NameNode URL not accesible on Kerberos Cluster

Download Firefox and configure. See if it works before we dig into Chrome. That way we will know that we just need to get Chrome to negotiate with the site.
Explorer
Posts: 19
Registered: ‎12-02-2014

Re: NameNode URL not accesible on Kerberos Cluster

Hi,

 

Quick update, it works with Firefox. However, with HDFS HA, it does not work well when we rollover active NN to another node.

 

Is there away to configure this with HDFS HA enabled?

 

Thanks,

Silaphet

Posts: 341
Topics: 0
Kudos: 35
Solutions: 27
Registered: ‎08-16-2016

Re: NameNode URL not accesible on Kerberos Cluster

What do you mean "it does not work well"? Does the second NN UI not work? Is there an error?
Announcements