Shutdown or Restart CVM Failure
Last updated: 2019-09-23 18:50:34PDF
Failure to shut down or restart a CVM is a rare event. Here are possible reasons for such failure and troubleshooting methods.
Possible reasons for shutdown or restart failure
Check the CPU/memory usage of the CVM. Excessive CPU utilization or memory exhaustion may cause shutdown or restart failure of the CVM on the console.
For Linux operating systems, you can check whether the ACPI management application is installed by running the
ps -ef | grep -w "acpid" | grep -v "grep"command. Install the acpid module if no ACPI process exists.
For Windows operating systems, you can check whether such failure is caused by WindowsUpdate taking too long. Windows usually performs patch-related operations by the time when the system is about to shut down, and if the update takes a long time, shutdown/restart failure may occur.
In case of initial purchase of Windows, the initialization process is slightly longer due to the use of Sysprep for distributing images. Windows will ignore the shutdown/restart event until the initialization has been finished, thus causing CVM shutdown/restart failure.
If the operating system is broken due to some software installed or attacks from Trojans or other viruses, shutdown/restart failure may also occur.
The forced shutdown/restart feature provided by Tencent Cloud can be used in case of multiple failed attempts to shut down or restart the CVM. This feature allows you to forcibly shut down/restart the CVM, which however may cause data loss or file system damage.
Select Forced Shutdown in the shutdown operation window on the CVM console.
Select Forced Restart in the restart operation window on the CVM console.