Get the App
SLTechnology News&Howtos  ›  Database  › 

FATAL-Fatal error: Target Interaction Manager failed at Startup

Shulou Source: shulou.com Published: 2022-06-01 05:42:47 10月04日 Update

. / emctl start agent

Oracle Enterprise Manager Cloud Control 12c Release 5

Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.

Starting agent... Failed.

Fatal agent error: State Manager failed at Startup

Fatal agent error: Target Interaction Manager failed at Startup

Fatal agent error: Target Interaction Manager failed at Startup

EMAgent is Thrashing. Exiting watchdog

Consult emctl.log and emagent.nohup in: / tmpdata/agent12c/agent_inst/sysman/log

You have new mail in / var/spool/mail/oracle

[oracle@dm01dbadm01 bin] $. / emctl status agent

Oracle Enterprise Manager Cloud Control 12c Release 5

Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.

Agent is Not Running

You have new mail in / var/spool/mail/oracle

Tail-100 emctl.log

78313:: Tue Jun 12 09:54:24 2018::AgentLifeCycle.pm: Check agent status retCode=1

78313:: Tue Jun 12 09:54:24 2018::TZ:Asia/Shanghai EmctlLogAvailabilityMarker Operation=start Diag=failed

78313:: Tue Jun 12 09:54:24 2018::Calling releaselobalLock

78313:: Tue Jun 12 09:54:24 2018::AgentCommandLock:released lock on emctl lockfile

78313:: Tue Jun 12 09:54:24 2018::Released agent command lock

78313:: Tue Jun 12 09:54:24 2018::Cleaning up agent command lock

78313:: Tue Jun 12 09:54:24 2018::AgentCommandLock:closed file handle of emctl lockfile

88516:: Tue Jun 12 09:56:52 2018::Initializing the agent command locking system

88516:: Tue Jun 12 09:56:53 2018::AgentLifeCycle.pm: Processing status agent

88516:: Tue Jun 12 09:56:53 2018::AgentStatus.pm:Processing status agent

88516:: Tue Jun 12 09:56:53 2018::AgentStatus.pm:emdctl status returned 1

88516:: Tue Jun 12 09:56:53 2018::Cleaning up agent command lock

88516:: Tue Jun 12 09:56:53 2018::AgentCommandLock:closed file handle of emctl lockfi

Tail-100 emagent.nohup

-Tue Jun 12 09:51:50 2018::70850::Checking status of EMAgent: 72466-

-Tue Jun 12 09:51:50 2018::70850::EMAgent exited at Tue Jun 12 09:51:50 2018 with return value 57. -

-Tue Jun 12 09:51:50 2018::70850::EMAgent will be restarted because of an Out of Memory Exception. -

-Tue Jun 12 09:51:50 2018::70850::writeAbnormalExitTimestampToAgntStmp: exitCause=OOM: restartRequired=1-

-Tue Jun 12 09:51:50 2018::70850::Restarting EMAgent. -

-Tue Jun 12 09:51:50 2018::70850::Auto tuning the agent at time Tue Jun 12 09:51:50 2018-

InMemoryLoggingSize=7340032

_ SchedulePersistTimer=30

MaxThreads=10

AgentJavaDefines=-Xmx430M-XX:MaxPermSize=96M

SchedulerRandomSpreadMins=5

UploadMaxNumberXML=5000

UploadMaxMegaBytesXML=50.0

Auto tuning was successful

-Tue Jun 12 09:51:53 2018::70850::Finished auto tuning the agent at time Tue Jun 12 09:51:53 2018-

-Tue Jun 12 09:51:53 2018::70850::Launching the JVM with following options:-Xmx430M-XX:MaxPermSize=96M-server-Djava.security.egd= file:///dev/./urandom-Dsun.lang.ClassLoader.allowArraySyntax=true-XX:+UseLinuxPosixThreadCPUClocks-XX:+UseConcMarkSweepGC-XX:+CMSClassUnloadingEnabled-XX:+UseCompressedOops-

-Tue Jun 12 09:51:53 2018::70850::Agent Launched with PID 73593 at time Tue Jun 12 09:51:53 2018-

-Tue Jun 12 09:51:53 2018::73593::Time elapsed between Launch of Watchdog process and execing EMAgent is 30 secs-

2018-06-1209 Missing filename for log handler 5114092 [1:main] WARN-Missing filename for log handler 'wsm'

2018-06-1209 Missing filename for log handler 51100 [1:main] WARN-Missing filename for log handler 'opss'

2018-06-1209 Missing filename for log handler 51lav 54101 [1:main] WARN-Missing filename for log handler 'opsscfg'

Agent is going down due to an OutOfMemoryError

-Tue Jun 12 09:52:03 2018::70850::Checking status of EMAgent: 73593-

-Tue Jun 12 09:52:03 2018::70850::EMAgent exited at Tue Jun 12 09:52:03 2018 with return value 57. -

-Tue Jun 12 09:52:03 2018::70850::EMAgent will be restarted because of an Out of Memory Exception. -

-Tue Jun 12 09:52:03 2018::70850::EMAgent is Thrashing. Exiting loop. -

-Tue Jun 12 09:52:03 2018::70850::Commiting Process death. -

-Tue Jun 12 09:52:03 2018::70850::writeAbnormalExitTimestampToAgntStmp: exitCause=OOM: restartRequired=0-

-Tue Jun 12 09:52:03 2018::70850::Exited due to Thrash. -

-EMState agent

-Tue Jun 12 09:53:25 2018::78478::Mismatch detected between timezone in env (Asia/Shanghai) and in / tmpdata/agent12c/agent_inst/sysman/config/emd.properties (Asia/Chungking). Forcing value to latter.. -

Tail-100 gcagent.log

2018-06-1209 including periodShift of 54 including periodShift of 12800 [45:CBCC52CF:GC.SysExecutor.1 (HeapMonitorTask)] DEBUG-Scheduling next HeapMonitorTask after delay 4999 including periodShift of 0 milliseconds

2018-06-1209 DEBUG-End task HeapMonitorTask

2018-06-12 09 Fatal error 54 Target Interaction Manager failed at Startup [1:main] Target Interaction Manager failed at Startup

Java.lang.OutOfMemoryError: Java heap space

At java.util.Arrays.copyOf (Arrays.java:2882)

At java.lang.AbstractStringBuilder.expandCapacity (AbstractStringBuilder.java:100)

At java.lang.AbstractStringBuilder.append (AbstractStringBuilder.java:390)

At java.lang.StringBuffer.append (StringBuffer.java:224)

At oracle.sysman.gcagent.target.interaction.execution.Threshold.mergeState (Threshold.java:2447)

At oracle.sysman.gcagent.target.interaction.execution.Threshold.restoreThresholdState (Threshold.java:1937)

At oracle.sysman.gcagent.target.interaction.execution.Threshold.initThreshold (Threshold.java:4273)

At oracle.sysman.gcagent.target.interaction.execution.TargetInteractionMgr.init (TargetInteractionMgr.java:225)

At oracle.sysman.gcagent.target.interaction.execution.TargetInteractionMgr.tmNotifier (TargetInteractionMgr.java:171)

At oracle.sysman.gcagent.tmmain.lifecycle.TMComponentSvc.invokeNotifier (TMComponentSvc.java:1009)

At oracle.sysman.gcagent.tmmain.lifecycle.TMComponentSvc.invokeInitializationStep (TMComponentSvc.java:1094)

At oracle.sysman.gcagent.tmmain.lifecycle.TMComponentSvc.doInitializationStep (TMComponentSvc.java:927)

At oracle.sysman.gcagent.tmmain.lifecycle.TMComponentSvc.notifierDriver (TMComponentSvc.java:823)

At oracle.sysman.gcagent.tmmain.TMMain.startup (TMMain.java:264)

At oracle.sysman.gcagent.tmmain.TMMain.agentMain (TMMain.java:565)

At oracle.sysman.gcagent.tmmain.TMMain.main (TMMain.java:554)

2018-06-12 09 notifierMain 54 Done initialization State=STARTUP_P1 14 812 [1:3305B9] Done initialization State=STARTUP_P1

Pwd

/ tmpdata/agent12c/agent_inst/sysman/config

[oracle@dm01dbadm01 config] $more emd.properties

AgentJavaDefines=-Xmx572M-XX:MaxPermSize=96M

Modify to

AgentJavaDefines=-Xmx1024M-XX:MaxPermSize=96M

. / emctl start agent

Oracle Enterprise Manager Cloud Control 12c Release 5

Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.

Starting agent. Started.

Tags: Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Xiaomi Microsoft Shulou Information Apple Shulou Technology