Get the App
SLTechnology News&Howtos  ›  Database  › 

OMC cloud agent often stops after installation

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

Use the customer's test account to do an OMC cloud agent test, the agent is also installed, and the logs are automatically collected.

The next day, I found that agent was out of service, so I started it, the state was normal, and I found it stopped again in the afternoon.

There seems to be a problem:

View the log file under the path / home/oracle/omcagent/cloudagent/agent_inst/sysman/log/

[oracle@orcl1 log] $tail-n 50 gcagent.log

At oracle.sysman.gcagent.target.rowsource.Rowsource._fetch (Rowsource.java:210)

At oracle.sysman.gcagent.target.rowsource.ProjectionRowSource._fetch_internal (ProjectionRowSource.java:253)

At oracle.sysman.gcagent.target.rowsource.Rowsource._fetch (Rowsource.java:210)

At oracle.sysman.gcagent.target.rowsource.FilterRowSource._fetch_internal (FilterRowSource.java:97)

At oracle.sysman.gcagent.target.rowsource.Rowsource._fetch (Rowsource.java:210)

At oracle.sysman.gcagent.target.rowsource.ColumnRemap._fetch_internal (ColumnRemap.java:67)

At oracle.sysman.gcagent.target.rowsource.Rowsource._fetch (Rowsource.java:210)

At oracle.sysman.gcagent.target.rowsource.Rowsource.fetch (Rowsource.java:222)

At oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.executeRSTree (ExecuteTask.java:2916)

At oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.executeExecutionDescriptor (ExecuteTask.java:2047)

At oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.runTask (ExecuteTask.java:3225)

At oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.call (ExecuteTask.java:4541)

At oracle.sysman.gcagent.metadata.impl.collection.MetricColl$1.call (MetricColl.java:551)

At oracle.sysman.gcagent.metadata.impl.collection.MetricColl$1.call (MetricColl.java:512)

At oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.accountedCall (TaskFutureImpl.java:612)

At oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.call (TaskFutureImpl.java:656)

At java.util.concurrent.FutureTask.run (FutureTask.java:262)

2017-12-2009 ERROR-agent main threw an error [1:main (@ 2017-12-20 09:38:32 CST)] 08491

Java.lang.OutOfMemoryError: Java heap space

At java.nio.HeapByteBuffer. (HeapByteBuffer.java:57)

At java.nio.ByteBuffer.allocate (ByteBuffer.java:331)

At sun.nio.cs.StreamEncoder. (StreamEncoder.java:195)

At sun.nio.cs.StreamEncoder. (StreamEncoder.java:175)

At sun.nio.cs.StreamEncoder.forOutputStreamWriter (StreamEncoder.java:68)

At java.io.OutputStreamWriter. (OutputStreamWriter.java:133)

At oracle.sysman.gcagent.common.FileUtils.createWriter (FileUtils.java:1388)

At oracle.sysman.gcagent.common.FileUtils.setContents (FileUtils.java:221)

At oracle.sysman.gcagent.common.FileUtils.setContents (FileUtils.java:137)

At oracle.sysman.gcagent.common.FileUtils.setContents (FileUtils.java:114)

At oracle.sysman.gcagent.common.FileUtils.overwriteContents (FileUtils.java:93)

At oracle.sysman.gcagent.tmmain.AgentStatus.writeStatusMessage (AgentStatus.java:132)

At oracle.sysman.gcagent.tmmain.TMMain.writeCurrentStatus (TMMain.java:844)

At oracle.sysman.gcagent.tmmain.TMMain.waitForSignal (TMMain.java:878)

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

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

2017-12-20 09 ERROR-Lama:orcl1.jxut.edu.cn:3872:Response:Response 46 ERROR 32 125 [36:GC.SysExecutor.0 (Lama:orcl1.jxut.edu.cn:3872:Response) (Lama:orcl1.jxut.edu.cn:3872:Response:Response)]

Java.lang.OutOfMemoryError: Java heap space

2017-12-20 09 FloodControlCounter 46 INFO 32125 [123:B8A53FBA:GC.SysExecutor.3 (Lama:orcl1.jxut.edu.cn:3872:HT_Memory)] INFO-Handling OOME (FloodControlCounter [count=1, duration=300000, maxInDuration=0, timestamp=1513734391345], 6291195)

2017-12-20 09 agent status is being changed to EXITING 46 123:B8A53FBA 47 852

2017-12-20 09 Agent exiting with exit code 46 123:B8A53FBA 48 532 [123:B8A53FBA] Agent exiting with exit code 57

2017-12-20 09 omc_oracle_db:jxut01_12c:15SecCollection:RDB_MonSvcActiveSessionSample 47 114:6EA1EA8F:GC.Executor.5 02328 [114:6EA1EA8F:GC.Executor.5 (omc_oracle_db:jxut01_12c:15SecCollection) (omc_oracle_db:jxut01_12c:15SecCollection:RDB_MonSvcActiveSessionSample)] INFO-Cancelled task omc_oracle_db:jxut01_12c:15SecCollection:RDB_MonSvcActiveSessionSample due to [oracle.sysman.gcagent.task.TaskTimeoutException: task timeout: 30000 MILLISECONDS for omc_oracle_db:jxut01_12c:15SecCollection]

