If an SAE application instance fails to start, you can use the one-click debugging feature in the SAE console to efficiently identify the root cause.
Prerequisites
Background
During deployment, an instance may fail to start due to application-level issues or misconfigurations, often resulting in a CrashLoopBackOff state. In such cases, use the one-click debugging feature. This feature keeps the failing instance alive and lets you access its container through a webshell to diagnose the problem. For more information, see Use a webshell to diagnose an application.
Procedure
-
In the SAE application list, select the target region and namespace at the top, and then click the target application ID to open the application details page.
-
On the Basic Information page of the application, click the Instances tab.
-
On the Instances tab, in the Default Group section, find the application instance with a Status of CrashLoopBackOff. Hover over the status and click One-click Debugging in the tooltip.
-
In the One-click Debugging panel, select the I understand the system modification behavior and I accept further debugging. checkbox and click Next. Then, click Debug Instance to open the command-line interface of the target instance.
-
After you enter the container, you can start the application manually or perform other debugging tasks.
NoteWhen an instance enters debugging mode, its Status changes to No Service Traffic Received to distinguish it from normally running instances.
-
After debugging, delete the instance by using one of the following methods, depending on the application's deployment state:
-
Publishing state (a change is in progress)
On the Basic Information page, click Back to Earlier Version in the upper-right corner. Choose a rollback method to revert to the last stable version. After the deployment succeeds, the system automatically destroys the debugging instance.
-
Non-publishing state (no change is in progress and the instance is in the Running state)
In the Operations column for the target instance, click the
icon, and then click Delete. In the Delete Instance dialog box, click Confirm.
NoteAn instance with one-click debugging enabled does not receive service traffic. To avoid unnecessary charges, delete the instance immediately after debugging.
-