CSE Error Codes

Updated on 2024-12-16 GMT+08:00

View PDF

If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in Error Codes.

**Table 1** Engine management error codes
Status Code	Error Code	Error Message	Description	Measure
400	SVCSTG.00501134	Bad Request	Invalid engine type.	The engine type field is the specType field in the request query. Set it to a valid value (for example, CSE2) and try again. For example, to query the specifications supported by CSE, set specType to CSE2.
400	SVCSTG.00501111	Bad Request	Duplicate engine instance name.	Change the engine name.
400	SVCSTG.00501112	Bad Request	Insufficient engine instance quota.	Contact technical support engineers to increase the engine instance quota or delete unnecessary engine instances.
400	SVCSTG.00501133	Bad Request	Too many engines at the site.	Contact technical support engineers.
400	SVCSTG.00501103	Bad Request	Empty or invalid billing mode.	Input the billing mode parameter of the engine and check whether the user can create such an engine.
400	SVCSTG.00501104	Bad Request	Incorrect engine instance flavor format.	Invalid flavor. Enter a valid flavor.
400	SVCSTG.00501105	Bad Request	Incorrect AZ format.	Specify a valid AZ in the request parameter. The AZ field is a string array and cannot be empty. The number of AZ name levels ranges from 1 to 3.
400	SVCSTG.00501117	Bad Request	Engine cannot be deleted.	Wait until the engine state changes to Available, Unavailable, or Creation failed, and then try again.
400	SVCSTG.00501152	Bad Request	Incorrect task ID format.	Use the job ID returned by the APIs for creating and deleting an engine.
400	SVCSTG.00501153	Bad Request	Failed to find the task.	Use the job ID returned by the APIs for creating and deleting an engine.
400	SVCSTG.00501149	Bad Request	Abnormal engine node.	Try again later or contact technical support engineers.
400	SVCSTG.00501116	Bad Request	Failed to find the engine instance.	Check whether the input engine ID is correct. Use the username and password of the tenant to log in to CSE and check whether the current tenant has an engine with the corresponding ID.
400	SVCSTG.00501201	Bad Request	Incorrect format of the peer engine instance name.	The peer engine instance name must contain 3 to 24 characters, including letters, digits, and hyphens (-), and must start with a letter but cannot end with a hyphen (-). The name cannot be default and must be different from the current engine instance name.
400	SVCSTG.00501202	Bad Request	The peer engine must be an HA engine.	The engine must be an HA engine. Enter the engine flavor again.
400	SVCSTG.00501203	Bad Request	The peer engine must be in a single AZ.	The AZs must be single AZs. Enter the AZ list again.
500	SVCSTG.00500400	Internal Server Error	Incorrect internal request parameter of the service.	Check the error message. If the parameter is invalid, check whether the input argument is correct. For other errors, contact technical support engineers.

**Table 2** Dynamic configuration error codes
Status Code	Error Code	Error Message	Description	Measure
400	SVCSTG.00400649	Bad Request	Too long key or value.	The configuration item contains 1 to 2048 characters, including digits, letters, and special characters (.-_:[]). The value can contain 1 to 131072 characters, including digits, letters, and special characters ('~!@#$%^&*()_\{}\|:"<>?`-[],./=).
400	SVCSTG.00400650	Bad Request	Invalid configuration file.	Upload a valid file.
400	SVCSTG.00400651	Bad Request	The file is empty or in an incorrect format.	The uploaded file is empty or not in JSON format.
400	SVCSTG.00400652	Bad Request	The key or value is empty or is not a string.	The uploaded key or value is null or is not a string.
400	SVCSTG.00400653	Bad Request	Invalid label or body.	Enter a valid body or label in the query parameter.
400	SVCSTG.00400100	Bad Request	Invalid parameter.	Change parameters as prompted.
404	SVCSTG.00400106	Not Found	The resource does not exist.	Enter valid search criteria.
409	SVCSTG.00400107	Conflict	The resource already exists.	Do not create the same record.
500	SVCSTG.00300605	Failed to connect the configuration center to ETCD.	Internal Server Error	Contact technical support engineers.
400	SVCSTG.00300401	Invalid token	Unauthorized	Enter a correct token.

Parent topic: Appendix

Previous topic: ServiceStage Error Codes

Next topic: ServiceComb Error Codes

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot