My Oracle Support Banner

Node 3 Node Migration Fails on Step 9 at "Installpkg2/Exec[enablecmhttps_script]" (Doc ID 2209167.1)

Last updated on JANUARY 15, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.5.0 and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 


Step 9 of Node 3 node migration fails with:

************************************
Error [23642]: (//bdanode05.example.com//Stage[main]/Hadoop::Installpkg2/Exec[enablecmhttps_script]/returns)
change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/enablecmhttps.sh
&> /opt/oracle/BDAMammoth/bdaconfig/tmp/enablecmhttps_<ID>.out returned 1 instead of one of [0]
************************************

1. The file: /opt/oracle/BDAMammoth/bdaconfig/tmp/enablecmhttps_<ID>.out shows that the KEYSTORE/TRUSTSTORE path/passwords fail to be found so TLS can not be added to Navigator.

From /opt/oracle/BDAMammoth/bdaconfig/tmp/enablecmhttps_<ID>.out:

API Version used is
Error : No output returned
Failed. Full error log in : /opt/oracle/BDAMammoth/bdaconfig/tmp/cm_config_<ID>.err
json-select: no valid input found for "items?s(name:"KEYSTORE_PATH")/value/@bash@"
json-select: no valid input found for "items?s(name:"KEYSTORE_PASSWORD")/value/@bash@"
API Version used is
Error : No output returned
Failed. Full error log in : /opt/oracle/BDAMammoth/bdaconfig/tmp/cm_config_<ID>.err
API Version used is
Error : No output returned
Failed. Full error log in : /opt/oracle/BDAMammoth/bdaconfig/tmp/cm_config_<ID>.err
json-select: no valid input found for "items?s(name:"TRUSTSTORE_PATH")/value/@bash@"
json-select: no valid input found for "items?s(name:"TRUSTSTORE_PASSWORD")/value/@bash@"
API Version used is
Error : No output returned
Failed. Full error log in : /opt/oracle/BDAMammoth/bdaconfig/tmp/cm_service_roleConfigGroups_mgmt-NAVIGATORMETASERVER-BASE_config_<ID>.err

2. These files show:

curl: (7) couldn't connect to host

3. From the CM Server logs:/var/log/cloudera-scm-server/cloudera-scm-server.out and /var/log/cloudera-scm-server/cloudera-scm-server.log:

a) cloudera-scm-server.out:

JAVA_HOME=/usr/java/jdk1.8.0_92
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Exception in thread "MainThread" org.apache.avro.AvroRuntimeException: java.io.FileNotFoundException: /var/lib/cloudera-scm-server/ssl/.keystore (No such file or directory)
at com.cloudera.server.common.HttpConnectorServer.start(HttpConnectorServer.java:89)
at com.cloudera.server.cmf.Main.startAgentServer(Main.java:571)
at com.cloudera.server.cmf.Main.startAvro(Main.java:483)
at com.cloudera.server.cmf.Main.run(Main.java:620)
at com.cloudera.server.cmf.Main.main(Main.java:217)
Caused by: java.io.FileNotFoundException: /var/lib/cloudera-scm-server/ssl/.keystore (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at org.mortbay.resource.FileResource.getInputStream(FileResource.java:275)
at org.mortbay.jetty.security.SslSelectChannelConnector.createSSLContext(SslSelectChannelConnector.java:639)
at org.mortbay.jetty.security.SslSelectChannelConnector.doStart(SslSelectChannelConnector.java:613)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.Server.doStart(Server.java:235)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at com.cloudera.server.common.HttpConnectorServer.start(HttpConnectorServer.java:87)
...

b) cloudera-scm-server.log:

2016-04-21 11:46:06,411 ERROR main:org.hibernate.engine.jdbc.spi.SqlExceptionHelper: Connections could not be acquired from the underlying database!
2016-04-21 11:46:06,414 INFO main:org.springframework.beans.factory.support.DefaultListableBeanFactory: Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@*: defining beans [commandLineConfigurationBean,entityManagerFactoryBean,com.cloudera.server.cmf.TrialState,com.cloudera.server.cmf.TrialManager,
com.cloudera.cmf.crypto.LicenseLoader]; root of factory hierarchy
2016-04-21 11:46:06,414 ERROR main:com.cloudera.server.cmf.Main: Server failed.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.cloudera.server.cmf.TrialState': Cannot resolve reference to bean 'entityManagerFactoryBean' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactoryBean': FactoryBean threw exception on object creation; nested exception is javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Could not open connection
...

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.