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. |
400 |
LTS.0007 |
The request body format must be json. |
The request body is not in JSON format. |
Modify the request body to the JSON format and try again. |
400 |
LTS.0101 |
Failed to create log group, the group name has been existed |
Failed to create the log group because a log group with the same name already exists. |
Check the log group name. |
400 |
LTS.0104 |
LTS.0104Failed to create log group, the number of log groups exceeds the quota |
Failed to create the log group because the maximum number of log groups allowed has been reached. |
Check whether the number of log groups has reached the quota (100 by default). |
400 |
LTS.0105 |
Log group is associated by transfer |
Failed to delete the log group because the log group has been associated with log transfer tasks. |
Delete the associated log transfer tasks first. |
400 |
LTS.0106 |
The log group TTL day must be integer and between 1 and 30 |
The log retention duration must be set from 1 to 30 days. |
Change the log retention duration to a value ranging from 1 to 30. |
400 |
LTS.0205 |
The log stream name has been existed |
Failed to create the log stream because a log stream with the same name already exists. |
Check the log stream name. |
400 |
LTS.0206 |
Failed to create log stream, the number of Log streams exceeds the quota |
Failed to create the log stream because the maximum number of log streams allowed has been reached. |
Check whether the number of log streams in the log group has reached the quota (100 by default). |
400 |
LTS.0207 |
Log stream is associated by transfer |
Failed to delete the log stream because the log stream has been associated with log transfer tasks. |
Check whether the log stream is associated with a log transfer task. A log stream associated with a log transfer task cannot be deleted. |
400 |
LTS.0416 |
obs bucket does not exist |
The OBS bucket does not exist. |
Create an OBS bucket first. |
400 |
LTS.0701 |
end_time must be superior to start_time, and line_num must be between them if it's provided |
The values of time parameters must meet the following requirements: start_time < line_num < end_time |
Modify the parameter values to meet the requirements. |
400 |
LTS.1901 |
field is not in the list |
A parameter is not in the specified list. |
Modify the parameter based on the description in error_msg. |
400 |
LTS.1902 |
name is invalid |
A parameter is not in the specified list. |
Modify the parameter based on the description in error_msg. |
400 |
LTS.1903 |
limit must be between lower boundary and upper boundary |
The value of limit is not in the range allowed. |
Set limit to a value ranging from 1 to 5000. |
401 |
LTS.0001 |
Invalid projectId |
Invalid project ID. |
Ensure that the project ID in the URI is the same as that in the token. |
401 |
LTS.0003 |
Incorrect IAM authentication information: decrypt token fail |
Invalid token. |
Obtain a token again. |
401 |
LTS.0023 |
Current user is suspended or restricted or unverified. |
Your account has not completed the real-name authentication, or has been frozen or restricted. |
Ensure that your account has completed the real-name authentication, and is not in arrears or frozen. |
403 |
LTS.0018 |
Current user does not have the permission to operate obs |
You do not have the permissions required to perform operations on the OBS bucket. |
You do not have the permissions required to perform operations on the OBS bucket. |
500 |
LTS.0010 |
Internal Server Error |
Internal server error. |
An internal error occurred in LTS. Contact technical support. |
500 |
LTS.0102 |
Failed to create log group. |
Failed to create the log group. |
Check whether the project ID is correct and whether the log group name meets the requirements. |
500 |
LTS.0103 |
Failed to delete log group |
Failed to delete the log group. |
Check whether the database or network connection is normal. |
500 |
LTS.0202 |
Failed to create log stream |
Failed to create the log stream. |
Check whether the project ID and group ID are correct and whether the log stream name meets the requirements. |
500 |
LTS.0203 |
Failed to delete log stream |
Failed to delete the log stream. |
Check whether the database or network connection is normal. |
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