EM 13.2 Agent on IBM AIX - Agent is Unreachable (REASON = unable to connect to http server at https://hostname:port/emd/main/. [handshake has no peer]) but the host is reachable.
(Doc ID 2566311.1)
Last updated on JANUARY 17, 2023
Applies to:
Enterprise Manager Base Platform - Version 13.2.0.0.0 and laterIBM AIX on POWER Systems (64-bit)
Symptoms
Receiving the following unreachable alerts for 13.2 Agent running on AIX and gets cleared in few mins:
emctl commands from agent home throws the below error:
oracle@<hostname>:<AGENT_INST>/bin> ./emctl upload agent
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Status agent Failure:unable to connect to http server at https://<hostname>:<port>/emd/lifecycle/main/. [handshake has no peer]
oracle@<hostname>:<AGENT_INST>/bin> ./emctl pingOMS
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD pingOMS error: unable to connect to http server at https://<hostname>:<port>/emd/main/. [handshake has no peer]
Observed the following errors in emagent.nohup:
----- 2019-06-22 06:04:29,872::27984462::Checking status of EMAgent : 51183956 -----
---- 2019-06-22 06:04:29,872::27984462::Hang detected for EMAgent : 51183956 -----
----- 2019-06-22 06:04:29,872::27984462::Debugging component EMAgent -----
----- 2019-06-22 06:04:29,873::generate first thread dump file for diagnosis -----
JVMDUMP039I Processing dump event "user", detail "" at 2019/06/22 06:04:49 - please wait.
JVMDUMP032I JVM requested Java dump using '<AGENT_INST>/sysman/emd/javacore.20190401.222749.51183956.0001.txt' in response to an event
JVMDUMP010I Java dump written to <AGENT_INST>/sysman/emd/javacore.20190401.222749.51183956.0001.txt
JVMDUMP013I Processed dump event "user", detail "".
----- 2019-06-22 06:04:59,929::generate second thread dump file for diagnosis -----
JVMDUMP039I Processing dump event "user", detail "" at 2019/06/22 06:04:59 - please wait.
JVMDUMP032I JVM requested Java dump using '<AGENT_INST>/sysman/emd/javacore.20190401.222759.51183956.0002.txt' in response to an event
----- 2019-06-22 06:04:59,985::generate Threads.51183956lsof.1 for diagnosis -----
----- Attempting to kill EMAgent : 51183956 -----
----- 2019-06-22 06:05:05,208::27984462::EMAgent exited at 2019-06-22 06:05:05,207 with signal 9 -----
----- 2019-06-22 06:05:05,208::27984462::EMAgent either hung or in abnormal state. -----
----- 2019-06-22 06:05:05,208::27984462::EMAgent will be restarted/thrashed. -----
----- 2019-06-22 06:05:05,208::27984462::writeAbnormalExitTimestampToAgntStmp: exitCause=ABNORMAL : restartRequired=1 -----
----- 2019-06-22 06:05:05,209::27984462::Restarting EMAgent. -----
Changes
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 |
Changes |
Cause |
Solution |
References |