A simple application server moves through a defined set of states from creation to release. Understanding these states helps you anticipate what happens when you perform operations such as starting, stopping, or upgrading a server.
How it works
The following diagram shows all possible state transitions:
At a high level: creating a server moves it through Preparing → Starting → Running. From Running, you can stop, restart, reset, or upgrade the server. A server that expires, has an overdue payment, or is locked for security reasons enters the Disabled state.
Server states
The following table describes each state a simple application server can enter during its lifecycle.
| State in the console | State in an API call response | State type | Description |
|---|---|---|---|
| Preparing | Pending | Transitory | The server enters this state when creation begins, then transitions to Starting. |
| Starting | Starting | Transitory | The server enters this state after being created, started, or restarted, then transitions to Running. |
| Running | Running | Stable | The server is running and accessible. Servers approaching expiration also remain in this state — monitor the remaining service lifetime. |
| Stopping | Stopping | Transitory | The server enters this state after a stop or restart operation, then transitions to Stopped. |
| Stopped | Stopped | Stable | The server has been stopped. |
| Resetting | Resetting | Transitory | The server enters this state after a reset operation, then transitions to Running. |
| Upgrading | Upgrading | Transitory | The server enters this state after a resource plan upgrade, then transitions to Running. |
| Disabled | Disabled | Stable | The server has expired, been stopped due to an overdue payment, or been locked due to a security risk. See the Disabled state warning section below for recovery steps. |
Managing server states
The following sections describe each operation and its effect on server state.
Create a server
State transition: Preparing (Pending) → Starting → Running
After creation completes, the server enters the Running state and is ready to use. For example, connect to the server to manage its operating system, or deploy a website and access it from a browser. For more information, see Create a simple application server.
Stop a server
State transition: Running → Stopping → Stopped
Prerequisite: The server must be in the Running state.
If you don't need the server temporarily, stop it from the server card. For more information, see View the information of a simple application server.
Start a server
State transition: Stopped → Starting → Running
Prerequisite: The server must be in the Stopped state.
Start the server from the server card. For more information, see View the information of a simple application server.
Restart a server
State transition: Running → Stopping → Starting → Running
Prerequisite: The server must be in the Running state.
Restart the server after operations that require a reboot to take effect. For example, after setting a password, restart the server to apply the change. For more information, see Reset password.
Reset a server
State transition: Running → Resetting → Running
For more information, see Reset a simple application server.
Upgrade a server
State transition: Running → Upgrading → Running
If the current resource plan no longer meets your requirements, upgrade to a larger plan. For more information, see Upgrade configurations.
Release a server
Prerequisite: The server must be expired and in the Disabled state.
If an expired server is no longer needed, release it manually or wait for the system to release it automatically. For more information, see Release an instance.
Disabled state warning
A server enters the Disabled state when it expires, has an overdue payment, or is locked due to a security risk.
If your server is about to be stopped due to expiration or an overdue payment, the system sends you a notification. To maintain service continuity, renew the resource plan or complete the payment as soon as possible. For more information, see Expiration and overdue payments.
If your server is locked due to a security risk, submit a ticket to unlock it.