2017-12-20 09Partition 47VO6706 [23:5BB01D54:Thread-7] INFO-* jetty*: Stopped regularConnector@36895c35 {SSL-HTTP/1.1} {0.0.0.03872}

2017-12-20 09 jetty*: Stopped o.e.j.s.h.ContextHandler@5c974df9 47 23:5BB01D54 [23:5BB01D54] INFO-* jetty*: Stopped o.e.j.s.h.ContextHandler@5c974df9 {/, null,UNAVAILABLE}

2017-12-20 09 jetty*: Stopped o.e.j.s.h.ContextHandler@3ea75851 47 jetty*: Stopped o.e.j.s.h.ContextHandler@3ea75851 07487 [23:5BB01D54] jetty*: Stopped o.e.j.s.h.ContextHandler@3ea75851 {/ emd/persistence/main,null,UNAVAILABLE}

2017-12-20 09 jetty*: Stopped o.e.j.s.ServletContextHandler@418db5fe 47 jetty*: Stopped o.e.j.s.ServletContextHandler@418db5fe 11258 [23:5BB01D54] jetty*: Stopped o.e.j.s.ServletContextHandler@418db5fe {/ emd/daemon,null,UNAVAILABLE}

2017-12-20 09 jetty*: Stopped o.e.j.s.ServletContextHandler@333b8e45 47 jetty*: Stopped o.e.j.s.ServletContextHandler@333b8e45 12032 [23:5BB01D54] jetty*: Stopped o.e.j.s.ServletContextHandler@333b8e45 {/ emd/gateway,null,UNAVAILABLE}

2017-12-20 09 jetty*: Stopped o.e.j.s.ServletContextHandler@491b58d6 47 jetty*: Stopped o.e.j.s.ServletContextHandler@491b58d6 12032 [23:5BB01D54] jetty*: Stopped o.e.j.s.ServletContextHandler@491b58d6 {/ emd/browser,null,UNAVAILABLE}

2017-12-20 09 jetty*: Stopped o.e.j.s.ServletContextHandler@401a5c05 47 jetty*: Stopped o.e.j.s.ServletContextHandler@401a5c05 12033 [23:5BB01D54] jetty*: Stopped o.e.j.s.ServletContextHandler@401a5c05 {/ emd/receiver,null,UNAVAILABLE}

2017-12-20 09 jetty*: Stopped o.e.j.s.h.ContextHandler@2de48d50 47 jetty*: Stopped o.e.j.s.h.ContextHandler@2de48d50 12805 [23:5BB01D54] jetty*: Stopped o.e.j.s.h.ContextHandler@2de48d50 {/ emd/main,null,UNAVAILABLE}

2017-12-20 09 jetty*: Stopped o.e.j.s.h.ContextHandler@407a8d92 47 jetty*: Stopped o.e.j.s.h.ContextHandler@407a8d92 12805 [23:5BB01D54] jetty*: Stopped o.e.j.s.h.ContextHandler@407a8d92 {/ emd/lifecycle/main,null,UNAVAILABLE}

At first glance, the java virtual machine does not have enough memory. Take a look at metalink and find the same problem:

OMC: Oracle Management Cloud Agent Crashes after Upgrade to Version 1.21.0 (document ID 2322444.1)

[oracle@orcl1 config] $cp emd.properties emd.properties.bak

[oracle@orcl1 config] $vi emd.properties

[oracle@orcl1 config] $pwd

/ home/oracle/omcagent/cloudagent/agent_inst/sysman/config

[oracle@orcl1 config] $cat emd.properties | grep Xmx

AgentJavaDefines=-Xmx1024M-XX:MaxPermSize=512M

Restart after modification:

[oracle@orcl1 bin] $. / omcli start agent

Oracle Management Cloud Agent

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

Starting agent. Started.

[oracle@orcl1 bin] $. / omcli status agent

Oracle Management Cloud Agent

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

Version: 1.24.0

State Home: / home/oracle/omcagent/cloudagent/agent_inst

Log Directory: / home/oracle/omcagent/cloudagent/agent_inst/sysman/log

Binaries Location: / home/oracle/omcagent/cloudagent/LAMA_LINUX.X64_171117.1500/core/1.24.0

Process ID: 88144

Parent Process ID: 87986

URL: https://orcl1.jxut.edu.cn:3872/emd/main/

Started at: 2017-12-20 21:14:31

Started by user: oracle

Operating System: Linux version 2.6.39-400.245.1.el5uek (amd64)

Data Collector enabled: false

Sender Status: FUNCTIONAL

Gateway Upload Status: FUNCTIONAL

Last successful upload: 2017-12-20 21:15:15

Last attempted upload: 2017-12-20 21:15:11

Pending Files (MB): 0.02

Pending Files: 49

Backoff Expiration: (none)

Agent is Running and Ready

[oracle@orcl1 bin] $

At present, the state is normal, look at it tomorrow, if it is still running, the problem will be solved!

Tags: Problem status test insufficient memory customer file document log account path two days installed service run Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno macOS MariaDB Redmi Huawei Apple