My Oracle Support Banner

EM13c, EM12c : Agent Start Up Fails With Error "Agent status could not be determined" (Doc ID 2363786.1)

Last updated on MARCH 11, 2020

Applies to:

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

Symptoms

In Enterprise Manager (EM) Cloud Control, Trying to start the agent fails,

$ ./emctl start agent
Oracle Enterprise Manager Cloud Control 12c Release 5
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
Agent status could not be determined. Check the agent process
Consult emctl.log and emagent.nohup in: <Agent_Inst>/sysman/log

Trying to Stop agent is not showing any results. Some cases observed none of the agent logs were getting updated.

Few cases seen the following stack from <Agent_Inst>/sysman/log/emctl.log file:

15868 :: Mon Feb 19 10:47:44 2018::AgentCommandLock:Acquiring a lock(type=1)on emctl lockfile
15868 :: Mon Feb 19 10:47:44 2018::AgentCommandLock:lockFile returns 1
15868 :: Mon Feb 19 10:47:44 2018::acquireGlobalLock returned: 1
15868 :: Mon Feb 19 10:47:44 2018::EM_SECURE_HOSTNME: comhp44
15868 :: Mon Feb 19 10:47:44 2018::EM_SECURE_PORT: 1830
15868 :: Mon Feb 19 10:47:44 2018::EM_LISTEN_ON_ALL_NICS: true
15868 :: Mon Feb 19 10:47:50 2018::AgentLifeCycle.pm:status agent returned with retCode=2
15868 :: Mon Feb 19 10:47:50 2018::AgentLifeCycle.pm: Exiting with retCode=1: Could not determine the status of the agent process
15868 :: Mon Feb 19 10:47:50 2018::TZ:SAT5 EmctlLogAvailabilityMarker Operation=start Diag=2(status could not be determined)

 

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.