move elb docs to proper location Reviewed-by: OpenTelekomCloud Bot <None>
126 KiB
Error Codes
The following error code descriptions are only suitable for classic load balancers.
Overview
If an error occurs when using an API, an error response will be returned, which contains the error code and a piece of message, as shown in the following example. The following table lists error codes and their descriptions.
Example of Returned Error Information
{ "error": { "message": "listener exist, the port repeat", "code": "ELB.6101" } }
Error Codes
Status Code |
Error Code |
Message |
Description |
Solution |
---|---|---|---|---|
400 |
ELB.0002 |
Api request is null. |
The request is empty. |
Change the parameter settings. |
400 |
ELB.0004 |
Api response is null or invaild. |
The response is empty. |
Ensure that the backend server is healthy. |
400 |
ELB.0230 |
Tenant_id is empty. |
The project ID is left blank. |
Correct the project ID. |
400 |
ELB.1000 |
The loadbalancer URL is too long. |
The URL length exceeds the limit. |
Correct the URL. |
400 |
ELB.1010 |
Query elb quota error. |
Failed to query the quota. |
Contact customer service. |
400 |
ELB.1020 |
Lb ID is not correct. |
Incorrect load balancer ID. |
Change the parameter settings. |
400 |
ELB.1001 |
Request parameters error, private_key or certificate is nil or empty. Request parameters error, lb type, name, admin_state_up one of them is empty. |
Parameter type, name, or admin_status_up is left blank. |
Change the parameter settings. |
400 |
ELB.1001 |
Request parameter is not valid. |
The length of the load balancer name exceeds the limit. |
Change the listener name. |
400 |
ELB.1021 |
Request parameters error, name invalid. |
Invalid load balancer name. |
Change the parameter settings. |
400 |
ELB.1031 |
Request parameters error, lb len description too long. |
The length of the load balancer description exceeds the limit. |
Change the description. |
400 |
ELB.1041 |
Request parameters error, lb type is not valid. |
Invalid load balancer type. |
Change the parameter settings. |
400 |
ELB.1051 |
Request parameters error, lb bandwidth is not valid. |
Invalid load balancer bandwidth. |
Change the parameter settings. |
4000 |
ELB.1061 |
Request parameters error, lb vip_address and vip_subnet_id are nil. |
The floating IP address or subnet ID is left blank. |
Change the parameter settings. |
400 |
ELB.1071 |
Request parameters error, lb vip_address is not valid. |
Invalid floating IP address. |
Change the parameter settings. |
400 |
ELB.1081 |
Request parameters error, lb vpc_id is empty. |
The VPC ID is left blank. |
Change the parameter settings. |
403 |
ELB.1091 |
Lb number larger than quota. |
The number of load balancers exceeds the quota. |
Request a higher quota or delete load balancers that are no longer needed. |
400 |
ELB.1101 |
Vip address is exist. |
The floating IP address exists. |
Enter a valid floating IP address. |
404 |
ELB.1002 |
Find lb failed. |
The load balancer does not exist. |
Change the load balancer ID. |
400 |
ELB.1008 |
There is at least one member under the lb. |
Failed to delete the load balancer. |
Change the parameter settings. |
400 |
ELB.1018 |
There is at least one member under the lb. |
The load balancer has backend ECSs added. |
Change the parameter settings. |
400 |
ELB.1005 |
Update request paramters error. |
Failed to modify the load balancer. |
Check the parameters. |
400 |
ELB.1015 |
Lb can not be updated. |
The load balancer cannot be modified. |
Check the parameters. |
400 |
ELB.1025 |
Udpate request parameters error, name is too long. |
The length of the load balancer name exceeds the limit. |
Change the load balancer name. |
400 |
ELB.1035 |
Update request parameters error, name is not valid. |
Invalid load balancer name. |
Change the load balancer name. |
400 |
ELB.1045 |
Update request parameters error, description too long. |
The length of the load balancer description exceeds the limit. |
Change the description. |
400 |
ELB.1003 |
Lb not exist. |
The load balancer does not exist. |
Check the load balancer ID. |
400 |
ELB.1004 |
Query condition is not valid. |
Invalid query condition. |
Change the query condition. |
400 |
ELB.6000 |
Listener ID length is not correct. |
The length of the listener ID exceeds the limit. |
Change the listener ID. |
400 |
ELB.6010 |
Listener ID content is not correct. |
Invalid listener ID. |
Change the listener ID. |
400 |
ELB.6030 |
Listener is not associated with loadbalancer id. |
The listener does not belong to any load balancer. |
Check the listener ID. |
400 |
ELB.6040 |
The loadbalaner that the listener belongs to is not exist. |
The load balancer to which the listener is added does not exist. |
Check the load balancer ID. |
400 |
ELB.6020 |
Listener url is not correct. |
Incorrect listener URL. |
Correct the URL. |
400 |
ELB.6001 |
Request parameters error, "..nilKey.." is nil. |
A mandatory parameter is left blank. |
Specify the mandatory parameters. |
400 |
ELB.6011 |
Request parameters error, listener name too long. |
The length of the listener name exceeds the limit. |
Change the listener name. |
400 |
ELB.6021 |
Request parameters error, listener name is not valid. |
Invalid listener name. |
Change the listener name. |
400 |
ELB.6031 |
Request parameters error, listener len description too long. |
The length of the listener description exceeds the limit. |
Change the description. |
400 |
ELB.6041 |
Request parameters error, listener port is not in 1 ~ 65535. |
Invalid port number. |
Change the port number. |
400 |
ELB.6051 |
Request parameters error, listener lb algorithm is not valid. |
Invalid load balancing algorithm. |
Change the load balancing algorithm. |
400 |
ELB.6061 |
Request parameters error, listener protocol is not valid. |
Invalid protocol used by the listener. |
Change the protocol. |
400 |
ELB.6071 |
Request parameters error, listener backend protocol is not valid. |
Invalid backend ECS protocol. |
Change the protocol. |
400 |
ELB.6081 |
Request parameters error, listener sticky_session_type is not valid. |
Invalid sticky session type. |
Check the load balancer ID. |
403 |
ELB.6091 |
Request lb has more than user listener quota. |
The number of listeners reaches the limit. |
No more listeners can be added. |
400 |
ELB.6101 |
Listener port is repeated. |
The port exists. |
Use another port number. |
503 |
ELB.6002 |
Delete listener failed, listener does not exist. |
The listener does not exist. |
Check the listener ID. |
400 |
ELB.6015 |
This listener property cannot be updated |
The property cannot be modified. |
Select a property that can be modified. |
400 |
ELB.6025 |
Udpate request parameters error, listener len name too long. |
The length of the listener name exceeds the limit. |
Change the listener name. |
400 |
ELB.6035 |
Udpate request parameters error, listener name is not valid. |
Invalid listener name. |
Change the listener name. |
400 |
ELB.6045 |
Update request parameters error, listener len description too long. |
The length of the listener description exceeds the limit. |
Change the description. |
400 |
ELB.6003 |
Listener query condition is not valid. |
Invalid query condition. |
Change the query condition. |
400 |
ELB.2000 |
Member url is not correct. |
Incorrect backend ECS URL. |
Correct the URL. |
400 |
ELB.2003 |
Query member failed. |
Failed to query the backend ECS. |
Contact customer service. |
400 |
ELB.2005 |
Update member failed. |
Failed to update the backend ECS. |
Contact customer service. |
400 |
ELB.2010 |
Member listener ID length is not correct. |
The length of the listener ID exceeds the limit. |
Change the listener ID. |
400 |
ELB.2020 |
Member listener ID content is not correct. |
Incorrect listener ID. |
Change the listener ID. |
403 |
ELB.2001 |
Create member failed, the total amount of members exceeds the system setting. |
Failed to add the ECS because the number of backend ECSs reaches the limit. |
Check the maximum number of backend servers that can be added. |
400 |
ELB.2011 |
Add member listener is not exist. |
The listener does not exist. |
Ensure that the listener exists. |
400 |
ELB.2021 |
Request parameters error, member address is null. |
Invalid address. |
Check the IP address. |
400 |
ELB.2002 |
Delete member input param error. |
Incorrect parameters. |
Change the parameter settings. |
400 |
ELB.2012 |
This member is not exist. |
The backend ECS does not exist. |
Ensure that the backend server exists. |
400 |
ELB.7000 |
Listener_id must not be null. |
The listener ID is left blank. |
Change the listener ID and deliver the request again. |
400 |
ELB.7010 |
Healthcheck listener is not exist. |
The listener with which the health check is associated does not exist. |
Change the listener ID and deliver the request again. |
400 |
ELB.7020 |
This healthcheck is not exist. |
The health check does not exist. |
Change the health check ID and deliver the request again. |
400 |
ELB.7001 |
Healthcheck_interval is illegal. |
Invalid health check interval. |
Change the interval. |
400 |
ELB.7002 |
Healthcheck delete condition is not valid. |
Invalid query condition. |
Change the query condition. |
400 |
ELB.7001 |
Healthcheck update condition is not valid. |
Invalid query condition. |
Change the query condition. |
400 |
ELB.7004 |
Healthcheck query condition is not valid. |
Invalid query condition. |
Change the query condition. |
400 |
ELB.7014 |
Healthcheck configuration not exist. |
The health check does not exist. |
Check the health check ID. |
400 |
ELB.8001 |
Create a SG error. |
Failed to create the security group. |
Contact customer service. |
400 |
ELB.8101 |
Create VPC error. |
Failed to create the VPC. |
Contact customer service. |
400 |
ELB.8102 |
Delete VPC error. |
Failed to delete the VPC. |
Contact customer service. |
400 |
ELB.8103 |
Query VPC error. |
Failed to query the VPC. |
Contact customer service. |
400 |
ELB.8201 |
Create subnet error. |
Failed to create the subnet. |
Contact customer service. |
400 |
ELB.8202 |
Delete subnet error. |
Failed to delete the subnet. |
Contact customer service. |
400 |
ELB.8203 |
Query subnet error. |
Failed to query the subnet. |
Contact customer service. |
400 |
ELB.9001 |
Interval ELB create VM error. |
Failed to add the ECS. |
Contact customer service. |
400 |
ELB.9002 |
Internal ELB delete VM error. |
Failed to delete the ECS. |
Contact customer service. |
400 |
ELB.9003 |
Internal ELB query VM error. |
Failed to query ECS details. |
Contact customer service. |
400 |
ELB.9006 |
Internal ELB update port fail. |
Failed to update the port configured on the ECS data plane. |
Contact customer service. |
400 |
ELB.9007 |
Intenal ELB bind port fail. |
Failed to bind the port configured on the ECS data plane. |
Contact customer service. |
400 |
ELB.9061 |
Internal ELB query topic fail. |
Failed to query the SMN topic. |
Contact customer service. |
400 |
ELB.9062 |
Internal ELB create topic fail. |
Failed to create the SMN topic. |
Contact customer service. |
400 |
ELB.9063 |
Internal ELB query subscription fail. |
Failed to query the SMN subscription. |
Contact customer service. |
400 |
ELB.9064 |
Internal ELB create subscription fail. |
Failed to create the SMN subscription. |
Contact customer service. |
400 |
ELB.9023 |
Internal ELB get image error. |
Failed to query the image. |
Contact customer service. |
400 |
ELB.9033 |
Internal ELB get flavour error. |
Failed to query ECS specifications. |
Contact customer service. |
400 |
ELB.9043 |
Internal ELB get interface error. |
Failed to query the API bound to the ECS. |
Contact customer service. |
400 |
ELB.1007 |
Query internal ELB error. |
Failed to query details of the private network load balancer. |
Contact customer service. |
400 |
ELB.1012 |
Create tenant resource relation error. |
Failed to create the relationship between resources and the user. |
Contact customer service. |
400 |
ELB.1013 |
Update resource tenant allocation failed, cloud eye warning rule exceeds. |
Failed to modify the quota of a resource because the quota set in the Cloud Eye alarm rule is too large. |
Contact customer service. |
400 |
ELB.1014 |
Query resouce tenant relation failed. |
Failed to query the relationship between resources and the user. |
Contact customer service. |
400 |
ELB.1102 |
Token invalid |
Invalid token. |
Contact customer service. |
400 |
ELB.1103 |
Token invalid |
Invalid token. |
Contact customer service. |
400 |
ELB.1104 |
Token invalid |
Invalid token. |
Contact customer service. |
400 |
ELB.1105 |
Token invalid |
Invalid token. |
Contact customer service. |
400 |
ELB.1109 |
Authentication failed. |
Real-name authentication failed. |
Contact customer service. |
400 |
ELB.1201 |
Get Token failed |
Failed to obtain the token. |
Contact customer service. |
400 |
ELB.3001 |
Create floating IP failed. |
Failed to assign the floating IP address. |
Contact customer service. |
400 |
ELB.3002 |
Delete floating IP failed. |
Failed to release the floating IP address. |
Contact customer service. |
400 |
ELB.3003 |
Query floating IP failed. |
Failed to query the floating IP address. |
Contact customer service. |
400 |
ELB.3004 |
Query floating IP list failed. |
Failed to query floating IP addresses. |
Contact customer service. |
400 |
ELB.3005 |
Update floating IP failed. |
Failed to update the floating IP address. |
Contact customer service. |
400 |
ELB.4001 |
Create elastic IP failed. |
Failed to assign the EIP. |
Contact customer service. |
400 |
ELB.4002 |
Delete elastic IP failed. |
Failed to release the EIP. |
Contact customer service. |
400 |
ELB.4003 |
Query elastic IP failed. |
Failed to query the EIP. |
Contact customer service. |
400 |
ELB.4004 |
Query elastic IP list failed. |
Failed to query EIPs. |
Contact customer service. |
400 |
ELB.4005 |
Update elastic IP failed. |
Failed to update the EIP. |
Contact customer service. |
400 |
ELB.5003 |
Query bandwidth failed. |
Failed to query the bandwidth. |
Contact customer service. |
400 |
ELB.5005 |
Update bandwidth failed. |
Failed to update the bandwidth. |
Contact customer service. |
400 |
ELB.6004 |
Query listeners list failed. |
Failed to query listeners. |
Contact customer service. |
400 |
ELB.6006 |
Query ECS failed. |
Failed to query the ECS. |
Contact customer service. |