- What's New
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
- Application Service Mesh
- Buying a Service Mesh
- Mesh Management
- Service Management
- Gateway Management
- Grayscale Release
- Mesh Configuration
- Traffic Management
- Security
-
Best Practices
- Upgrading Data Plane Sidecars Without Service Interruption
- Service Governance for Dubbo-based Applications
- Reserving Source IP Address for Gateway Access
- How Do I Create a Service Mesh with IPv4/IPv6 Dual Stack Enabled
- How Do I Query Application Metrics in AOM?
- Reducing the Agency Permissions of ASM Users
- Istio-ingressgateway HA Configuration
- API Reference
-
FAQs
- Service Mesh Cluster
-
Mesh Management
- Why Cannot I Create a Service Mesh for My Cluster?
- Why Are Exclusive Nodes Still Exist After Istio Is Uninstalled?
- How Do I Upgrade ICAgent?
- How Do I Enable Namespace Injection for a Cluster?
- How Do I Disable Sidecar Injection for Workloads?
- What Can I Do If a Pod Cannot Be Started Due to Unready Sidecar?
- Why Does the Owner Group of the File Mounted to the Service Container Change After Configuring fsgroup?
- How Do I Handle a Canary Upgrade Failure?
- Possible Causes of Sidecar Injection Failures
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the Page of the Deployed Demo Application?
- Why Does Error Code 500 Is Displayed When I Create a Gateway?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- What Should I Do If the Application Data Fails to Be Obtained?
- How Do I Inject a Sidecar for the Pod Created Using a Job or Cron Job?
- Performing Grayscale Release
-
Managing Traffic
- Why Are the Created Clusters, Namespaces, and Applications Not Displayed on the Traffic Management Page?
- How Do I Change the Resource Requests of the istio-proxy Container?
- Does ASM Support HTTP/1.0?
- How Can I Block Access from Some IP Address Ranges or Ports for a Service Mesh?
- How Do I Configure max_concurrent_streams for a Gateway?
- How Do I Fix Compatibility Issues Between Istio CNI and Init Containers?
-
Monitoring Traffic
- Why Cannot I View Traffic Monitoring Data Immediately After a Pod Is Started?
- Why Are the Latency Statistics on the Dashboard Page Inaccurate?
- Why Is the Traffic Ratio Inconsistent with That in the Traffic Monitoring Chart?
- Why Can't I Find Certain Error Requests in Tracing?
- Why Cannot I Find My Service in the Traffic Monitoring Topology?
- How Do I Connect a Service Mesh to Jaeger or Zipkin for Viewing Traces?
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- User Guide
-
FAQs
- Service Mesh Cluster
- Mesh Management
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- Performing Grayscale Release
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Copied.
Error Codes
If an API fails to be called, no service data will be returned. You can identify the cause based on the error code of each API. If an error occurs in API calling, HTTP status code 4xx or 5xx will be returned. The response body contains the specific error code and information. If you are unable to identify the cause of an error, contact customer service and provide the error code so that we can help you solve the problem as soon as possible.
Error Response Body Format
If an error occurs during API calling, an error code and a message will be displayed. The following shows an error response body.
{
"errorMsg": Modify the request body based on the returned message and the ASM API documentation, or contact technical support.
"errorCode": "ASM.01400001"
}
In the preceding information, error_code indicates an error code, and error_msg describes the error.
Error Code Description
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to Error Codes.
Status Code |
Error Code |
Error Message |
Description |
Troubleshooting |
---|---|---|---|---|
400 |
ASM.01400001 |
Invalid request. |
The request body is invalid. |
Modify the request body based on the returned message and the ASM API documentation, or contact technical support. |
401 |
ASM.01401001 |
Authorization failed. |
The authentication failed. |
See the returned message or contact technical support. |
403 |
ASM.01403001 |
Forbidden. |
The access is denied. |
See the returned message or contact technical support. |
404 |
ASM.01404001 |
Resource not found. |
The resource is not found. |
Check whether the resource to be accessed has been deleted. |
409 |
ASM.01409001 |
The resource already exists. |
The resource already exists. |
Delete the resource and try again. |
429 |
ASM.01429001 |
Resource locked by other requests. |
The resource is locked by another request. |
See the returned message or contact technical support. |
500 |
ASM.01500001 |
Internal error. |
An internal error occurred. |
See the returned message or contact technical support. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot