- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 67 Insurance
- 536.8K On-Premises Infrastructure
- 138.5K Analytics Software
- 38.6K Application Development Software
- 5.9K Cloud Platform
- 109.5K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.2K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
NodeManager.sh - xxx.com:9506: NOT RUNNING (General SSLEngine problem)
first of all I want to state my versions I am using for the upcoming scenario / question:
OBIEE: Version 188.8.131.52.0
OBI Administration Tool: Version 184.108.40.206.0
Oracle Essbase: Version 220.127.116.11.008.28
Server OS: Linux RedHat Enterprise Edition 7.9
Yesterday I tried to restart our Oracle BI environment which was successfully running since May 2016 in SSL-mode (SHA2).
The Linux-terminal shows me the following output:
[[email protected] bin]$ bi_start Starting domain; Using domainHome: /opt/oracle/base/product/fmw/user_projects/domains/bi ... Initializing WebLogic Scripting Tool (WLST) ... Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands <Feb 1, 2022 12:21:17 PM CET> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.> <Feb 1, 2022 12:21:17 PM CET> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.> <Feb 1, 2022 12:21:17 PM CET> <Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation: weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.> Unable to connect to running NodeManager on host: xxx.com, 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 (xxx.com:9506): NOT RUNNING
It seems that the NoteManger is still using the pre-defined Oracle certicates which came with the initial installation. For all other components I have actually installed a separate company certificate in the past which is still valid until the end of the year. I guess that the Oracle certicate is not valid anymore and therefore I am not able to start up the NodeManager.
I have already tried to following conslusion:
The connection to the admin server was successful and I was able to perform the synchronisation as described. Unfortunately, there was no change in behavior.
I also tried this approach without any success:
Maybe someone of you has also struggled with the same problem and give me a little hint / help on it?
Best regards and thanks in advance