Auto Scaling:Troubleshoot scaling activity exceptions

Error message

Possible cause

Solution

DBInstanceIdentifier does not refer to an existing DB instance.(xxxx)

The ApsaraDB RDS instance does not exist.

Check whether the ApsaraDB RDS instance attached to the scaling group exists.

The current status of the load balancer xxxxx does not support this action.

The Server Load Balancer (SLB) instance is not in the Active state.

Check whether the SLB instance attached to the scaling group is in the Active state.

To execute the specified scaling rule, the total capacity will not change.

The number of instances in a scaling group must remain within the defined minimum and maximum limits. Any scaling activity that causes the instance count to exceed these limits will be rejected.

Check the existing number of instances and scaling rule configurations. Make sure that the post-scaling instance count remains within the configured limits.

The current status of DB instance xxxxx does not support this action.

The ApsaraDB RDS instance is in an abnormal state and cannot support scaling activities.

If the ApsaraDB RDS instance attached to the scaling group is being migrated, log on to the ApsaraDB RDS console to verify the instance status. Once the instance is confirmed to be functional, retry the scaling activity.

You cannot delete a scaling group or launch a new scaling activity while there is scaling activity in progress for the specified scaling group.

The scaling group is currently undergoing a scaling activity.

Wait for the current scaling activity to complete before initiating a new one.

You cannot launch a new scaling activity during the cooldown period.

The scaling activity was rejected because the scaling group is currently in the cooldown period.

Wait for the cooldown period to finish before initiating scaling activities. For more information, see Cooldown period.

The current status of the specified scaling group does not support this action.

The scaling group is in an unsupported state, such as Disabled or Deleting.

If the scaling group is disabled, enable it before initiating the scaling activity.

The specified SecurityGroupId does not exist.

The security group specified in the scaling configuration does not exist.

Modify the scaling configuration by specifying a valid security group.

To remove the instances, the total capacity will be lesser than the min size.

The number of instances in a scaling group cannot be reduced below the specified minimum. If removing instances would cause the group size to fall below this minimum, the removal operation is rejected.

Check the existing number of instances and scaling rule configurations. Make sure that the post-scaling instance count remains within the configured limits.

The specified LoadBalancerId does not exist.

The specified SLB instance does not exist.

Check whether the SLB instance attached to the scaling group exists. For information about how to attach an SLB instance to a scaling group, see Attach or detach SLB instances to or from scaling groups.

Ess should be authorized in ram to operate user resource.

The current Resource Access Management (RAM) user does not have permissions to access Auto Scaling resources.

Log on to the RAM console to grant permissions before you proceed.

To attach the instances, the total capacity will be greater than the max size.

The number of instances in the scaling group cannot exceed the specified maximum. If adding instances would cause the group size to exceed this limit, the operation is rejected.

Check the existing number of instances and scaling rule configurations. Make sure that the post-scaling instance count remains within the configured limits.

The current status of virtual switch does not support this operation.

The vSwitch is in the pending or modifying state, preventing the scaling activity from being executed.

Check the status of the vSwitch associated with the scaling group to ensure it is working correctly and then retry the scaling activity.

The specified virtual switch does not exist.

The specified vSwitch does not exist.

Make sure that the vSwitch associated with the scaling group is not deleted.

The specified launch template set is not found.

The specified launch template does not exist.

Log on to the ECS consoleand check that the launch template associated with the scaling group exists. If necessary, update the launch template for the scaling group.

Instance "xxxxx" and the specified scaling group are not in the same VPC.

The ECS instance and the scaling group are in different virtual private clouds (VPCs).

Make sure that the scaling group and ECS instances are in the same VPC, or that the ECS instances are using the classic network.

The specified virtual switch and the instance in Load Balancer "xxxxx" are not in the same VPC.

The SLB instance and the vSwitch are in different VPCs.

Make sure that the vSwitch and the SLB instance are in the same VPC. For information about limits on attaching SLB instances to scaling groups, see Attach or detach SLB instances to or from scaling groups.

Instance "xxxx" is already attached to another scaling group.

ECS instances can only be added to a single scaling group and cannot be part of multiple scaling groups simultaneously.

Make sure that ECS instances to be added are not part of any existing scaling groups.

The specified image does not exist.

The image does not exist.

Check the scaling configuration to ensure the image exists and is accessible.

