{"id":2142,"date":"2016-05-16T13:44:40","date_gmt":"2016-05-16T16:44:40","guid":{"rendered":"http:\/\/www.dbarj.com.br\/en\/?p=2142"},"modified":"2016-05-16T14:12:42","modified_gmt":"2016-05-16T17:12:42","slug":"em-agent-start-fails-outofmemoryerror","status":"publish","type":"post","link":"https:\/\/www.dbarj.com.br\/en\/2016\/05\/em-agent-start-fails-outofmemoryerror\/","title":{"rendered":"EM agent start fails With ‘Target Interaction Manager failed at Startup’ and ‘java.lang.OutOfMemoryError: Java heap space’ reported on logs"},"content":{"rendered":"

In this article, I will show\u00a0how to solve EM Agent failing to startup\u00a0related to java memory problems.<\/p>\n

Those days,\u00a0after applying some EM Agent patches and trying to restart them,\u00a0I received the error below:<\/p>\n

[emc12@localhost ~]$ emctl start agent\r\nOracle Enterprise Manager Cloud Control 12c Release 5\r\nCopyright (c) 1996, 2015 Oracle Corporation.  All rights reserved.\r\nStarting agent ........................................................................... failed.\r\nFatal agent error: Target Interaction Manager failed at Startup\r\nFatal agent error: Target Interaction Manager failed at Startup\r\nFatal agent error: Target Interaction Manager failed at Startup\r\nEMAgent is Thrashing. Exiting watchdog\r\nConsult emctl.log and emagent.nohup in: \/u01\/app\/emc12\/agent_inst\/sysman\/log\r\n[emc12@localhost ~]$<\/pre>\n
When checking the emagent.nohup<\/strong> file, there was an error related to java memory:<\/p>\n
Agent is going down due to an OutOfMemoryError\r\n----- Fri May 13 10:46:21 2016::18719::Checking status of EMAgent : 19177 -----\r\n----- Fri May 13 10:46:21 2016::18719::EMAgent exited at Fri May 13 10:46:21 2016 with return value 57. -----\r\n----- Fri May 13 10:46:21 2016::18719::EMAgent will be restarted because of an Out of Memory Exception. -----\r\n----- Fri May 13 10:46:21 2016::18719::EMAgent is Thrashing. Exiting loop. -----\r\n----- Fri May 13 10:46:21 2016::18719::Commiting Process death. -----\r\n----- Fri May 13 10:46:21 2016::18719::writeAbnormalExitTimestampToAgntStmp: exitCause=OOM : restartRequired=0 -----\r\n----- Fri May 13 10:46:21 2016::18719::Exited due to Thrash. -----<\/pre>\n
As the error shows, it was an “Out of Memory Exception<\/strong>“. To solve it, I had to increase the java heap space allocated to emagent.<\/p>\n
Edit ‘$AGENT_BASE\/agent_inst\/sysman\/config\/emd.properties’<\/strong> and increase the memory allocated to 512M<\/strong> (a good and enough value).<\/p>\n
Before:<\/p>\n
[emc12@localhost config]$ cat emd.properties | grep agentJavaDefines\r\nagentJavaDefines=-Xmx128M -XX:MaxPermSize=96M<\/pre>\n
After edited:<\/p>\n
[emc12@localhost config]$ cat emd.properties | grep agentJavaDefines\r\nagentJavaDefines=-Xmx512M -XX:MaxPermSize=96M<\/pre>\n
Finally,\u00a0try to restart agent running “emctl start agent<\/strong>“:<\/p>\n
[emc12@localhost ~]$ emctl start agent\r\nOracle Enterprise Manager Cloud Control 12c Release 5\r\nCopyright (c) 1996, 2015 Oracle Corporation.  All rights reserved.\r\nStarting agent ..................... started.<\/pre>\n
Great, agent is back to life. However, if you still face any issues, you will need to clear the agent state and retry.<\/p>\n
Do the following:<\/p>\n
    \n
  1. Stop and kill any remaining process related to EM Agent that is still running (perl or java).<\/li>\n
  2. Clean all\u00a0files from ‘$AGENT_BASE\/agent_inst\/sysman\/emd\/state\/*<\/strong>‘ folder (or move them to a temporary place).<\/li>\n
  3. Clear agent state by running:\u00a0emctl clearstate agent<\/strong>.<\/li>\n
  4. Increase the\u00a0memory allocated editing emd.properties<\/strong>, as showed before, if not already done.<\/li>\n
  5. Try to start the agent again.<\/li>\n<\/ol>\n
     <\/p>\n
    More information can be found at\u00a0the MOS Doc ID\u00a0below:<\/p>\n