Error Codes
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in API Gateway Error Codes.
Status Code |
Error Codes |
Error Message |
Description |
Solution |
---|---|---|---|---|
400 |
LTS.0009 |
Failed to validate the request body. |
Parameter verification failed. |
Modify request parameters based on the returned error information and try again. |
400 |
LTS.0010 |
The system encountered an internal error |
An internal error occurred |
An internal error occurred in LTS. Contact technical support. |
400 |
LTS.0201 |
The log group is not existed |
Failed to create the log stream because the associated log group does not exist. |
Check whether the ID of the log group is correct. |
400 |
LTS.0208 |
Log stream is associated by transfer |
The log stream does not exist. |
Check whether the log stream to be deleted exists. |
400 |
LTS.0301 |
'*' and '?' not allowed as first character |
Asterisks (*) and question marks (?) are placed in the middle or at the end of a keyword. |
Check the keywords field based on the error information. |
400 |
LTS.2001 |
Failed to create alarm rule |
Creation error. |
Check whether the project ID is correct. |
400 |
LTS.2002 |
Failed to delete alarm rule |
Deletion error. |
Check whether the database or network connection is normal. |
400 |
LTS.2003 |
Failed to update alarm rule |
Modification error. |
Abnormal connection to the database. Check the database instance status. |
400 |
LTS.2004 |
The size of alarm rule has exceed the limit: 200 |
The number of alarm rules cannot exceed 200. |
Delete existing alarm rules that are no longer used. |
400 |
LTS.2005 |
The parameter is incorrect |
Incorrect parameter. |
Correct the parameter based on the returned error information. |
400 |
LTS.2006 |
Alarm rule name has already exist |
The alarm rule name already exists. |
Use another alarm rule name. |
400 |
LTS.2007 |
Alarm rule not exist |
The alarm rule does not exist. |
Check whether the alarm rule exists. |
400 |
LTS.2008 |
Find Alarm rule failed |
Failed to query the alarm rule. |
Check whether the database or network connection is normal. |
400 |
LTS.2009 |
User must have SMN service authority |
You must have the permissions on SMN. |
Acquire the permissions on SMN. |
400 |
LTS.2010 |
Topics cannot be empty |
The SMN topic cannot be empty. |
Check whether the SMN topic is empty. |
400 |
LTS.2011 |
Alarm rule invalid query frequency or invalid cron expression |
Invalid query frequency or cron expression. |
Check the query frequency or cron expression. |
400 |
LTS.2012 |
The query time range cannot be larger than 1 hour when the query frequency is less than every 5 minutes. |
The query time range cannot be larger than 1 hour when the query frequency is less than every 5 minutes. |
Check the query time range and query frequency. |
400 |
LTS.2013 |
Send Subject Error |
Incorrect SMN topic. |
Correct the topic based on the error information. |
403 |
LTS.0003 |
No permission. |
Invalid role |
Grant the LTS service permission. |
403 |
LTS.0011 |
Invalid projectId |
Invalid project ID. |
Ensure that the project ID in the URL is the same as that in the token. |
500 |
LTS.0107 |
Current user does not have the permission to operate this group |
Failed to update the log group. |
Abnormal connection to the database. Check the database instance status. |
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