My Oracle Support Banner

EM 13c: OMS Startup Fails with 'Node Manager Could Not Be Started'. (Doc ID 2656089.1)

Last updated on APRIL 09, 2020

Applies to:

Enterprise Manager Base Platform - Version 13.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

EM OMS Fails to start after importing the custom keystores for weblogic components.

$emctl start oms

Oracle Enterprise Manager Cloud Control 13c Release 3
Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved.
Starting Oracle Management Server...
WebTier Successfully Started
Node Manager Could Not Be Started
Check Node Manager log file for details: /u01/app/em13c/gc_inst/user_projects/domains/GCDomain/nodemanager/nodemanager.log
Oracle Management Server is Down
JVMD Engine is Down
Starting BI Publisher Server ...
Node Manager Could Not Be Started
Check Node Manager log file for details: /u01/app/em13c/gc_inst/user_projects/domains/GCDomain/nodemanager/nodemanager.log
BI Publisher Server is Down

$../gc_inst/em/EMGC_OMS1/sysman/log/emctl.log reports the following errors:

2020-03-25 09:54:22,764 [Thread-1] INFO commands.BaseCommand run.605 - <OUT>NMProcess: <Mar 25, 2020 9:54:22 AM CDT> <INFO> <Loading identity key store: FileName=../gc_inst/user_projects/domains/GCDomain/security/customKeystore.jks, Type=jks, PassPhraseUsed=false>
2020-03-25 09:54:22,777 [Thread-1] INFO commands.BaseCommand run.605 - <OUT>NMProcess: <Mar 25, 2020 9:54:22 AM CDT> <SEVERE> <Fatal error in NodeManager server: com.rsa.jsafe.JSAFE_PaddingException: Invalid padding.>

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


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