DataDiskSnapshotId "xxxx" does not exist.

The data disk snapshot does not exist.

Check the scaling configuration to ensure that the data disk snapshot exists and is accessible.

Error message

Possible cause

Solution

Fail to scale instances for scaling group("Ignore to remove N instances("instances in standby/protected status")").

The specified instance is in the Standby or Protected state.

Manually remove or release the instance.

Fail to remove Instances "i-xxx1, i-xxx2"("The current status of the specified scaling group does not support this action.").

The scaling group is in a state that prevents instance removal.

Make sure that the scaling group is in the Enabled state. For more information, see RemoveInstances.

Fail to create Instances into scaling group("The specified InstanceType has been offline.").

The specified instance type is no longer available for purchase.

Select available instance types in the scaling configuration. For more information, see Overview of instance families.

Fail to create Instances into scaling group("The specified ImageId does not exist.").

The image ID specified in the scaling configuration is invalid.

Check the scaling configuration to ensure the specified image exists and is accessible, or select an alternative available image.

Fail to create Instances into scaling group("Your account has been in arrears.").

Your account has overdue payments.

Make sure that your account balance is sufficient. To check your account funds, go to Billing Management.

Fail to create Instances into scaling group("Your account does not have enough balance.").

Your account balance is insufficient.

Make sure that your account balance is sufficient. To check your account funds, go to Billing Management.

Fail to create Instances into scaling group("Your account has not passed the real-name authentication yet.").

Your account failed real-name authentication.

Complete real-name authentication.

Fail to create Instances into scaling group("The specified parameter "spotPriceLimit" can't be lower than current public price.").

The maximum hourly price for spot instances is less than the prevailing market price.

Check and update the scaling configuration and reset the maximum hourly price or bidding policy to guarantee the conditions for creating spot instances are fulfilled. For more information, see Overview

Fail to create Instances into scaling group("Living afterpay instances quota exceeded.").

Your pay-as-you-go instance limit has been reached.

To raise the limit on pay-as-you-go instances, contact Alibaba Cloud support or submit a service ticket. For more information, see Manage ECS quotas.

Fail to create Instances into scaling group("The specified parameter "KeyPairName" does not exist in our records.").

The AccessKey pair specified in the scaling configuration is missing.

Check the scaling configuration to make sure that the current AccessKey pair is valid. If necessary, reset the AccessKey pair.

Fail to create Instances into scaling group("The specified parameter 'SystemDisk.Category' is not support IoOptimized Instance. Valid Values: cloud_efficiency;cloud_ssd. ").

System disks of this type cannot be used to create I/O-optimized instances.

Check the scaling configuration and adjust the system disk type as needed. Recommended system disk types:

• cloud_efficiency

• cloud_ssd

Fail to create Instances into scaling group("The resource is out of stock in the specified zone. Please try other types, or choose other regions and zones.").

The available inventory for the specified resource is inadequate.

Check the scaling configuration and scaling group details, and select an alternative instance type or zone if necessary.

Fail to create Instances into scaling group("The RAM user does not have the privilege to pass a RAM role.").

The specified RAM role in the scaling configuration does not exist.

Check the scaling configuration and assign a valid RAM role.

Fail to create Instances into scaling group("No payment method has been registered on the account.").

The account currently has no default payment method.

To set the default payment method, go to Billing Management.

Fail to create Instances into scaling group("Exceeding the allowed amount of instances of a security group.").

The number of instances associated with the specified security group has reached its maximum limit.

Check the existing scaling configuration and distribute the instances across multiple scaling groups, ensuring each group is associated with a specific security group to improve horizontal scaling performance.

Fail to create Instance into scaling group("The current status of instance "pending" does not support this action.").

The instance is in a state that does not support the requested operation.

Check the instance state to ensure it is in the Running state and retry the operation.

Fail to create Instances into scaling group("Abandon lifecycleActionResult parameter caused the instance to rollback.").

The scaling group has a lifecycle hook with the Scaling Activity parameter set to Scale-out Event and the Default Execution Policy parameter set to Reject. Once the specified timeout period expires, the lifecycle hook is triggered to roll back the scale-out activity and release the scaled-out instances.

Check the execution policy of the lifecycle hook.

Fail to create instance into scaling group("The specified SecurityGroupId is invalid or does not exist.")

The security group does not exist.

