EM 12c, EM 13c : New Deployment of Agent Fails with "emctl start agent on host Failed"

(Doc ID 2177365.1)

Last updated on DECEMBER 18, 2016

Applies to:

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

Symptoms

Agent deployment through EM Console fails with the below error:

Execution of command /software/OEM_AGENT_LOC/agent_inst/bin/emctl start agent on host Failed 

Error Message:Not Available
Exit Code :1

Fix the cause of the error and retry the operation (or) manually run the following commands on the remote host
/software/OEM_AGENT_LOC/agent_inst/bin/emctl start agent
/software/OEM_AGENT_LOC/agent_inst/bin/emctl config agent addinternaltargets

-  Attempting to start the agent manually at the target host also fails:

-  The <AGENT_INST>/sysman/log/emagent.nohup shows that the Agent is crashing during startup:

----- Sat Aug 20 07:31:00 2016::32047112::Auto tuning the agent at time Sat Aug 20 07:31:00 2016 -----
----- Sat Aug 20 07:31:03 2016::32047112::Finished auto tuning the agent at time Sat Aug 20 07:31:03 2016 -----
----- Sat Aug 20 07:31:03 2016::32047112::Launching the JVM with following options: -Xmx128M -server -Djava.security.egd=file:
///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -Xgcpolicy:gencon -----
----- Sat Aug 20 07:31:03 2016::32047112::Agent Launched with PID 33816634 at time Sat Aug 20 07:31:03 2016 -----
----- Sat Aug 20 07:31:03 2016::33816634::Time elapsed between Launch of Watchdog process and execing EMAgent is 6 secs -----
----- Sat Aug 20 07:31:03 2016::32047112::Previous Thrash State(-1,-1) -----
2016-08-20 07:31:03,899 [1:main] WARN - Missing filename for log handler 'wsm'
2016-08-20 07:31:03,929 [1:main] WARN - Missing filename for log handler 'opss'
2016-08-20 07:31:03,933 [1:main] WARN - Missing filename for log handler 'opsscfg'
----- Sat Aug 20 07:31:35 2016::32047112::Checking status of EMAgent : 33816634 -----
----- Sat Aug 20 07:36:35 2016::32047112::Checking status of EMAgent : 33816634 -----
----- Sat Aug 20 07:36:35 2016::32047112::Abnormality reported for EMAgent : 33816634 -----
----- Sat Aug 20 07:36:35 2016::32047112::Debugging component EMAgent -----
----- Sat Aug 20 07:36:35 2016::generate first thread dump file for diagnosis -----
JVMDUMP039I Processing dump event "user", detail "" at 2016/08/20 07:36:35 - please wait.
JVMDUMP032I JVM requested Java dump using '/software/OEM_AGENT/agent_inst/sysman/emd/javacore.20160820.073635.33816634.0001.txt' in response to an event
JVMDUMP010I Java dump written to /software/OEM_AGENT/agent_inst/sysman/emd/javacore.20160820.073635.33816634.0001.txt
JVMDUMP013I Processed dump event "user", detail "".
----- Sat Aug 20 07:36:45 2016::generate second thread dump file for diagnosis -----
JVMDUMP039I Processing dump event "user", detail "" at 2016/08/20 07:36:45 - please wait.
JVMDUMP032I JVM requested Java dump using '/software/OEM_AGENT/agent_inst/sysman/emd/javacore.20160820.073645.33816634.0002.txt' in response to an event
----- Sat Aug 20 07:36:45 2016::generate Threads.33816634lsof.1 for diagnosis -----
----- Attempting to kill EMAgent : 33816634 -----
----- Sat Aug 20 07:36:50 2016::32047112::EMAgent exited at Sat Aug 20 07:36:50 2016 with signal 9 -----
----- Sat Aug 20 07:36:50 2016::32047112::EMAgent either hung or in abnormal state. -----

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms