Support Questions

Find answers, ask questions, and share your expertise

Hue continuosly regenerate configuration

avatar
New Contributor

I've got an instance of hue server on my host configured to use infra-solr, and it's tell me that it's got stale configuration on solr_url because the server is changed. 

If I restart the hue service for the first minute everything is good, but just some minute later it tells me again that's got stale configuration. The solr_url value isn't changed, there's the same url that was before i restart the service. Seems like it cannot update hue.ini config file

Any help?

1 ACCEPTED SOLUTION

avatar
New Contributor

I don't know how, but I resolved the issue. For some reason i've to install Ranger RMS, but on the host where I've Ranger i don't have enough RAM to take both Ranger and Ranger RMS. So I've migrated Ranger to a new host with enough RAM to run both, and during the migration i've got an error because Postgre reached the maxinum active  connection. Later that, the issue was fixed... So i think the cause was the DB

View solution in original post

2 REPLIES 2

avatar
Community Manager

@im_al3x Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our Hue experts @nramanaiah @dturnau  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.


Regards,

Diana Torres,
Community Moderator


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community:

avatar
New Contributor

I don't know how, but I resolved the issue. For some reason i've to install Ranger RMS, but on the host where I've Ranger i don't have enough RAM to take both Ranger and Ranger RMS. So I've migrated Ranger to a new host with enough RAM to run both, and during the migration i've got an error because Postgre reached the maxinum active  connection. Later that, the issue was fixed... So i think the cause was the DB