My Oracle Support Banner

OEM13cR5: Agent Is Not Starting On Exadata Node After DomU Patching (Doc ID 3073532.1)

Last updated on MARCH 13, 2025

Applies to:

Enterprise Manager Base Platform - Version 13.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

OEM: 13cR5

In Oracle Enterprise Manager Cloud Control, Agent is unable to start post patching of DomU on Exadata node level. Even though the OMS to Agent port communication and vice-versa working agent is unable to start.

$ ./emctl start agent
Oracle Enterprise Manager Cloud Control 13c Release 5
Copyright (c) 1996, 2021 Oracle Corporation. All rights reserved.
Starting agent .......................................... failed.
HTTP Listener failed at Startup
Possible port conflict on port(3872): Retrying the operation.....
Failed to start the agent after 3 attempts. Please check that the port(3872) is available.
Consult emctl.log and emagent.nohup in: /u02/app/oracle/agent/agent_inst/sysman/log

 Communication Checks:

From OMS:

ping <agent-hostname>
telnet <agent-hostname> <agent-port>
nslookup <agent-hostname>
cat /etc/hosts | grep -i <agent-hostname>
openssl s_client -connect <agent-hostname>:<agent-port>

From Target Agent:

ping <oms/slb hostname>
telnet <oms/slb hostname> <oms/slb https upload port>
nslookup <oms/slb hostname>
cat /etc/hosts | grep -i <oms/slb hostname>
openssl s_client -connect <oms/slb hostname>:<oms/slb upload port>

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.