Symptoms
Unable to activate 360 Monitoring from Plesk:
CONFIG_TEXT: Failed to install 360 Monitoring, please try again later
Something went wrong. Please try again later. Request ID: Root=1-12345a6b-12ab34c567890d1e23f45g6h.
Cause
On expanding the server infrastructure, the new components temporarily got the primary role before they got updated completely. That led to the inability to activate 360 Monitoring due to half-empty databases.
The issue is fixed and the necessary changes are applied on the 360 Monitoring side in order to avoid it in the future.
Resolution
October 6
12:45 UTC | 8:45 EDT
The cause of the issue is confirmed. It was related to the expansion of the server infrastructure.
11:40 UTC | 7:40 EDT
The issue is fixed.
07:36 UTC | 03:36 EDT
We are receiving reports of issues with the 360 Monitoring activation.
From Plesk:
CONFIG_TEXT: Failed to install 360 Monitoring, please try again later
Something went wrong. Please try again later. Request ID: Root=1-12345a6b-12ab34c567890d1e23f45g6h.
From CLI on a Plesk server:
# plesk ext platform360 --monitoring-setup -p360-key-file /path/to/the/token
ERR [extension/platform360] Server error: POST https://platform360.io/api/v1/monitoring/servers/1a23b45c-1234-1a23-1abc-1a234b56789c/setup resulted in a 500 Internal Server Error response:
{"error":"Something went wrong"}
Request failed: Server error: POST https://platform360.io/api/v1/monitoring/servers/1a23b45c-1234-1a23-1abc-1a234b56789c/setup resulted in a 500 Internal Server Error response:
{"error":"Something went wrong"}
exit status 6
Manual installation:
# hello360 USERTOKEN /etc/agent360-token.ini
Could not retrieve server_id:
We will provide additional updates as soon as we can.
Comments
0 comments
Please sign in to leave a comment.