02-06-2017 08:46 AM
as written before.
Other apps like CM or resource manager are reachable and working without any problems only hue did not.
And yes as mentioned before
Adding allow_hosts=* at /etc/hue/conf/hue.ini didnt help anything.
02-06-2017 09:49 AM - edited 02-06-2017 09:54 AM
different hue.ini same error.
[desktop] # Set this to a random string, the longer the better. # This is used for secure hashing in the session store. secret_key= # Execute this script to produce the Django secret key. This will be used when # 'secret_key' is not set. ## secret_key_script= # Webserver listens on this address and port http_host=0.0.0.0 http_port=8888 allow_host=*
and btw. /etc/hue/hue.ini is exactly the same cause it links to the same dir....
02-06-2017 10:03 AM
02-06-2017 10:54 AM
If you are using a Cloudera Manager managed cluster, then you need to set hue.ini edits in:
Hue Service Advanced Configuration Snippet (Safety Valve) for hue_safety_valve.ini
Cloudera Manager will distribute that configuration to the process directory that is used to read in the configuration for Hue when it starts. So, if you update files directly, it should not impact the configuration for Hue.
I would recommend testing after making the updates to the Cloudera Manager safety valve and let us know if that helps at all ... make sure you have restarted Hue.
As another note, I installed a clean Ubuntu 14.04 instance and then installed 5.10. Using the embedded DB for Hue, all sync and migrations ran well and I can log into Hue with no changes. There must be another factor here that we are not seeing. If the safety valve update and restart does not fix the issue, I'll try to come up with some other things we can check.