Support Questions

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

CDP data warehousing catalog creation error

avatar

Hi Team,

We have CDP cluster integrated with OpenShift cluster, private cloud setup with all the service like hive, atlas, ranger running. 

When we are creating the Datawarehouse CatLog in management console we are getting the below error in console, can you please help us to find out the cause.

some Errors from management console: 

1. Driver failed to create DB Catalog: IP address is not expected for default warheouse RDS endpoint. Check if RDS is enabled in the env? Error Code : 9999

2. timeout exceeded transitioning from state 'Starting'.Last event: {InProgress checking if metastore statefulset is ready with at least 1 ready replica(s) (config-id: 5afc7144-9409-47e2-a9b9-2c7822adafbf version: 2022.0.7.1-2) 2023-02-09 10:08:44.366274685 +0000 UTC} Error Code : 9999

OpenShift pods log:

/usr/local/bin/config-merger /tmp/hive/conf/atlas-application.properties /mnt/config/current/atlas-application.properties /etc/hive/conf/atlas-application.properties -wf2 atlas.rest.address -wf2 atlas.kafka.bootstrap.servers -wf2 atlas.kafka.zookeeper.sync.time.ms -wf2 atlas.kafka.security.protocol -wf2 atlas.enableTLS -wf2 atlas.jaas.KafkaClient.option.principal -wf2 atlas.jaas.KafkaClient.option.serviceName -wf2 atlas.kafka.sasl.kerberos.service.name -setfromparams atlas.jaas.KafkaClient.option.principal=$+SERVICE_PRINCIPAL -set truststore.file=/mnt/config/current/truststore.jks -set atlas.kafka.ssl.truststore.location=/mnt/config/current/truststore.jks -set hadoop.security.credential.provider.path=localjceks://file/jceks/secrets.jceks -set truststore.password=changeit -set cert.stores.credential.provider.path=localjceks://file/jceks/secrets.jceks -set atlas.jaas.KafkaClient.option.keyTab=/mnt/config/current/hive

4 REPLIES 4

avatar
Master Collaborator

Hi @suryawanshinp , 
Looks like the error you list in point (1) can potentially be due to your external postresDB database using an IP address instead of the hostname. Please consult the documentation here: https://docs.cloudera.com/cdp-private-cloud-data-services/1.5.0/installation/topics/cdppvc-installat...

 

 

Kind regards,

Alex

 

avatar

@aakulov  : Yes, external postgress DB database configured with IP address as per document link provided, we changed it to hostname . but still getting same error. no luck.

avatar
Master Collaborator

I would suggest working with Cloudera support on this, as they would be best suited for analyzing logs and suggesting next steps.

avatar
Community Manager

@suryawanshinp Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks


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: