My Oracle Support Banner

Oracle Enterprise Manager 13c Emctl Start Oms Failed. Node Manager Could Not Be Started (Doc ID 2526340.1)

Last updated on NOVEMBER 16, 2022

Applies to:

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

Symptoms

Enterprise Manager (EM) 13.2.2 Cloud Control

The EM 13.2.2 OMS does not start, providing this message:

Node Manager Could Not Be Started
Check Node Manager log file for details: <OMS Instance Base>/gc_inst/user_projects/domains/GCDomain/nodemanager/nodemanager.log
Oracle Management Server is Down

The <OMS Instance Base>/gc_inst/em/EMGC_OMS1/sysman/log/emctl.log shows:

2019-03-27 11:12:00,459 [Thread-1] INFO commands.BaseCommand run.605 - <OUT>weblogic.nodemanager.NMConnectException: Connection refused. Could not connect to NodeManager. Check that it is running at <HOST NAME>/<IP Address>:7401.
2019-03-27 11:12:00,460 [Thread-1] INFO commands.BaseCommand run.605 - <OUT>Node Manager is not up, sleeping for five seconds...
2019-03-27 11:12:01,790 [Thread-1] INFO commands.BaseCommand run.605 - <OUT>NMProcess: Mar 27, 2019 11:12:01 AM weblogic.nodemanager.server.NMServer main
2019-03-27 11:12:01,791 [Thread-1] INFO commands.BaseCommand run.605 - <OUT>NMProcess: SEVERE: Fatal error in NodeManager server: Could not obtain exclusive lock with lockFile '<PATH>/gc_inst/user_projects/domains/GCDomain/nodemanager/nodemanager.process.lck'. This most likely indicates another NodeManager process is already running in this NodeManaagerHome.



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.