All Products
Search
Document Center

Elastic Compute Service:What do I do if an ECS instance remains in the Stopping state?

Last Updated:Feb 07, 2025

This topic describes how to troubleshoot the issue that an Elastic Compute Service (ECS) instance remains in the Stopping state when you stop or restart the instance in the ECS console.

Background information

When you stop or restart an ECS instance in the ECS console, the internal operating system of the instance must release resources, such as processes, CPUs, and memory, and the virtualization layer must also release related resources. The time required for the stop or restart operation is approximately up to 20 minutes and varies based on various factors, such as the number of services running on the instance. For example, after an instance restart operation is triggered, the instance enters the Stopping (Stopping) state, the Starting (Starting) state, and then the Running (Running) state.

Workflow

If the ECS instance remains in the Stopping state for an extended period of time, for example, more than 10 to 20 minutes, you can troubleshoot and handle the issue by using the following workflow.

image

The following section describes the common causes of and solutions to instances that remain in the Stopping state for an extended period of time.

  • Causes

    • When an ECS instance runs an excessive number of service processes, the operating system must release the related resources after the stop operation is triggered. As a result, the instance remains in the Stopping state for an extended period of time.

    • The system becomes unresponsive for unknown reasons during the stop process.

  • Solutions

    • After the instance stop operation is triggered, the instance starts to perform stop-related operations. During this period, the instance status cannot be changed. Wait until the instance is restarted or stopped before you proceed.

    • If you want to obtain more information, such as the status of an instance, you can connect to the instance by using Virtual Network Computing (VNC). Identify and handle the issue based on the information on the VNC terminal.

    • After the instance is restarted, analyze system logs to identify the cause of the issue.

References