Available in Classic and VPC
Guides problem situations you may encounter while using the Auto Scaling service and how to troubleshoot them. Click each problem situation to go to the relevant page.
Common problems
The following describes common problem situations that users may encounter:
LAUNCH process stops and server creation error
The LAUNCH process is paused and the server is not created.
- The number of servers should increase, but new servers are not created.
- Scale-out has not been performed.
- Servers keep being terminated automatically.
- Servers are repeatedly being terminated and created when the desired capacity is set to be 1.
- Servers are randomly terminated regardless of the set schedule.
Error messages
The following describes error messages that users may see:
"Failed to link externally." Error message
The message that indicates the external linkage has failed appears when trying to create Launch Configuration.
"Administrative suspension is active due to repeated server creation failures" error message
- The error message that indicates "Administrative suspension is active due to repeated server creation failures" appears.
- "It is presumed that there is defect in the server image or user data. Launching server instance failed." The message appears.
Content to explore
NAVER Cloud Platform provides information in many ways to help our customers. Here guides some useful contents that you can leverage when using the Auto Scaling service.
- FAQs: Auto Scaling FAQs
- NAVER Cloud Platform blog: use Auto Scaling
If you did not find what you need in this guide or need additional information, feel free to let us know anytime by clicking the feedback icon below. We'll look into your feedback and provide more useful information.