Error Codes¶
Introduction¶
This section explains the meanings of error codes returned by CTS APIs.
Example of Returned Error Information¶
{
"error_code": "CTS.0003",
"error_msg": "Invalid message body. The message body is empty or invalid."
}
Error Code Description¶
Status Code | Error Code | Error Message | Description | Solution |
|---|---|---|---|---|
400 | CTS.0001 | IAM or OBS exception, please check. | The IAM or OBS service is abnormal. | Contact technical support. |
403 | CTS.0002 | The user fails the authentication or does not have permission to this operation. | Authentication failed or you do not have the permissions required. | Check your permissions. |
400 | CTS.0003 | Invalid message body. The message body is empty or invalid. | The message body is empty or invalid. | Check the body content and format. |
500 | CTS.0004 | Data write exception. | Failed to write data. | Contact technical support. |
500 | CTS.0005 | Data read exception. | Failed to read data. | Contact technical support. |
403 | CTS.0012 | Invalid project ID. Check whether the project ID is correct. | The project ID is invalid. | Check whether the project ID is correct. |
400 | CTS.0056 | Failed to create lts trace analysis. | Failed to enable trace analysis. | Contact technical support. |
404 | CTS.0100 | CTS does not support API interface version query. | API version query is not supported in CTS. | Contact technical support. |
400 | CTS.0200 | Tracker number is Maximum. | The number of trackers has reached the upper limit. | Delete or modify unnecessary trackers. |
400 | CTS.0201 | A management tracker has been created. | A management tracker has been created. | Check whether the management tracker is available. |
400 | CTS.0202 | Invalid message body. Tracker tracker_type must be either system or data. | The value of tracker_type is invalid. | Change its value to system or data. |
400 | CTS.0203 | Invalid message body. The tracker_name is a string of 1 to 32 characters and cannot start with underscores or hyphens. | The value of tracker_name is invalid. | Modify its value by referring to the parameter descriptions. |
400 | CTS.0204 | The tracker_name parameter of a management tracker can only be set to system. | The tracker_name parameter of a management tracker must be set to system. | Modify its value by referring to the parameter descriptions. |
400 | CTS.0205 | Invalid message body. Tracker status is required and value must be either enabled or disabled. | The status parameter can only be set to enabled or disabled. | Change its value to enabled or disabled. |
400 | CTS.0206 | Invalid message body. The data_bucket is not need. | The data_bucket parameter cannot be included in the message body for a management tracker. | Delete the data_bucket parameter. |
400 | CTS.0207 | Invalid message body. The tracker_name value cannot be system or system-trace. | The tracker_name parameter in the message body cannot be set to system for a data tracker. | Change the value of tracker_name to a value other than system. |
400 | CTS.0208 | The tracker already exists. | The tracker already exists. | Check whether the tracker already exists. |
400 | CTS.0209 | You cannot create different trackers to record the same type of operations on the same OBS bucket. | A type of operations on an OBS bucket can be tracked by only one tracker. | Change the tracker configurations. |
400 | CTS.0210 | Invalid message body. The OBS bucket for which data operations are to be recorded can not be empty. | The OBS bucket to be tracked cannot be empty. | Select another bucket or ensure that the bucket is not empty. |
400 | CTS.0211 | Check bucket failed.The bucket is not exist. | The OBS bucket to be tracked does not exist. | Check whether bucket_name is correctly set. |
400 | CTS.0212 | The tracked OBS bucket can not be modify. | The tracked OBS bucket cannot be modified. | Withdraw the changes on the OBS bucket. |
400 | CTS.0213 | Invalid message body. The OBS bucket for which data operations are to be recorded and the OBS bucket configured for storing transferred traces cannot be the same. | The OBS bucket used for trace transfer cannot be the tracked OBS bucket. | Select another OBS bucket for trace transfer. |
404 | CTS.0214 | The tracker does not exist. | The tracker does not exist. | Check whether the tracker has been deleted. |
400 | CTS.0215 | Check bucket failed.The bucket is already exist. | The OBS bucket already exists. | Change the value of bucket_name. |
400 | CTS.0216 | Create bucket failed. | Failed to create a bucket. | Contact technical support. |
400 | CTS.0217 | Set bucket life cycle failed. Contact O&M personnel. | Failed to set a lifecycle rule for the OBS bucket. | Contact technical support. |
400 | CTS.0218 | Invalid message body. The file_prefix_name is a string of 0 to 64 characters and can only contain uppercase letters, lowercase letters, digits, hyphens, underscores and periods. | The value of file_prefix_name is invalid. | Modify its value by referring to the parameter descriptions. |
400 | CTS.0219 | The bucket operation cannot be empty. | The operation type cannot be empty. | Select at least one operation type to track. |
400 | CTS.0220 | KMS is not supported. | KMS is not supported. | Contact technical support. |
400 | CTS.0221 | The KMS ID is empty. | The KMS ID is empty. | Check whether the KMS ID is correct. |
400 | CTS.0222 | Failed to obtain key list from KMS. | KMS verification failed. | Check whether the KMS ID is correct. |
400 | CTS.0225 | The Bucket operation must be WRITE or READ or WRITE,READ. | The bucket operation must be write, read, or read/write. | Enter a correct parameter. |
400 | CTS.0231 | Invalid bucket name. A bucket name must be a string of 3 to 63 characters, including only lowercase letters, digits, hyphens (-), or periods (.). It must start with a digit or a lowercase letter. | Invalid bucket name. A bucket name must contain 3 to 63 characters and start with a digit or a lowercase letter. Only lowercase letters, digits, hyphens (-), and periods (.) are allowed. | Check whether the bucket name is correct. |
400 | CTS.0300 | Query data failed. | Query failed. | Try again later or contact technical support. |
400 | CTS.0400 | Notification name is existed already. | The key event notification name already exists. | Check whether the key event notification already exists. |
400 | CTS.0401 | Invalid message body. The operations parameter value is invalid. | The operations parameter is invalid. | Check whether the operation parameter is correct. |
400 | CTS.0402 | The Smn topic does not exist. | The SMN topic does not exist. | Check whether the SMN topic exists. |
404 | CTS.0403 | The notification does not exist. | The key event notification does not exist. | Check whether the key event notification has been deleted. |
400 | CTS.0404 | State setting failed, check if topicId exists. | Failed to enable the key event notification. Check whether the SMN topic has been configured. | Check whether the SMN topic has been configured. |
400 | CTS.0407 | The quantity has exceeded the maximum quantity limit. | The number of key event notifications exceeds the upper limit. | Check whether the number of key event notifications exceeds the quota. |
400 | CTS.0410 | The notification_type must be smn. | The key event notification type can only be smn. | Check the key operation notification type. |
400 | CTS.0411 | The notification_name invalid. | The notification name is invalid. | Check whether the notification name is correct. |