Grid Control Agent Startup Fails with KEY_MISMATCH and Agent is Already Running
(Doc ID 961773.1)
Last updated on JULY 07, 2023
Applies to:
Enterprise Manager Base Platform - Version 10.2.0.5 to 11.1.0.1 [Release 10.2 to 11.1]Information in this document applies to any platform.
Symptoms
Agent does not start. The start command output shows that the Agent is already running. The 'ps' command does not show Agent processes running on the server.
The log files show the following errors:
- From Agent log file <AGENT_HOME>/sysman/log/emagent.trc, the following errors appears:
2009-10-23 11:27:12,734 Thread-4026870688 ERROR pingManager: Received Key Mismatch from OMS
2009-10-23 11:27:12,831 Thread-4026870688 ERROR pingManager: Received Key Mismatch from OMS
2009-10-23 11:27:42,933 Thread-4026870688 ERROR pingManager: Received Key Mismatch from OMS
2009-10-23 11:27:43,028 Thread-4026870688 ERROR pingManager: Received Key Mismatch from OMS
- From OMS log files there are several KEY_MISMATCH errors from a different hostname. The <oms home>/sysman/log/emoms.log shows the following errors
2009-10-23 11:22:19,465 [AJPRequestHandler-ApplicationServerThread-15] ERROR eml.OMSHandshake processFailure.843 - OMSHandshake failed.(AGENT URL = https://<agenthost2.<DOMAIN_NAME>>:3872/emd/main/)(ERROR = KEY_MISMATCH)
2009-10-23 11:22:49,567 [AJPRequestHandler-ApplicationServerThread-9] ERROR eml.OMSHandshake processFailure.843 - OMSHandshake failed.(AGENT URL = https://agenthost2.<DOMAIN_NAME>:3872/emd/main/)(ERROR = KEY_MISMATCH)
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 |