| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2018-11-21 |
error, message, troubleshooting, problems |
loadbalancer-service |
{{site.data.keyword.attribute-definition-list}}
{: #error-message-troubleshooting} {: troubleshoot} {: support}
This topic provides information on common error messages that you might encounter while creating or updating an instance of {{site.data.keyword.loadbalancer_full}}. {: shortdesc}
| Error | Explanation | Solution |
|---|---|---|
The maximum number of load balancers 'n' has been reached. |
Only 50 load balancer instances are allowed per account. | Ensure that you have 50 or less load balancer instances per account. |
The maximum number of given protocols 'n' in load balancer product order has been reached. |
Only two protocols can be added while provisioning a load balancer. | If you need more protocols, then after provisioning, you can add up to ten from the Protocols tab in the Load Balancer management flow. For more information, see monitoring and managing your service. |
The maximum number of given server instances 'n' in load balancer product order has been reached. |
Only ten servers can be added while provisioning a load balancer. | If you need extra servers, then after provisioning, you can add up to 50 from the Server Instances tab in the Load Balancer management flow. For more information, see monitoring and managing your service. |
Load balancer name must be a string and have at least 1 and up to 40 characters. |
The load balancer name is mandatory. Use only alphanumeric characters (or special characters '-' and '.') for the name. The name must not begin or end with a special character, and must be limited to 40 characters in length. | Enter a unique load balancer name. For example, "ui-servers" or "backend-servers". |
Format error found in given load balancer name. |
The load balancer name is mandatory. Use only alphanumeric characters (or special characters '-' and '.') for the name. The name must not begin or end with a special character, and must be limited to 40 characters in length. | Enter a unique load balancer name. For example, "ui-servers" or "backend-servers". |
Load balancer with the same name (case insensitive) already exists. |
A load balancer with the same name exists. | Enter a unique load balancer name to proceed further, for example, "ui-servers" or "backend-servers". |
Load balancer description must be a string and not exceed 255 characters. |
The load balancer description must be a string that does not exceed 255 characters. | Limit the description to 255 characters. |
Frontend port 80 is already used. |
You might have entered a front-end port that is already in use. | Enter a unique front end port. |
Backend port must be an integer. |
You might have entered an invalid back-end port value. | Enter a back-end port number between 1 and 65535. |
Since the protocol and port are not editable in health monitor, this error is impossible from UI. |
Your private subnet is not a standard type and cannot be used to create the load balancer. | Contact IBM Support. |
Private subnet 'xyz' must have at least 'n' free IP addresses. |
The selected private subnet does not have any free IP addresses. | Check these troubleshooting steps for more information. |
Specified private subnet VLAN is on router 'xyz'. However, no public subnet with 'n' free IPs was found with VLAN on the same router. |
This happens because you selected the Allocate from public subnet from this account option during provisioning. | Select Allocate from IBM System Pool instead, or contact IBM Support. |
Given new description must be a string. |
You might have entered an invalid description. | Enter a valid load balancer description, no larger than 255 characters. |
A billing item is required to process a cancellation for load balancer uuid=aaaa-bbbb-cccc-dddd. |
Billing information is missing or invalid for your account, and the load balancer cannot be cancelled. | Contact IBM Support. |
An internal error occurred. Data could not be retrieved. |
Metrics data cannot be retrieved | Reload the page. If the issue persists, then contact IBM Support. |
Front-end port must be an integer between 1 and 65535 excluding the range 56500-56520. |
You might have entered a front-end port number between 56500-56520. | Enter a unique port number between 1 to 65535, excluding the range of 56500 to 56520. |
Back-end port must be an integer. |
You might have entered an invalid back-end port value. | Enter a back-end port number between 1 and 65535. |
Back-end port must be an integer between 1 and 65535 excluding the range 56500-56520. |
You might have entered a back-end port between 56500 and 56520. | Enter a back-end port number between 1 and 65535, excluding the range of 56500 to 56520. |
Backend protocol HTTP is not compatible with frontend protocol TCP. |
You might have selected an incompatible back-end protocol and front-end protocol combination. | Select a valid front-end and back-end protocol combination, in the form: <br> HTTP-HTTP <br> HTTPS-HTTP <br> TCP-TCP |
Member weight <some value> is provided for member abcd-xxxx-yyyy-2222. The allowed weight value is 0-100 |
You might have entered an invalid weight. | Enter a weight value between 0 and 100. |
There was a problem fetching the servers. |
This can happen as a result of network timeout issues. | Reload the page. If the issue persists, contact IBM Support. |
| {: caption="Error messages" caption-side="bottom"} |