OCI Management Agent Service : Gateway Agent Stop Working Suddenly and Fails To Start
(Doc ID 2986588.1)
Last updated on NOVEMBER 10, 2023
Applies to:
OCI Management Agent Service - Version N/A to N/AInformation in this document applies to any platform.
Symptoms
The Management Gateway Agent was working fine and suddenly it stopped functioning.
Trying to start the gateway fails with following error:
$systemctl start mgmt_gateway
Job for mgmt_gateway.service failed beause the control process exited with error code.
Job for mgmt_gateway.service failed beause the control process exited with error code.
Error stack observed from /opt/oracle/mgmt_agent/agent_inst/log/mgmt_agent.log file:
2023-10-20 15:40:29,889 [SendQueue.72 (SenderManager_sender)-278230] INFO - Generated AuthenticationException for CommError[Level=DESTINATION,key=401:NotAuthenticated(401),retry=true,backoff=-1,category=AUTHENTICATION,msgTxt=](Date 'Fri, 20 Oct 2023 15:40:29 UTC' is not within allowed clock skew. Current 'Fri, 20 Oct 2023 15:45:30 UTC', valid datetime range: ['Fri, 20 Oct 2023 15:40:30 UTC', 'Fri, 20 Oct 2023 15:50:31 UTC'])
2023-10-20 15:40:29,890 [SendQueue.72 (SenderManager_sender)-278230] WARN - #-# invocation access log [request-id-prefix: 62AP4V66] #-#
Service: OCI
Method: POST
Path: /20180401/metrics
Headers: Content-Type=application/json
date=Fri, 20 Oct 2023 15:40:17 GMT
host=telemetry-ingestion.us-ashburn-1.oraclecloud.com
x-content-sha256=jZpcLJfq2Vz/ByQwlZXew6Yk5bH6SLHojK8udrOkgSI=
Authorization=**********************************************************************************************************************************************************************************************************************
opc-request-id=<opc-request-id>
User-Agent=Jersey/2.34 (Apache HttpClient 4.5.14)
Attempts:
<--> Endpoint: telemetry-ingestion.us-ashburn-1.oraclecloud.com
opc-request-id: <opc-request-id>
StartTime: 2023-10-20 15:40:17,769 GMT
Status: 401 Unauthorized
Headers: Content-Length=240
opc-request-id=<opc-request-id>/90BCC9A971A02B9B2B1B82F846E49A26/459874C8FF6FB1DA91C07BB5C9D13CC5
Date=Fri, 20 Oct 2023 15:45:29 GMT
Content-Type=application/json
ErrorBody: {"code":"NotAuthenticated","message":"Date 'Fri, 20 Oct 2023 15:40:17 UTC' is not within allowed clock skew. Current 'Fri, 20 Oct 2023 15:45:29 UTC', valid datetime range: ['Fri, 20 Oct 2023 15:40:29 UTC', 'Fri, 20 Oct 2023 15:50:30 UTC']"}
EndTime: 2023-10-20 15:40:28,520 GMT
2023-10-20 15:40:29,890 [SendQueue.72 (SenderManager_sender)-278230] WARN - #-# invocation access log [request-id-prefix: 62AP4V66] #-#
Service: OCI
Method: POST
Path: /20180401/metrics
Headers: Content-Type=application/json
date=Fri, 20 Oct 2023 15:40:17 GMT
host=telemetry-ingestion.us-ashburn-1.oraclecloud.com
x-content-sha256=jZpcLJfq2Vz/ByQwlZXew6Yk5bH6SLHojK8udrOkgSI=
Authorization=**********************************************************************************************************************************************************************************************************************
opc-request-id=<opc-request-id>
User-Agent=Jersey/2.34 (Apache HttpClient 4.5.14)
Attempts:
<--> Endpoint: telemetry-ingestion.us-ashburn-1.oraclecloud.com
opc-request-id: <opc-request-id>
StartTime: 2023-10-20 15:40:17,769 GMT
Status: 401 Unauthorized
Headers: Content-Length=240
opc-request-id=<opc-request-id>/90BCC9A971A02B9B2B1B82F846E49A26/459874C8FF6FB1DA91C07BB5C9D13CC5
Date=Fri, 20 Oct 2023 15:45:29 GMT
Content-Type=application/json
ErrorBody: {"code":"NotAuthenticated","message":"Date 'Fri, 20 Oct 2023 15:40:17 UTC' is not within allowed clock skew. Current 'Fri, 20 Oct 2023 15:45:29 UTC', valid datetime range: ['Fri, 20 Oct 2023 15:40:29 UTC', 'Fri, 20 Oct 2023 15:50:30 UTC']"}
EndTime: 2023-10-20 15:40:28,520 GMT
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 |