Troubleshooting general issues
Some generally known issues with Managed services are documented.
- Sometimes, Managed services may fail to retrieve the power state of a resource from the remote provider. The cause of the error may be due to the missing underlying cloud resource. As a resolution, check the cloud provider console to ensure that the underlying resource is still present. If it has been deleted from outside of Managed services, then this error message may occur.
-
Managed services might face issues whenever a microservice becomes inactive. To find and restart all the inactive microservices, run the following command from the directory where you extracted the content of the Managed services compressed file on the master node:
bash MS-remedies.sh
Note: The script does not restart base microservices like MongoDB, Auth, and Identity.
-
For information about collecting Managed services Logs, see Collecting logs using camCollector script.