Hub Web UI doesn't work

[#1]

Hi,  I have a cluster witn CDH 5.4.2,  and the whole cluster is working fine, but when I try to access to the Hue Web UI doesn't work, ( https://host:7180/cmf/services/23/status ) when I go to https://host:8888 , it doesn't work.. ( it looks like a ERR_CONNECTION_TIMED_OUT error )   I got the next error at the Log from Hue.  

5:37:45 AM INFO settings Welcome to Hue 3.7.0

5:37:46 AM WARNING __init__ Couldn't import snappy. Support for snappy compression disabled.[09/Jun/2015 20:00:13 ] settings INFO Welcome to Hue 3.7.0

6:00:14 AM WARNING __init__ Couldn't import snappy. Support for snappy compression disabled.

6:00:14 AM INFO settings Welcome to Hue 3.7.0

6:00:15 AM WARNING __init__ Couldn't import snappy. Support for snappy compression disabled.  

do you have any idea ? 

[#2]

Could we get more log information about the Hue services? (the lines above
are just warnings when snappy is not installed and does not matter).

What is the health of Hue too in CM?

Romain

[#3]

Hi, 

Thanks for your answerd, but I find out that it's something wrong with the gateway or something.

I can reach port 7180 .. that is for Cloudera Manager, 

But I can not reach Ports:

8888 - for Hue

50070 - for HDFS

8983 - for Solr ( also .. ports for Impala, Yarn )

those ports I already add as a DNAT rule, 

when I did a telnet test ... to those specifict ports.. I got an

HTTP/1.1 408 Request Timeout

[#4]

nd the health of the whole CM is ok .. ( all the programs, are working fine.. they have green light )

also I restart the CM , twice, in order to test it.. but I still got the same error.. 

[#5 · Accepted solution]

Hum, seems like you have a firewall issue or something like that

[#6]

actually i get 

Clock Offset

on the whole clusters 

but when i try to updated 

$ sudo ntpdate pool.ntp.org
$ sudo service ntp stop
$ sudo ntpdate pool.ntp.org
$ sudo service ntp start

i got an error

no server suitable for synchronization found

also i try the next.. 

 $ sudo ntpdate ntp.ubuntu.com

**** ntpdate[1258]: no server suitable for synchronization found
$ sudo ntpdate pool.ntp.org
**** ntpdate[1267]: no server suitable for synchronization found
$ sudo ntpdate de.pool.ntp.org
**** ntpdate[1273]: no server suitable for synchronization found
$ sudo ntpdate us.pool.ntp.org
**** ntpdate[1276]: no server suitable for synchronization found

do you have any suggest?

[#7]

There was no Firewall issue for me.

[#8]

Facing the same issue. Can't connect to the other ports like 

8888 - for Hue

50070 - for HDFS

When try to open hue web ui.... its saying "

This site can’t be reached

gke-hadoop-ubuntu-default-pool-78514257-626p.c.platform-services.internal’s server DNS address could not be found.

DNS_PROBE_FINISHED_NXDOMAIN"

Please help.

[#9]

@frankenstein, "server DNS address could not be found." indicates that your configured DNS servers on the browser host cannot resolve your hostname.  Make sure gke-hadoop-ubuntu-default-pool-78514257-626p.c.platform-services.internal  can be resolved to an IP address on your browser host.

[#10]

@bgooley "How to resolve the hostname on browser host. Can you please explain the solution in detail."

[#11]

In putty connected to the master instace and performed ping gke-hadoop-ubuntu-default-pool-78514257-626p.c.platform-services.internal ..... its responding. Also performed curl http://gke-hadoop-ubuntu-default-pool-78514257-626p.c.platform-services.internal:10002/ (my hue server is down so tried connecting to hive having 10002 port) got this:

I think in putty its connected but in browser its not resolving the hostname....

[#12]

@bgooley "How to resolve the hostname on browser host. Can you please explain the solution in detail."

[#13]

@Genthandsome,

I'm talking about DNS.

https://en.wikipedia.org/wiki/Domain_Name_System

For instance, if using a DNS server for name resolution:

$ nslookup www.google.com

Server:        x.x.x.x
Address:    x.x.x.x#53

Non-authoritative answer:
Name:    www.google.com
Address: 172.217.0.36

My point in this case is that someone got an error saying that the browser could not resolve the IP.

For example, see:

https://stackoverflow.com/questions/36668374/how-do-i-solve-the-server-dns-address-could-not-be-foun...

The browser problem showed an issue with the browser and how it tries to communicate with the server host; it had nothing to do with Hue.

[#14]

@Genthandsome,

Actually, that stackoverflow may be off target since it talks about public addresses.  Your browser needs to resolve a hostname into an IP so that your computer can connect to Hue.  If that resolution (or mapping) fails then the client (browser in this case) cannot connect to the host specified in the browser's URL.

[#15]

I got these WARN in kt renewer under hue log and after two hours of troubleshooting learnt that the PID on Cloudera Monitoring serverices had some conflicts.

Had to stop Cloudera Monitor services

restart cloudera-scm-server and agent

It did all the magic.

Issue resolved..

It might be different for others, though.