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.0001 |
Invalid log transfer type. |
Invalid projectId. ProjectId is invalid or null. |
Check the projectId to ensure it is valid and not null. |
|
400 |
LTS.0002 |
The parameter is empty |
The parameter is empty. The parameter cannot be empty. |
Check the parameter to ensure it is not empty. |
|
400 |
LTS.0003 |
Invalid token |
Invalid token |
Obtain the token again. |
|
400 |
LTS.0007 |
The request body format must be json |
The incoming request body is invalid. The incoming request body is not JSON. |
Check the request body to ensure it is a valid JSON format. |
|
400 |
LTS.0009 |
Failed to validate the request body |
Failed to validate the request body. Request parameters are illegal. |
Check the request parameters to ensure they are valid. |
|
400 |
LTS.0010 |
The system encountered an internal error |
The system encountered an internal error. |
Contact support or check the system logs for more information. |
|
400 |
LTS.0011 |
Invalid projectId |
Illegal projectId. The projectId is empty or inconsistent with the projectId in the token. |
Check the projectId to ensure it is not empty and matches the projectId in the token. |
|
400 |
LTS.0014 |
Failed to process current operation to ES |
The operation database is abnormal. The connection to the database is abnormal. |
Check the database connection and ensure the database is running normally. |
|
400 |
LTS.00141 |
kafka operation authorize failed. |
Querying custom Kafka failed. |
Check custom Kafka configuration and connectivity. |
|
400 |
LTS.0018 |
Current user does not have the permission to operate obs, obs error code: [%s]. |
The current user does not have permission to make this request. The current user does not have the operation permission of the OBS bucket. |
Check the user permissions to ensure they have the required access to the OBS bucket. |
|
400 |
LTS.0019 |
Current bucket is encrypted |
Failed to create a dump. Encryption is enabled for the OBS bucket. Disable the encryption and try again. |
Disable OBS bucket encryption and retry dump creation. |
|
400 |
LTS.0020 |
Current bucket is encrypted. |
Failed to modify a dump. Encryption is enabled for the OBS bucket. Disable the encryption and try again. |
Disable OBS bucket encryption and retry dump modification. |
|
400 |
LTS.0101 |
Failed to create log group, the log group name has been existed |
Failed to create log group. The log group name has already existed. |
Check the log group name to ensure it is unique. |
|
400 |
LTS.0102 |
Failed to create log group |
Failed to create log group. Failed to connect to database. |
Check the database connection. |
|
400 |
LTS.0103 |
Failed to delete log group |
Failed to delete log group. Failed to connect to database. |
Check the database connection. |
|
400 |
LTS.0104 |
Failed to create log group, the number of log groups exceeds the quota |
Failed to create log group, the number of log groups exceeds the quota. |
Increase the quota or reduce the number of log groups. |
|
400 |
LTS.0105 |
The log group is associated by transfer |
The log group is associated by transfer. Some log streams in the log group is associated by transfer. |
Check the transfer strategy associated with the log group. |
|
400 |
LTS.0106 |
The number of TTL days is out of range. |
The number of TTL days is out of range. |
Set the TTL days correctly. |
|
400 |
LTS.0107 |
Current user does not have the permission to operate this group. |
Failed to update the log group. |
Failed to connect to the database. Check the database instance status. |
|
400 |
LTS.0108 |
The log group is associated by agent conf |
Failed to delete log group. The log group contains the log stream of the created host access. |
Remove the log stream from the log group or delete the host access. |
|
400 |
LTS.0201 |
The log group does not existed. |
The log group does not existed. |
Verify the log group name or create a new log group. |
|
400 |
LTS.0202 |
Failed to create log stream. |
Failed to create log stream. Failed to connect to database. |
Check the database connection. |
|
400 |
LTS.0205 |
The log stream name has been existed |
The log stream name has been existed. |
Use a different log stream name. |
|
400 |
LTS.0206 |
Failed to create log stream, the number of log streams exceeds the quota |
Failed to create log stream, the number of log streams exceeds the quota. |
Increase the quota or reduce the number of log streams. |
|
400 |
LTS.0207 |
The log stream is associated by transfer. |
The log stream is associated by transfer. |
Check the transfer strategy associated with the log stream. |
|
400 |
LTS.0208 |
The log stream does not existed. |
The log stream does not existed. |
Verify the log stream name or create a new log stream. |
|
400 |
LTS.0209 |
The log stream is associated by agent conf. |
Failed to delete log stream. Host access has been configured for this log stream. |
Remove the host access configuration or delete the log stream. |
|
400 |
LTS.0402 |
Failed to delete transfer |
Failed to delete transfer strategy. Failed to connect to database. |
Check the database connection. |
|
400 |
LTS.0403 |
The topic is repeated with other transfer |
Failed to create transfer strategy, transfer is already associated. Failed to create transfer strategy because the log stream is already bound to another transfer strategy. |
Check the existing transfer strategy or use a different log stream. |
|
400 |
LTS.0405 |
The log transfer does not existed |
The transfer strategy does not exist. Failed to delete transfer strategy because the transfer strategy does not exist. |
Verify the transfer strategy name or create a new transfer strategy. |
|
400 |
LTS.0412 |
Failed to create transfer, prefix name is invalid. |
Failed to create transfer strategy. Failed to create transfer policy, log file prefix name is invalid. |
Use a valid log file prefix name. |
|
400 |
LTS.0413 |
Failed to create transfer, directory prefix name is invalid |
Failed to create transfer strategy. Failed to create transfer policy, the provided log folder prefix name is invalid. |
Use a valid log folder prefix name. |
|
400 |
LTS.0500 |
The system encountered an internal error. |
The system encountered an internal error. |
Contact support for assistance. |
|
400 |
LTS.0503 |
Failed to create agent conf. |
Failed to create collection path. The system encountered an internal error. |
Check the collection path configuration or system status. |
|
400 |
LTS.0505 |
Failed to delete agent conf. |
Failed to delete collection path. The system encountered an internal error. |
Verify the collection path existence or system status. |
|
400 |
LTS.0506 |
Failed to update agent conf. |
Failed to update collection path. The system encountered an internal error. |
Check the collection path configuration or system status. |
|
400 |
LTS.0511 |
Call icmgr exception. |
Failed to operate collection path. The system encountered an internal error. |
Verify the collection path configuration or system status. |
|
400 |
LTS.0601 |
params validator error. |
Parameter verification failed. |
Verify and correct the input parameters. |
|
400 |
LTS.0603 |
group or stream not exist |
The log group or log stream does not exist. |
Check the log group and log stream existence. |
|
400 |
LTS.0604 |
stream transfer exist |
Failed to create transfer because the log stream has been configured for transfer. |
Verify the log stream transfer configuration. |
|
400 |
LTS.0605 |
save transfer exist. |
Failed to save DIS transfer. Failed to connect to database. |
Check the DIS transfer configuration and database connection. |
|
400 |
LTS.0607 |
update transfer not exist. |
Failed to update DIS transfer configuration. Updating the DIS transfer configuration failed because the transfer configuration does not exist. |
Verify the existence of the DIS transfer configuration. |
|
400 |
LTS.0608 |
dis stream not exist. |
Failed to create or update DIS transfer. Failed to create or update DIS transfer because the DIS channel does not exist. |
Check the existence of the DIS channel. |
|
400 |
LTS.0610 |
dis stream auth failed. |
Failed to create or update DIS transfer. Failed to create or update DIS transfer because the user does not have permission to this DIS channel. |
Verify the user permissions for the DIS channel. |
|
400 |
LTS.0611 |
delete transfer id failed. |
Failed to delete DIS transfer. Failed to connect to database. |
Check the DIS transfer configuration and database connection. |
|
400 |
LTS.0612 |
%s fieldType is error |
Incorrect structured field type. |
Adjust the structured field type to match the data. |
|
400 |
LTS.0711 |
Log filter params validator error. |
Incorrect parameter settings. Modify the parameters and try again. |
Adjust the parameter settings and retry the operation. |
|
400 |
LTS.0721 |
Failed to delete lts ticket. |
Failed to operate the ES. |
Check Elasticsearch service status and configuration. |
|
400 |
LTS.0722 |
Log chart failed to store data in ES. |
Failed to operate the ETCD. |
Verify ETCD service availability and configuration. |
|
400 |
LTS.0751 |
custom template params validator error. |
Parameter verification failed. |
Verify and correct the input parameters. |
|
400 |
LTS.0752 |
The number of custom templates exceeds the maximum. |
The number of user-defined templates has reached the upper limit (50). |
Delete unused templates or increase the limit. |
|
400 |
LTS.0753 |
The number of fields in custom template exceeds the limit. |
The number of fields in the customized template exceeds the upper limit (1 to 200). |
Adjust the template to meet the field count requirements. |
|
400 |
LTS.0754 |
Custom template name already exist or in system templateName exist. |
The customized template name already exists. |
Use a unique name for the customized template. |
|
400 |
LTS.0755 |
Field name or userDefined name repeat. |
Duplicate field name. |
Ensure all field names are unique within the template. |
|
400 |
LTS.0756 |
FieldNames or userDefinedNames have internal fields. |
The field name or alias is the same as the built-in field. |
Rename the field to avoid conflicts with built-in fields. |
|
400 |
LTS.0757 |
Log custom template operation failed. |
Operation failed. |
Check system status and retry the operation. |
|
400 |
LTS.0901 |
The filter name has been existed |
The filter name has been existed. |
Use a unique filter name. |
|
400 |
LTS.0902 |
Failed to create log filter. |
Failed to create log filter. Failed to connect to database. |
Check the log filter configuration and database connection. |
|
400 |
LTS.0903 |
Failed to delete log filter. |
Failed to delete filter. Failed to connect to database. |
Check the filter configuration and database connection. |
|
400 |
LTS.0904 |
Failed to update log filter. |
Filter update failed. Failed to connect to database. |
Check the filter configuration and database connection. |
|
400 |
LTS.0906 |
The filter does not existed. |
Failed to delete or update filter. The filter does not exist. |
Verify the existence of the filter. |
|
400 |
LTS.0908 |
Failed to create statisticsRule report query. |
Failed to create statisticsRule report query. Failed to connect to database. |
Check the statistics rule configuration and database connection. |
|
400 |
LTS.0909 |
Failed to delete statisticsRule report query. |
Failed to delete statistical rule. Failed to connect to database. |
Check the statistical rule configuration and database connection. |
|
400 |
LTS.0910 |
Failed to update statisticsRule report query. |
Failed to update statistical rules. Failed to connect to database. |
Check the statistical rules configuration and database connection. |
|
400 |
LTS.0911 |
The filter is exceed. |
The number of filters has reached the upper limit. A single log stream can only have up to 5 filters. |
Reduce the number of filters or create a new log stream. |
|
400 |
LTS.0912 |
The metric name has been existed. |
The metric name has been existed. |
Use a unique metric name. |
|
400 |
LTS.1602 |
Failed to create search criteria, the number of search criteria exceeds the quota |
Create quick search failed. Max. quick searches per log stream: 200 |
Delete existing quick searches or use a new log stream. |
|
400 |
LTS.1603 |
The search criteria name already exists |
Create quick search failed. Quick search name already in use. |
Use a unique quick search name. |
|
400 |
LTS.1604 |
Failed to create search criteria record. |
Failed to create quick search. Failed to connect to database. |
Check the quick search configuration and database connection. |
|
400 |
LTS.1606 |
Search criteria record not existed. |
Failed to delete or update quick search. This quick search does not exist. |
Verify the existence of the quick search. |
|
400 |
LTS.1607 |
Failed to delete search criteria. |
Failed to delete quick search. Failed to connect to database. |
Check the quick search configuration and database connection. |
|
400 |
LTS.1702 |
Failed to create VPC channel. The system encountered an internal error. |
Failed to create VPC channel. The system encountered an internal error. |
Check the VPC channel configuration or system status. |
|
400 |
LTS.1703 |
Failed to obtain kafka instance. The system encountered an internal error. |
Failed to obtain kafka instance. The system encountered an internal error. |
Check the Kafka instance configuration or system status. |
|
400 |
LTS.1704 |
Failed to connect to kafka. The provided kafka password is empty. |
Failed to connect to kafka. The provided kafka password is empty. |
Provide a valid Kafka password. |
|
400 |
LTS.1706 |
Unable to send data to kafka. kafka topic does not exist. |
Unable to send data to kafka. kafka topic does not exist. |
Create the Kafka topic or verify the topic name. |
|
400 |
LTS.1707 |
Failed to connect to kafka. Kafka status is abnormal. |
Failed to connect to kafka. Kafka status is abnormal. |
Check the Kafka service status and configuration. |
|
400 |
LTS.1712 |
The length of the field is greater than 128 characters. |
dms instance registration failed. |
Verify DMS instance configuration and registration process. |
|
400 |
LTS.1719 |
kafka user or password wrong. |
Username or password is incorrect. |
Verify the username and password credentials. |
|
400 |
LTS.1720 |
kafka connection check failed |
Failed to connect to Kafka. |
Check Kafka connection parameters and service status. |
|
400 |
LTS.1722 |
list kafka topic error. |
Query Topic failed. |
Check Kafka topic existence and configuration. |
|
400 |
LTS.1723 |
kafka operation authorize failed. |
Kafka permission verification failed. |
Verify Kafka user permissions and access policies. |
|
400 |
LTS.1802 |
stream kafka transfer exist |
DMS dump has been configured for this topic. Replace the topic and try again. |
Use a different topic for DMS dump configuration. |
|
400 |
LTS.1803 |
kafka transfer topic exist. |
The topic has been configured for dms access. Please change the topic and try again. |
Select a new topic not configured for DMS access. |
|
400 |
LTS.1821 |
access type is label and host group type is windows. |
Failed to create the agency. |
Check IAM agency configuration and permissions. |
|
400 |
LTS.1822 |
access type is LABEL and labels is null. |
Failed to obtain the agency. |
Verify agency existence and access permissions. |
|
400 |
LTS.1823 |
access type is LABEL and host list is not null. |
The agency of user lts_admin_trust does not exist. |
Create the required agency for user lts_admin_trust. |
|
400 |
LTS.1824 |
access type is IP and labels is not null. |
The authorization period of user lts_admin_trust is not permanent. |
Adjust the agency authorization period to permanent. |
|
400 |
LTS.1825 |
DMS UserAccess role not exist |
The DMS UserAccess system policy does not exist. |
Create the required DMS UserAccess system policy. |
|
400 |
LTS.1826 |
access type or gost group type can not update. |
Failed to obtain the DMS UserAccess delegation authorization information. |
Verify DMS UserAccess delegation configuration. |
|
400 |
LTS.1827 |
Failed to get hostGroup list. |
Failed to add the DMS UserAccess authorization. |
Check DMS UserAccess authorization parameters and retry. |
|
400 |
LTS.2001 |
Failed to create alarm rule. |
Failed to create the alarm rule. |
Verify alarm rule parameters and retry creation. |
|
400 |
LTS.2002 |
Failed to delete alarm rule. |
Failed to delete the alarm rule. |
Check alarm rule existence and permissions. |
|
400 |
LTS.2003 |
Failed to update alarm rule. |
Failed to modify the alarm rule. |
Verify alarm rule parameters and retry modification. |
|
400 |
LTS.2004 |
The size of alarm rule has exceed the limit: 200. |
Max. number of rules reached. Delete rules that you no longer require and try again. |
Remove unused rules to create new ones. |
|
400 |
LTS.2005 |
Param is_css_sql is null or false, is_css_sql must be true. |
Incorrect alarm rule parameters. Modify the parameters and try again. |
Adjust the alarm rule parameters and retry. |
|
400 |
LTS.2006 |
Alarm rule name or Alarm rule alias has already exist. |
The rule name or original rule name exists. |
Use a unique rule name. |
|
400 |
LTS.2007 |
Alarm rule not exist. |
The alarm rule does not exist. |
Verify the existence of the alarm rule. |
|
400 |
LTS.2008 |
Find Alarm rule failed. |
Failed to obtain the alarm rule. |
Check alarm rule configuration and permissions. |
|
400 |
LTS.2009 |
User must have SMN service authority. |
You do not have the permissions required for SMN. |
Check SMN permissions or contact the administrator. |
|
400 |
LTS.2010 |
Topics cannot be empty. |
Select an SMN topic. |
Choose an existing SMN topic from the list. |
|
400 |
LTS.2011 |
Alarm rule invalid query frequency or invalid cron expression. |
Invalid query frequency or Invalid cron expression. |
Verify query frequency settings and cron expression syntax. |
|
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. |
Adjust query time range to be within 1 hour for frequencies under 5 minutes. |
|
400 |
LTS.2013 |
Notification rule get error. |
Check whether the notification rule exists. |
Verify the existence of the notification rule in the system. |
|
400 |
LTS.2014 |
Failed to create notification template. |
Create message template failed. Check whether the template name is already in use. |
Use a unique name for the message template. |
|
400 |
LTS.2015 |
Failed to delete notification template. |
Deletion failed. The current message template has been associated with a notification rule. |
Disassociate the template from notification rules before deletion. |
|
400 |
LTS.2024 |
The number of alarm rules to be updated is limited. |
Max. number of rules reached. Delete rules that you no longer require and try again. |
Remove unused rules to create new ones. |
|
400 |
LTS.2819 |
Failed to get hostGroup list. |
Failed to query the host group list. |
Check host group configuration and service 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