This article applies to:
•Proxy and Data Ingestion
•Product edition: All
•Feature Category: Proxy
Problem description:
On Friday, Oct 21st, 3:45 pm PST, a number of VMware Aria Operations for Applications service account tokens were deleted, this means that any task using those tokens will error out.
It also affects the ability of proxies to connect to the VMware Aria Operations for Applications if proxies are deployed using the affected tokens.
You should already have been alerted of this issue through either a 401 error on the proxy device or a "Proxy check-in with an invalid token observed" Out of the Box alert if proxies are installed using the impacted tokens.
Also, if these tokens were used in any WF API calls in a script/code or external integration, then it would also need to be updated with the new tokens.
2021-02-18 22:52:28,376 ERROR [proxy:checkinError] HTTP 401 Unauthorized: Please verify that your server and token settings are correct and that the token has Proxy Management permission!
Resolution:
Please ask your teams to follow the steps here to restore ingestion:
-
- Generate service account token- https://docs.wavefront.com/wavefront_api.html#generate-and-manage-the-api-tokens-for-a-service-account
- Update the proxy configuration (wavefront.conf) file with the new token- https://docs.wavefront.com/proxies_configuring.html
- Restart the proxies- https://docs.wavefront.com/proxies_installing.html#start-and-stop-a-proxy
Please see docs for details:
https://docs.wavefront.com/proxies_troubleshooting.html#common-proxy-log-messages
"Post October 21st 2022, if your proxies are down with the error below, your service account was deleted and needs to be reactive and proxies need to be reissued with the new token" what do you mean by 'reactive' - also what happened to cause you to delete service accounts on the 21st October?
I've answered No to was this article helpful as it raises more questions than it answers