Check the scaling configuration to ensure the specified security group exists, or select an existing security group.

Fail to create instance into scaling group("The specified ImageId does not exist.")

The image does not exist.

Check the scaling configuration to ensure the specified image exists, or select an existing image.

Fail to create instance into scaling group("Your account has been in arrears.")

Your account balance is insufficient.

Make sure that your account balance is sufficient.

Fail to scale instances for scaling group("Backend server quota exceeded in load balancer "lb-xxxxxxx".").

The quota for ECS instances that can be attached to the SLB backend server group has been reached.

Raise the quota for ECS instances that can be attached to the SLB backend server group. For more information, see Limits and Quota management.

Fail to create Instances into scaling group("The specified imageName does not exist.").

The image name does not exist.

Check the scaling configuration to ensure the specified image name exists, or select an existing image name.

Fail to create Instances into scaling group("This resource type is not supported. Please try other resource types.").

The specified resource type is not available in the selected zone.

To increase the scale-out success rate, specify multiple zones for the scaling group and include multiple ECS instance types in the scaling configuration. For more information, see Manage scaling groups and Create a scaling configuration of the ECS type.

Fail to create Instances into scaling group("The specified parameter SnapshotId is not exist.").

The disk snapshot does not exist.

Check the scaling configuration to ensure the specified disk snapshot exists, or select an existing disk snapshot.

Fail to create Instances into scaling group("Don't have enough private IPs in this switch").

The vSwitch lacks enough available private IP addresses.

Check the vSwitch specified in the scaling configuration and increase its available private IP addresses, or Include multiple zones in the scaling configuration. For more information, see Manage scaling groups.

Fail to create Instances into scaling group("The specified parameter SystemDisk.Size is less than the image size.").

The system disk size is smaller than the image size.

Check the scaling configuration and either increase the system disk size or replace the specified image with a smaller one.

Fail to create Instances into scaling group("Living postPaid disks quota exceeded.").

The pay-as-you-go disk limit for the current account has been reached.

To raise the limit on pay-as-you-go disks, contact Alibaba Cloud support or submit a service ticket. For more information, see Manage ECS quotas.

Fail to create Instances into scaling group("The specified ram role is not authorized for ecs, please check your role policy.").

The AliyunEssDefaultRole RAM role of Auto Scaling does not have permissions to use ECS resources.

Grant permissions on ECS resources to the AliyunEssDefaultRole RAM role.

Fail to create instance into scaling group("The resource in the specified zone is no longer available for sale. Please try other regions and zones.")

The instance type is no longer available for purchase in the specified zone.

Check the scaling group settings and specify multiple zones. For more information, see Manage scaling groups.

Fail to create instance into scaling group("The resource is out of stock in the specified zone. Please try other types, or choose other regions and zones.")

The instance type is no longer available for purchase in the specified zone.

To increase the scale-out success rate, specify multiple zones for the scaling group and include multiple ECS instance types in the scaling configuration. For more information, see Manage scaling groups and Create a scaling configuration of the ECS type.

Fail to create instance into scaling group("The specified parameter "KeyPairName" only support IoOptimized Instance.")

The instance type is non-I/O optimized and does not support AccessKey pairs.

In the scaling configuration, either change the instance type to an I/O-optimized type or remove the KeyPair parameter.

Fail to create instance into scaling group("A RAM role can't be used for classic instance.")

Instances in the classic network do not support RAM roles.

Check the network type of the scaling group. If it is not set to VPC, either change the network type to VPC or remove the RamRoleName parameter from the scaling configuration.

Fail to create instance into scaling group("The specified parameter "RAMRoleName" does not exist.")

The RAM role name does not exist.

Log on to the RAM console to check whether the current RAM role exists, or specify another RAM role.

Fail to create instance into scaling group("The specified image does not support the specified InstanceType.")

The image and the instance type do not match.

Go to the ECS purchase page to view the supported images for the selected instance type and adjust the scaling configuration accordingly.

Fail to create instance into scaling group("The requested resource is sold out in the specified zone; try other types of resources or other regions and zones.")

The inventory for the specified instance type is insufficient in the selected zone for the scaling group.

To increase the scale-out success rate, specify multiple zones for the scaling group and include multiple ECS instance types in the scaling configuration. For more information, see Manage scaling groups and Create a scaling configuration of the ECS type.