Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Cloudera CDP 7.1.3 - Error running solr query, please check solr configs. Collection not found: ranger_audits

avatar
Explorer

Hi folks,

  After install Cloudera CDP 7.1.3 we try to access on RANGER CONSOLE --> AUDIT --> ACCESS and we get this error/message

"Error running solr query, please check solr configs. Collection not found: ranger_audits"

Looking file catalina.out

==================================================================================

Oct 19, 2020 11:59:39 PM org.apache.ranger.server.tomcat.SolrCollectionBootstrapper connect
INFO: Solr is in Cloud mode
Oct 19, 2020 11:59:39 PM org.apache.ranger.server.tomcat.SolrCollectionBootstrapper uploadConfiguration
INFO: Config already exists with name ranger_audits
Oct 19, 2020 11:59:41 PM org.apache.ranger.server.tomcat.SolrCollectionBootstrapper createCollection SEVERE: Error while creating collection in solr : org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://XXXXXXXXXXXX:8993/solr: Underlying core creation failed while creating collection: ranger_audits
Oct 19, 2020 11:59:41 PM org.apache.ranger.server.tomcat.SolrCollectionBootstrapper logErrorMessageAndWait SEVERE: Error while performing operations on solr. [retrying after 60000 ms]

==================================================================================

We run these steps using this information:

https://docs.cloudera.com/cdp-private-cloud-base/7.1.3/installation/topics/cdpdc-additional-steps-ra...

But it is still this error.

thanks for you help.

Regards

Eduardo

 

1 ACCEPTED SOLUTION

avatar
Explorer

Hi all,

 We upgrade do CDP 7.1.4 and this problem solves. We don´t know why happening this problem, but the upgrade solve it.

 

close issue.

thanks

 

View solution in original post

1 REPLY 1

avatar
Explorer

Hi all,

 We upgrade do CDP 7.1.4 and this problem solves. We don´t know why happening this problem, but the upgrade solve it.

 

close issue.

thanks