Cannot access Hue Web UI

[#1]

Hi,

I set up a Cloudera Live test cluster.

So far everything works fine, but when I try to access the Hue Web UI (at <Hue Server IP>:8888) I get a timeout.

However, Cloudera Manager can be accessed on port 7180.

Does anyone have a solution about it?

[#2]

Cloudera Manager is responsible for managing and monitoring Hue (among other things, of course). If you can log into Cloudera Manager the first screen you will see includes a list of all services. Hue's status will be shown with a red, yellow or green dot. You can click on the service, go to the processes tab, and see logs from stdout, stderr, and the actual "role log" (this is most likely the be what you want to see). What does it show as the status of Hue and do you see any errors in that log?

[#3]

Thanks for the reply Sean.

The strange thing is that the Hue status is indicated with a green dot.

I had a look at the mentioned log files and couldn't find any error.

Even if I try to connect to port 8888 via telnet from the console of the Hue Server it refuses the connection.

[#4]

Hmm... The same server that hosts CM should also host Hue (on 8888, as you're trying) and a web server on port 80 with a "Guidance Page" with a link straight to Hue. Are you trying to connect to 8888 on the same IP as the one you can connect to Cloudera Manager on? If so, I'd be curious to know if when you look at the Hue service in CM and click on the Instances tab, if it shows the Hue server running on the host you're expecting.

[#5]

Ah, I think I figured out the reason for the problem:

There are to ethernet connections, one is public, and the other is internally used by the cluster.

Unfortunately, the Hue webinterface is only accessible by using the IP of the internal NIC.

Do you know how I can change that?

I already tried to change the parameter "http_host" in hue.ini, but it didn't work...

[#6 · Accepted solution]

If you go to the configuration tab for the Hue service and use the search
bar to search for properties with "wildcard" in the name, you should see a
property to have Hue server use a wildcard instead of binding to a specific
NIC. If that isn't checked, check it and restart the service once it's
saved. That property gets set when the service is created, so it's very
unusual that it's not getting applied for you - I haven't seen that before.
Thanks for reporting, though.

[#7]

Even though the thread has some time, I wanted to say that I had the same problem and that actually solved it for me.

Thanks!

[#8]

Follow the steps in the accepted solution, then use terminal to start the "hue" service with the below command,

sudo service hue start

[#9]

Hi Sean - I have done the same checking "wildcard", but it is not working for me. Should I try anything else here?

[#10]

check the status of hue server