OMC : Cloud Agent Core Dumping And Restarting With Synthetic Tests Added
(Doc ID 2701538.1)
Last updated on MAY 24, 2023
Applies to:
Oracle Management Cloud - Version N/A to N/A [Release 1.0]Information in this document applies to any platform.
Symptoms
Oracle Management Cloud (OMC), Agent is restarting and dumping Cores when more Synthetic Tests added.
Error Stack from <Agent_Inst>/sysman/log/emagent.nohup file:
WARN - Missing filename for log handler 'opsscfg'
# A fatal error has been detected by the Java Runtime Environment:
# SIGBUS (0x7) at pc=0x00007f10531d3d10, pid=104434, tid=0x00007f0ff019e700
# JRE version: Java(TM) SE Runtime Environment (8.0_251-b08) (build 1.8.0_251-b08)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.251-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libzip.so+0x11d10] newEntry.isra.4+0x60
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
# An error report file with more information is saved as: <Agent_Inst>/sysman/emd/hs_err_pid104434.log
# If you would like to submit a bug report, please visit: http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
----- 2020-07-21 13:39:05,350::102284::Checking status of EMAgent : 104434 -----
----- 2020-07-21 13:39:05,350::102284::EMAgent exited at 2020-07-21 13:39:05,350 with signal 6 -----
----- 2020-07-21 13:39:05,350::102284::EMAgent has exited due to an internal error -----
----- 2020-07-21 13:39:05,350::102284:: - checking for corefile at <Agent_Inst>/sysman/emd -----
----- 2020-07-21 13:39:05,350::102284::EMAgent will be restarted due to core dump(via signal 6). -----
----- 2020-07-21 13:39:05,350::102284::writeAbnormalExitTimestampToAgntStmp: exitCause=ABNORMAL : restartRequired=1 -----
----- 2020-07-21 13:39:05,350::102284::Restarting EMAgent. -----
# A fatal error has been detected by the Java Runtime Environment:
# SIGBUS (0x7) at pc=0x00007f10531d3d10, pid=104434, tid=0x00007f0ff019e700
# JRE version: Java(TM) SE Runtime Environment (8.0_251-b08) (build 1.8.0_251-b08)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.251-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libzip.so+0x11d10] newEntry.isra.4+0x60
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
# An error report file with more information is saved as: <Agent_Inst>/sysman/emd/hs_err_pid104434.log
# If you would like to submit a bug report, please visit: http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
----- 2020-07-21 13:39:05,350::102284::Checking status of EMAgent : 104434 -----
----- 2020-07-21 13:39:05,350::102284::EMAgent exited at 2020-07-21 13:39:05,350 with signal 6 -----
----- 2020-07-21 13:39:05,350::102284::EMAgent has exited due to an internal error -----
----- 2020-07-21 13:39:05,350::102284:: - checking for corefile at <Agent_Inst>/sysman/emd -----
----- 2020-07-21 13:39:05,350::102284::EMAgent will be restarted due to core dump(via signal 6). -----
----- 2020-07-21 13:39:05,350::102284::writeAbnormalExitTimestampToAgntStmp: exitCause=ABNORMAL : restartRequired=1 -----
----- 2020-07-21 13:39:05,350::102284::Restarting EMAgent. -----
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |