EM 13c: Enterprise Manager 13.2 Cloud Control Agent Fails to Start after Upgrade: EMAgent either hung or in abnormal state

(Doc ID 2232227.1)

Last updated on FEBRUARY 17, 2017

Applies to:

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

Symptoms

The Enterprise Manager (EM) 12.1.0.4 Cloud Control Agent has been successfully upgraded to version 13.2, however, the upgraded agent fails to start.

From the .../agent_inst/sysman/log/emagent.nohup file:

--- EMState agent
----- 2017-01-25 10:13:02,251::18033::Auto tuning the agent at time 2017-01-25 10:13:02,251 -----
----- 2017-01-25 10:13:03,058::18033::Finished auto tuning the agent at time 2017-01-25 10:13:03,057 -----
----- 2017-01-25 10:13:03,063::18033::Launching the JVM with following options: -Xmx512M -XX:MaxPermSize=256 -server -Djava.security.egd=file:///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -XX:-UseLargePages -XX:+UseLinuxPosixThreadCPUClocks -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops -----
----- 2017-01-25 10:13:03,064::18033::Agent Launched with PID 18110 at time 2017-01-25 10:13:03,064 -----
----- 2017-01-25 10:13:03,064::18110::Time elapsed between Launch of Watchdog process and execing EMAgent is 2 secs -----
----- 2017-01-25 10:13:03,064::18033::Previous Thrash State(-1,-1) -----
2017-01-25 10:13:03,470 [1:main (@ 2017-01-25 10:13:03 BRST)] WARN - Missing filename for log handler 'wsm'
2017-01-25 10:13:03,492 [1:main (@ 2017-01-25 10:13:03 BRST)] WARN - Missing filename for log handler 'opss'
2017-01-25 10:13:03,496 [1:main (@ 2017-01-25 10:13:03 BRST)] WARN - Missing filename for log handler 'opsscfg'
----- 2017-01-25 10:23:35,028::18033::Checking status of EMAgent : 18110 -----
----- 2017-01-25 10:23:35,029::18033::Hang detected for EMAgent : 18110 -----
----- 2017-01-25 10:23:35,029::18033::Debugging component EMAgent -----
----- 2017-01-25 10:23:35,029::generate first thread dump file for diagnosis -----
----- 2017-01-25 10:23:45,486::generate second thread dump file for diagnosis -----
----- 2017-01-25 10:23:45,746::generate Threads.18110lsof.1 for diagnosis -----
----- Attempting to kill EMAgent : 18110 -----
----- 2017-01-25 10:23:50,886::18033::EMAgent exited at 2017-01-25 10:23:50,886 with signal 9 -----
----- 2017-01-25 10:23:50,886::18033::EMAgent either hung or in abnormal state. -----
----- 2017-01-25 10:23:50,886::18033::EMAgent will be restarted/thrashed. -----
----- 2017-01-25 10:23:50,886::18033::writeAbnormalExitTimestampToAgntStmp: exitCause=ABNORMAL : restartRequired=1 -----
----- 2017-01-25 10:23:50,887::18033::Restarting EMAgent. -----
----- 2017-01-25 10:23:51,219::18033::Auto tuning the agent at time 2017-01-25 10:23:51,219 -----
----- 2017-01-25 10:23:52,042::18033::Finished auto tuning the agent at time 2017-01-25 10:23:52,042 -----
----- 2017-01-25 10:23:52,047::18033::Launching the JVM with following options: -Xmx512M -XX:MaxPermSize=256 -server -Djava.security.egd=file:///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -XX:-UseLargePages -XX:+UseLinuxPosixThreadCPUClocks -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops -----
----- 2017-01-25 10:23:52,048::18033::Agent Launched with PID 20228 at time 2017-01-25 10:23:52,048 -----
----- 2017-01-25 10:23:52,048::20228::Execing EMAgent process is taking longer than expected 120 secs -----
----- 2017-01-25 10:23:52,048::20228::Time elapsed between Launch of Watchdog process and execing EMAgent is 651 secs -------



 

 

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