Verifique o processo escutando na porta 3872:
# netstat -tlnpn | grep 3872 tcp 0 0 0.0.0.0:3872 0.0.0.0:* LISTEN 163311/java
Então identifique o caminho do processo na saída do comando ps:
# ps -ef | grep 163311 oracle 117309 163311 0 19:29 ? 00:00:00 /u02/app/oracle/agent/agent_13.4.0.0.0/perl/bin/perl /u02/app/oracle/agent/agent_13.4.0.0.0/plugins/oracle.sysman.db.agent.plugin_13.4.1.0.0/scripts/db/dg/dgDatabases.pl root 117830 108680 0 19:29 pts/0 00:00:00 grep --color=auto 163311 oracle 163311 24654 1 11:26 ? 00:06:51 /u02/app/oracle/agent/agent_13.4.0.0.0/oracle_common/jdk/bin/java -Xmx128M -XX:MaxMetaspaceSize=224M -server -Djava.security.egd=file:///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -XX:-UseLargePages -XX:+UseLinuxPosixThreadCPUClocks -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops -DHTTPClient.dontSeekTerminatingChunk=true -Dwatchdog.pid=24654 -cp /u02/app/oracle/agent/agent_13.4.0.0.0/jdbc/lib/ojdbc7.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/ucp/lib/ucp.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/oracle_common/modules/jsch-0.1.54.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/oracle_common/modules/com.oracle.http_client.http_client.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/oracle_common/modules/oracle.xdk/xmlparserv2.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/oracle_common/modules/oracle.dms/dms.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/oracle_common/modules/oracle.odl/ojdl.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/oracle_common/modules/oracle.odl/ojdl2.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/lib/optic.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/sysman/jlib/log4j-core.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/jlib/gcagent_core.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/sysman/jlib/emagentSDK-intg.jar:/u02/app/oracle/agent/agent_13.4.0.0.0/sysman/jlib/emagentSDK.jar oracle.sysman.gcagent.tmmain.TMMain
Retornou mais de um processo e uma chamada gigante, mas o caminho do agente neste exemplo é:
/u02/app/oracle/agent/agent_13.4.0.0.0/
$ /u02/app/oracle/agent/agent_13.4.0.0.0/bin/emctl status agent Oracle Enterprise Manager Cloud Control 13c Release 4 Copyright (c) 1996, 2020 Oracle Corporation. All rights reserved. --------------------------------------------------------------- Agent Version : 13.4.0.0.0 OMS Version : 13.4.0.0.0 Protocol Version : 12.1.0.1.0 Agent Home : /u02/app/oracle/agent/agent_inst Agent Log Directory : /u02/app/oracle/agent/agent_inst/sysman/log Agent Binaries : /u02/app/oracle/agent/agent_13.4.0.0.0 Core JAR Location : /u02/app/oracle/agent/agent_13.4.0.0.0/jlib Agent Process ID : 163311 Parent Process ID : 24654 Agent URL : https://xyz.oraclecloudatcustomer.com:3872/emd/main/ Local Agent URL in NAT : https://xyz.cloudatcustomer.com:3872/emd/main/ Repository URL : https://xyz.abc.com.br:4903/empbs/upload Started at : 2021-05-24 11:26:33 Started by user : oracle Operating System : Linux version 4.1.12-124.34.1.el7uek.x86_64 (amd64) Number of Targets : 30 Last Reload : (none) Last successful upload : 2021-05-24 19:25:28 Last attempted upload : 2021-05-24 19:25:28 Total Megabytes of XML files uploaded so far : 1.07 Number of XML files pending upload : 0 Size of XML files pending upload(MB) : 0 Available disk space on upload filesystem : 86.30% Collection Status : Collections enabled Heartbeat Status : Ok Last attempted heartbeat to OMS : 2021-05-24 19:29:59 Last successful heartbeat to OMS : 2021-05-24 19:29:59 Next scheduled heartbeat to OMS : 2021-05-24 19:30:59 --------------------------------------------------------------- Agent is Running and Ready
Uma opção que temos aqui para facilitar no dia a dia, é colocar o diretório do EMCC Agent Home no /etc/oratab e usar o oraenv para configuarar as variáveis de ambiente.
Exemplo como ficaria no arquivo:
emagent:/u02/app/oracle/agent/agent_13.4.0.0.0:N
Então podemos usar dessa forma:
. oraenv <<< emagent emctl status agent