HUE Quick Start Wizard Stuck at Checking Current Configuration

[#1]

Good Day All,

I installed CDH 5.12.0 on Windows 10 (home edition) / i3 64 bit OS with 8 GB RAM.

When I click on Quick Start, the HUE Quick Start Wizard gets stuck at Checking Current Configuration. Please see attached image.

I will appreciate if somebody can help me resolve this issue.

Thanks.

Regards,

-Shakeel

[#2]

I was trying today, mine is stuck too. Did your issue got resolved?

if yes, Please tell me how then?

Thanks,

Smita

[#3]

I've had the same experience using virtual box on OSX.

[#4]

I'm also having same problem

[#5]

Hello, I'm facing the same issue here. I don't know if it helps, but here is my cloudera configuration :

[#6]

For people facing the same issue : have you find a solution to this problem ?

[#7]

Same issue with Ubuntu 18.04 host.

[#8]

Same problem with Ubuntu 18.04 host...

[#9]

anyone found a solution ? having the same issue 😞

[#10]

was this issue resolved ? Pls revert if sorted.  🙂

[#11]

I also have the same issue, if anybody finds a solution ?????

[#12]

For me, Hue version 3 was not working. So I switched to version 4. Under cloudera link at the top right, I clicked check configuration. Step 1 was taking a lot of time to check configuration. I clicked on step 2,the examples were displayed, ready to be downloaded. I then went back to step 1 and it had finished checking my configuration, though it had an error. Anyway, I am glad am eventually able to access the examples.

[#13]

@BigDataEnthu This could be due to Hardware requirements or the Hue Slowness itself. As Hue itself requires Min 4GB of memory so this could be due to you have only 8GB for whole CDH. 

https://docs.cloudera.com/documentation/enterprise/release-notes/topics/hardware_requirements_guide....

I would say try to switch to Hue3 once and see the behaviour and at least try to bypass step first by just clicking on Next button or clicking on Steps 2 directly and see if this still hung. 

You can Also open Browser debugger tool to see what request is taking time and share the output here so that I can take a look.