OBIEE 12c: Start Script Fails to Connect to the Node Manager with Error "General SSLEngine Problem"
(Doc ID 2330254.1)
Last updated on JANUARY 13, 2023
Applies to:
Business Intelligence Suite Enterprise Edition - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
On a new installation of OBIEE 12.2.1.3, SSL is configured with Custom Identity and Trust keystores.
When the out-of-the-box DOMAIN_HOME/bitools/bin/start.sh script is invoked to start all the processes and system components, the Node Manager starts successfully (which is confirmed via the DOMAIN_HOME/nodemanager/nodemanager.log and the output of $ ps -ef | grep NodeManager) but the connection to the Node Manager fails and the following error is thrown onscreen:-
----------------------------------------------------------------------------------------------------
Node manager started, but cannot connect due to: Error occurred while performing nmConnect : Cannot connect to Node Manager. : General SSLEngine problem
Use dumpStack() to view the full stacktrace :
Unable to connect to NodeManager on host: <Server Name>, due to Error occurred while performing nmConnect : Cannot connect to Node Manager. : General SSLEngine problem
Use dumpStack() to view the full stacktrace :
Failed to start one or more Servers
NodeManager (<Server Name>:9606): NOT RUNNING
Please start node manager and re-run this command to obtain complete status
----------------------------------------------------------------------------------------------------
Note that the Admin Server, Node Manager and bi_server1 Managed Server can each be started successfully via the out-of-the-box DOMAIN_HOME\bin\startWebLogic.sh, startNodeManager.sh and startManagedWebLogic.sh scripts respectively.
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 |
References |