Error Code Manual
Last updated: 2025-03-10 22:14:24
Overview
PTS error codes mainly consist of two types:
Custom error codes generated by the engine when sending request packets.
Error codes passed through by the engine from protocols such as HTTP and gRPC.
Error codes only indicate a general category of error; to pinpoint the specific cause of an error, it is essential to see the detailed error information.
Engine-Customized Error Codes
Error codes customized by the engine, which are used to further categorize errors that may be caused by the script, such as an improperly set HTTP timeout (the default is 10 seconds) and a non-existent domain name, making it easier for you to troubleshoot issues.
Error Code | English Description | Error Code Definition |
999 | unkown | Common error code. For specific causes, see request samples and load generator engine logs. |
1010 | context deadline | Request timeout, typically accompanied by status code 1301, indicating a timeout condition. |
1100 | Specific DNS error message | Common error code for failed DNS queries. |
1101 | lookup: no such host | DNS domain name resolution error. |
1200 | Specific TCP error message | Common error code for requests that fail after a network connection has been successfully established. |
1201 | Specific TCP op error message | The request failed, and it did not use a TCP connection. |
1202 | connection reset by peer | The request failed, and the error occurred during a data read or write operation, after which the server closed the connection. This may be due to a server-side exception, high load, or other reasons. |
1203 | broken pipe | The request failed, and the error occurred during a data write operation, after which the server closed the connection. This may be due to a server-side exception, high load, or other reasons. |
1204 | Specific system call error message | The request failed, and the error originated from a system call. |
1210 | Specific dial error message | Common error code for failed network connection requests. |
1211 | unknown errno on with message | The request failed, and the error originated from an unrecognized system call. |
1212 | dial: i/o timeout | Network connection timeout |
1301 | request canceled | The request was canceled, typically due to a timeout, and in such cases, it usually occurs accompanied by the error code 1010. |
2000 | Specific error message | Database operation failed. |
2001 | Specific error message | The checkpoint result is False. |
Common HTTP Protocol Error Codes
Status Code | Status Code Name | Description |
100 | Continue | Continue. The client should proceed with its request. |
101 | Switching Protocols | Switch protocols. The server switches protocols as requested by the client. The switch can only be to a higher-level protocol, such as a newer version of HTTP. |
200 | OK | The request is successful. This is commonly used for GET and POST requests. |
201 | Created | Created. The request is successful and a new resource has been created. |
202 | Accepted | Accepted. The request has been accepted but it has not been completed yet. |
203 | Non-Authoritative Information | Non-authoritative information. The request is successful, but the returned meta information is from a copy, not the original server. |
204 | No Content | No content. The server successfully processes the request but does not return any content. This ensures the browser continues to display the current documentation without updating the webpage. |
205 | Reset Content | Reset content. The server successfully processes the request, and the user terminal (for example, the browser) should reset the documentation view. This return code can be used to clear form fields in a browser. |
206 | Partial Content | Partial content. The server successfully processes part of the GET request. |
300 | Multiple Choices | Multiple choices. The requested resource can be obtained from multiple locations, and the response may include a list of resource characteristics and addresses for the user terminal (such as browser) to choose from. |
301 | Moved Permanently | Moved permanently. The requested resource has been permanently moved to a new URI, the returned information will include the new URI, and the browser will automatically redirect to the new URI. Any future requests for this resource should use the new URI instead. |
302 | Found | Temporary movement. Similar to 301, but the resource is only temporarily moved. The client should continue to use the original URI. |
303 | See Other | View other addresses. Similar to 301. Use GET and POST requests to view. |
304 | Not Modified | Not modified. The requested resource has not been modified. When the server returns this status code, it will not return any resources. The client usually caches visited resources and provides a piece of header information indicating that the client only wants to return resources modified after the specified date. |
305 | Use Proxy | Use proxy. The requested resource should be accessed through a proxy. |
306 | Unused | Deprecated HTTP status code. |
307 | Temporary Redirect | Temporary redirect. Similar to 302. Use GET request to redirect. |
400 | Bad Request | Syntax error in client request. The server cannot understand. |
401 | Unauthorized | The request requires user identity authentication. |
402 | Payment Required | Reserved for future usage. |
403 | Forbidden | The server understands the client's request but refuses to execute it. |
404 | Not Found | The server cannot find the resource (web page) based on the client's request. With this code, website designers can set up a personalized page saying "The resource you requested cannot be found." |
405 | Method Not Allowed | The method in the client request is prohibited. |
406 | Not Acceptable | The server cannot fulfill the request based on the content characteristics requested by the client. |
407 | Proxy Authentication Required | The request requires proxy identity authentication. Similar to 401, but the requester should use a proxy for authorization. |
408 | Request Time-out | The server timed out while waiting for a request from the client. |
409 | Conflict | This code may be returned when the server completes the client's PUT request, indicating that a conflict occurred while processing the request. |
410 | Gone | The resource requested by the client no longer exists. Status code 410 differs from 404 in that 410 can be used if a resource that previously existed has now been permanently deleted. Website designers can specify the new location of the resource using a 301 status code. |
411 | Length Required | The server cannot process the request information without Content-Length sent by the client. |
412 | Precondition Failed | The precondition failed in the client's request information. |
413 | Request Entity Too Large | The server rejects the request because the requested entity is too large to process. To prevent continuous requests from the client, the server may close the connection. If the server is only temporarily unable to process the request, it will include a Retry-After response header. |
414 | Request-URI Too Large | The requested URL is too long (URLs are usually websites), and the server cannot process it. |
415 | Unsupported Media Type | The server cannot process the media format accompanying the request. |
416 | Requested range not satisfiable | The range requested by the client is invalid. |
417 | Expectation Failed | The server cannot meet the requirements of the Expect request header. |
500 | Internal Server Error | Internal server error occurs. Failed to complete the request. |
501 | Not Implemented | The server does not support the requested feature and cannot fulfill the request. |
502 | Bad Gateway | The server acting as a gateway or agency received an invalid response from the remote server while attempting to execute the request. |
503 | Service Unavailable | The server is temporarily unable to process the client's request due to overload or system maintenance. The length of the delay may be included in the server's Retry-After header information. |
504 | Gateway Time-out | The server acting as a gateway or agency did not receive a timely request from the remote server. |
505 | HTTP Version not supported | The server does not support the version of the requested HTTP protocol and cannot complete the processing. |
Common gRPC Protocol Error Codes
English Description | Status Code | Description |
OK | 0 | Not an error; returned upon success. |
CANCELLED | 1 | This operation is usually canceled by the caller. |
UNKNOWN | 2 | Unknown error. For example, this error may be returned when a Status value received from another address space belongs to an unknown error space in this address space. Additionally, errors raised by the API that do not return sufficient error information may be converted to this error. |
INVALID_ARGUMENT | 3 | The parameter specified by the client is invalid. Note that this is different from FAILED_PRECONDITION. INVALID_ARGUMENT indicates a parameter that is problematic regardless of the system status (such as an incorrectly formatted filename). |
DEADLINE_EXCEEDED | 4 | The expiration date has passed before the operation was completed. For operations that change the system status, this error may be returned even if the operation has been successfully completed. For example, a successful response from the server might have been delayed for a long time. |
NOT_FOUND | 5 | Some requested entities (for example, a file or directory) are not found. Note for server developers: If requests for an entire user category are denied, such as during a phased rollout of a feature or for unannounced allowlists, NOT_FOUND can be used. If requests from certain users within a category are denied, such as user-based access control, PERMISSION_DENIED should be used. |
ALREADY_EXISTS | 6 | The entity that the client is trying to create (for example, a file or directory) already exists. |
PERMISSION_DENIED | 7 | The caller does not have permissions to execute the specified operation. PERMISSION_DENIED cannot be used for denials caused by the exhaustion of some resources (for these errors, use RESOURCE_EXHAUSTED). If the caller cannot be identified, PERMISSION_DENIED should not be used (for those errors, use UNAUTHENTICATED). This error code does not imply that the request is valid, or that the requested entity exists or meets other preconditions. |
RESOURCE_EXHAUSTED | 8 | Some resources have been exhausted, which could be due to per-user quotas or insufficient space in the entire file system. |
FAILED_PRECONDITION | 9 | The operation is rejected because the system is not in the status required to perform the operation. For example, this could occur if the directory to be deleted is not empty, or if the rmdir operation is applied to a non-directory. Service implementers can use the following guidelines to decide between FAILED_PRECONDITION, ABORTED, and UNAVAILABLE: (a) If the client can retry the failed calling, use UNAVAILABLE. (b) If the client should retry at a higher level (for example, when a client-specified test-and-set fails, indicating the client should restart a read-modify-write sequence), use ABORTED. (c) If the client should not retry until the system status is explicitly fixed, use FAILED_PRECONDITION. For example, if a "rmdir" fails because the directory is not empty, FAILED_PRECONDITION should be returned because the client should not retry unless files are removed from the directory. |
ABORTED | 10 | The operation was aborted, typically due to concurrency issues such as a sequencer check failure or transaction abort. To determine whether to use FAILED_PRECONDITION, ABORTED, or UNAVAILABLE, see the guidelines above: |
OUT_OF_RANGE | 11 | The attempted operation is out of the valid range. E. For example, seeking or reading past the end of a file. Unlike INVALID_ARGUMENT, this error indicates an issue that can be fixed if the system status changes. For instance, requesting a 32-bit file system to read at an offset not within the [0, 2^32-1] range would yield an INVALID_ARGUMENT, whereas requesting a read operation at an offset beyond the current file size would result in an OUT_OF_RANGE. There is a slight overlap between FAILED_PRECONDITION and OUT_OF_RANGE. We recommend using OUT_OF_RANGE (the more specific error) when applicable, so that callers iterating over space can easily look for OUT_OF_RANGE errors to detect when they are done. |
UNIMPLEMENTED | 12 | This service does not implement or does not support/enable the operation. |
INTERNAL | 13 | Internal error. This indicates that some invariants expected by the underlying system have been broken. This error code is reserved for serious errors. |
UNAVAILABLE | 14 | The service is currently unavailable. This is most likely a transient condition that can be corrected by retrying after a rollback period. Note that retrying non-idempotent operations is not always secure. |
DATA_LOSS | 15 | Unrecoverable data loss or corruption. |
UNAUTHENTICATED | 16 | The request does not have valid authentication credentials for the operation. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No