Agent Upload to OMS Fails if OMS Locked in Secure,Agent isn't Secured_422922.1
Agent Upload to OMS Fails if the OMS is Locked in Secure Mode and Agent is not Secured (Doc ID 422922.1)
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |
Applies to:
Enterprise Manager Base Platform - Version 10.1.0.2 to 10.2.0.5 [Release 10.1 to 10.2]
Information in this document applies to any platform.
***Checked for relevance on 05-Oct-2011***
Checked for relevance on 26-Jun-2013
Symptoms
Agent upload to OMS is failing. The 'emctl upload' command returns:
OR
EMD upload error: Failed to upload file A*.xml: HTTP error.
The
2010-04-29 11:44:54,195 Thread-121416624 WARN http: nmehl_connect_internal: connect failed to (omsmachine.domain:4889): Connection refused (error = 111)
2010-04-29 11:44:54,195 Thread-121416624 ERROR upload: FxferSend: Cannot connect to: http://omsmachine.domain:4889/em/upload/. retStatus=-1
The Agent is trying to access ' http://omsmachine.domain:4889/em/upload/' URL and gets a 'Connection refused' error.
The
http://agentmachine.domain:3872/emd/main/)(ERROR = X-ORCL-EMAK MISSING)
In the 10.2.0.5 OMS versions, there is no error in the emoms.trc file. But the
The error code '403' indicates that the access to the '/em/upload' is forbidden.
Trying to access the OMS unsecure upload url: http://omsmachine.domain:4889/em/upload
from a browser also returns:
You don't have permission to access /em/upload on this server.
--------------------------------------------------------------------------------
Oracle-Application-Server-10g/10.1.2.2.0 Oracle-HTTP-Server Server at omsmachine.domain Port 4889
Changes
OMS has been recently locked for secure upload mode.
Cause
The OMS is locked in secure mode, hence is accepting uploads only from Agents which are secured with the OMS and sending the uploads to the https upload URL.
If any Agent tries to upload to the http URL, the connection will be rejected.
Solution
1. Ensure that the REPOSITORY_URL configured in the
Refer Note 737373.1: Communication: Agent to OMS Communication Fails if the Agent's REPOSITORY_URL Parameter has Incorrect Value
2. If the OMS is secured and locked (accepts uploads only in the https mode), then secure the Agent also.
Refer:
Note 428874.1: How to tell if the EM OMS is locked or unlocked?
Note 283091.1: How To Secure / Unsecure The Grid Control Components (Agent / OMS) In 10g
emctl secure agent
This will prompt you for the Agent Registration password, which is needed for secure operation to complete.
If the Agent Registration password is not known, create a new one using the steps in
Note 285490.1: Grid Control Security: How to Create / Edit the Agent Registration Password for Agent to OMS Secure Communication?
References
NOTE:283091.1 - How to Secure the OMS and Agent Components in a 10g Grid Control Setup?
NOTE:285490.1 - Grid Control Security: How to Create / Edit the Agent Registration Password for Agent to OMS Secure Communication?
NOTE:428874.1 - How To Verify if the Enterprise Manager Grid Control (OMS) is Locked or Unlocked?
NOTE:737373.1 - Communication: Agent to OMS Communication Fails if the Agent's REPOSITORY_URL Parameter has Incorrect Value
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/17252115/viewspace-1247793/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 11g Agent Upload Fails with "OMS version not checked Yet". (Doc ID 1265052.1)AI
- Agent to OMS Communi Fails if Agent is 'Blocked' in 10.2.0.5 Grid Cons_799618.1AIBloC996
- Agent to OMS Communi Fails if Agent's REPOSITORY_URL Para has Incorrect_737373.1AI
- windows下部署12c oms agent 及清除agentWindows
- OMS to Agent Comm Fails if IP Address of the Grid Ag Machine is Changed-605009.1AIMac
- EM 12c推送Agent出錯 - OMS_HOST and EM_UPLOAD_PORT is not availableAI
- Install GC Agent 11.1.0.1 fails at Config Agent File secure.log_1273470.1GCAI
- GC 11.1 Install fails at Agent CA while Securing Agent in secure.log_1118270.1GCAIWhile
- 【GC】重新配置Agent以應對 OMS伺服器的變化GC伺服器
- GC 10.2.0.1 OMS和Agent連線失敗後的處理過程GC
- EM 12c Cloud Control - Agent Unreachable : Received Key Mismatch from OMS - 3Cloud
- EM 12c Cloud Control - Agent Unreachable : Received Key Mismatch from OMS - 2Cloud
- EM 12c Cloud Control - Agent Unreachable : Received Key Mismatch from OMS - 1Cloud
- To Verify if the Enterprise Manager GC (OMS) is Locked or Unlocked_428874.1GC
- Agent Startup Fails When the Repository DB Does Not Support TZ of Agent-332131.1AI
- 配置OMS筆記筆記
- Grid Control服務端看不到Agent相關資訊,同時OMS狀態為unknown處理服務端
- OMS平臺介紹
- OMS Startup Fails during Repository Connection Attempt due to_310772.1AI
- OMS CA:10.2.0.1.0 GC Install Fails with "Error processing emkey-353131.1GCAIError
- Automatic Start GC Agent 10.2.0.5 via gcstartup Script fails with sudo_789363.1GCAI
- (oracle Agent出現以下錯誤) Emd upload error:uploadXMLFiles skipp...OracleErrorXML
- EM GC11.1.0.1 Agent Startup on AIX Fails with Error: nmectl_validate_1386861.1GCAIError
- Java Agent(上)Java
- 智慧體Agent智慧體
- Agent Install Fails with Error 'OUI-25031' Due to Environment Settings_380507.1AIErrorUI
- Problem: 10.2 Agent Install On Rac Fails With 'Exceptionmessage=Prkc-1002'AIException
- sysman.emcp.agent.AgentPlugIn raised by the Agent CA-740628.1PluginAI
- GC 11g install fails at OMS config stage-Wrong WLS version used_1135493.1GCAI
- GC Agent Startup Fails on AIX due to Invalid Timezone Setting at OS_825933.1GCAI
- zabbix安裝agent
- 資料庫agent資料庫
- java agent簡介Java
- Zabbix Agent安裝
- gc/Agent passwd resetGC
- SSH Agent 的作用
- Oracle9i的OMS使用方法Oracle
- Java 安全之Java AgentJava