Many causes can lead to CVM login failure. Causes that can be monitored by Cloud Monitor include overly high CVM bandwidth usage and overly high CVM CPU/memory usage. This document describes how to troubleshoot these two causes.
The following causes of CVM login failure can be detected by Cloud Monitor:
Before troubleshooting, check whether the login attempt failed because the entered password was incorrect, you forgot the password, or the password failed to reset.
If yes, reset the password.
Problem: the self-diagnosis tool shows that bandwidth utilization is too high.
Solutions:
Problem: the self-diagnosis tool or Cloud Monitor shows that the CPU/memory usage of the CVM instance is too high, and therefore the system cannot establish a remote connection or the connectivity is poor.
Possible causes: viruses, trojans, third-party anti-virus software, application exceptions, driver exceptions, and automatic software backend updates may lead to high CPU usage, resulting in CVM login failure or slow access.
Solutions:
Many causes may lead to CVM login failure. For more information on other causes, see Windows Instance Login Failures or Linux Instance Login Failures.
Was this page helpful?