Reply
Cloudera Employee
Posts: 717
Registered: ‎07-30-2013

Re: New Cloudera installation: Hue - Bad Request (400)

Are you using CM? Could you check that the hue.ini has the correct
'allow_host=*' in the desktop section?
kfc
Explorer
Posts: 8
Registered: ‎02-06-2017

Re: New Cloudera installation: Hue - Bad Request (400)

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.

New Contributor
Posts: 20
Registered: ‎12-27-2016

Re: New Cloudera installation: Hue - Bad Request (400)

hi Romainr, can you please escalate this ticket to cloudera devOps group ?

 

THANKS

 

Best regards

Georges-Louis

Cloudera Employee
Posts: 717
Registered: ‎07-30-2013

Re: New Cloudera installation: Hue - Bad Request (400)

You are probably not modifying the correct hue.ini, if you use CM, please
look at the generated hue.ini from the Hue role
New Contributor
Posts: 2
Registered: ‎02-06-2017

Re: New Cloudera installation: Hue - Bad Request (400)

Hello,

 

I am receiving the same error message on one of our installationas as well.

Running version:

5.10.0-1.cdh5.10.0.p0.41
New Contributor
Posts: 20
Registered: ‎12-27-2016

Re: New Cloudera installation: Hue - Bad Request (400)

hi Romainr,

 

allow_hosts=* at /etc/hue/conf/hue.ini didnt help anything

Highlighted
kfc
Explorer
Posts: 8
Registered: ‎02-06-2017

Re: New Cloudera installation: Hue - Bad Request (400)

[ Edited ]

different hue.ini same error.

/opt/cloudera/parcels/CDH-5.10.0-1.cdh5.10.0.p0.41/lib/hue/desktop/conf
[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=*

 

UPDATE:
 and btw. /etc/hue/hue.ini is exactly the same cause it links to the same dir....

Cloudera Employee
Posts: 717
Registered: ‎07-30-2013

Re: New Cloudera installation: Hue - Bad Request (400)

*Note:* To override a value in Cloudera Manager, you need to enter verbatim
each mini section from below into the Hue Safety Valve
:
Hue Service → Configuration → Service-Wide → Advanced → Hue Service
Advanced Configuration Snippet (Safety Valve) for hue_safety_valve.ini


http://gethue.com/how-to-configure-hue-in-your-hadoop-cluster/
kfc
Explorer
Posts: 8
Registered: ‎02-06-2017

Re: New Cloudera installation: Hue - Bad Request (400)

thx for the link added it exactly there via CM now.

Syntax like:
allow_host=*

 

and gues what... no change bad request 400

Posts: 958
Topics: 1
Kudos: 230
Solutions: 121
Registered: ‎04-22-2014

Re: New Cloudera installation: Hue - Bad Request (400)

Everyone,

 

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.

 

Ben

Announcements