Search monitoring: error codes

[ 1 Query error codes ] [ 2 Explanation for specific error codes ]

Query error codes

Error codes displayed in the table devo.internal.log.error are always composed of a letter and a number, as in the example below:

Q-1103001 → Q stands for query.

Number

The number indicates the error type. This number may be composed either of 3 or 7 digits.

Digit 1: Recoverability

Indicates the severity of the issue and informs whether it can be fixed or not.

Digit 1	Recoverable	Description

Digit 1	Recoverable	Description
`1`	NO	The error cannot be fixed.
`2`	MANUAL	The error requires manual action over another part of the system.
`3`	MAYBE	The error can be fixed in a medium-long amount of time.
`4`	YES	The error can be fixed immediately.

Digit 2-3: Kind

Kind of exception retrieved.

Digits 2-3	Kind	Description

Digits 2-3	Kind	Description
`00`	UNKNOWN	General error.
`01`	CONNECTION_ERROR	Connection error. It may be a transient issue.
`02`	EXTERNAL_ERROR	An error related to external factors, such as client’s code.
`03`	SYSTEM_RESOURCE	An error related to a system-wide resource, such as RAM or file handlers.
`04`	SECURITY_ERROR	An error related to a resource that requires additional security checks, such as signed queries.
`05`	QUERY_CANCELLED	Query cancelled by an external entity.
`06`	CONFIG_PARSING_ERROR	Format error on reading input resources, such as files, fields, decoding…
`07`	INTERNAL_ERROR	Internal error. This is not a transient issue, and can be induced by a non-deterministic event.
`08`	MISSING_RESOURCE	A resource required to execute the query is missing.
`09`	QUERY_LIMIT	Query limit reached (for example, maximum result rows, time, RAM…)
`10`	QUERY_PARSING_ERROR	Syntax error in the query, probably a missing or misspelled token. Includes errors found in static analysis performed after parsing (refinement order, unknown operations, operations with unexpected arguments…)
`11`	UNSUPPORTED_FEATURE	Unsupported or not implemented feature.

Digit 4-7: Specific error

The last 4 digits of the code are used to specify the detailed error of the exception. This detailed description is associated to the error type indicated by digits 2-3 explained above.

Digits 4-7	Description

Digits 4-7	Description
00 General error
`0000`	Unknown error.
01 Connection error
`4000`	`AFFINITY_RULES_CHANGED`: Affinity rules have changed during query execution and the query can no longer be processed.
03 System resource error
`1001`	`UNAVAILABLE_REGISTRY`: Required registry for a computation process is missing.
`1002`	`UNSUITABLE_REGISTRY`: Provided registry is not suitable for the required operation.
`1003`	`MEMORY_SHORTAGE`: Memory shortage.
04 Security error
`0001`	`AUTH_FAILED`: Authentication failed.
`0002`	`CANNOT_CHANGE_AUTH_FOR_ACTIVE_CLUSTER`: Cannot change authentication for active cluster.
06 Config parsing error
`4000`	`INVALID_SEGMENT_FILE`: Query is trying to access a file but cannot decode it.
07 Internal error
`0000`	`UNKNOWN_INTERNAL_ERROR`: Unknown internal error.
`0001`	`LOGFILE_LISTED_BUT_NOT_FOUND`: A listed file cannot be found in the directory, usually because it has been compressed simultaneously.
`0002`	`STALL_FOUND_IN_A_HOOK`: Stall event received while executing a subquery.
`4001`	`CANNOT_CREATE_ENTRY`: Error while caching data.
`4002`	`CANNOT_UPDATE_CACHE_DB`: Error while updating cached data.
`4003`	`CANNOT_DELETE_SEGMENTS`: Error while deleting cached data segments.
`4004`	`CANNOT_DELETE_ENTRY`: Error while deleting cached data entries.
`4005`	`INDEX_OUT_OF_BOUNDS`: Array index out of bounds.
08 Missing resource
`1000`	`MISSING_PREAGGREGATED_DATA`: Missing aggregated resource to execute the query (for example, an aggregation task).
`2000`	`RECURSIVE_UNION_TABLE`: Recursive definition for a union table.
`3000`	`MISSING_MAXMIND_FILES`: Missing files for Geolocation operations that use MaxMind.
`4000`	`MISSING_PUBLICSUFFIX_FILES`: Missing files for Public suffix operations.
`5000`	`MISSING_USERAGENT_FILES`: Missing files for User agent operations.
`6000`	`UNKNOWN_TABLE`: Unknown table.
09 Query limits
`0001`	`MAXIMUM_NUMBER_SURPASSED`: Maximum number of elements surpassed for the selected operation.
`0002`	`STACK_OVERFLOW`: Stack overflow while processing the query.
`0003`	`FAILED_TOO_MANY_TIMES`: Error limit reached. The query has failed n consecutive times and is quarantined for the following n minutes.
`0004`	`REGEX_OPERATIONS_SURPASSED`: Regular expression surpassed a safe limit
10 Query parsing error
`0001`	`ABSENT_LANGUAGE`: No language provided when parsing a query.
`0002`	`UNKNOWN_LANGUAGE`: Unknown query language.
`0003`	`ABSENT_CODE`: No code provided. This error relates to any kind of language, including expressions and Ty Terms.
`0004`	`NO_STARTING_TIME`: Query starting time no found.
`0005`	`NO_ENDING_TIME`: Query ending time no found.
`0006`	`CANNOT_PARSE_QUERY`: Cannot parse query.
`0007`	`ILLEGAL_TEMPORAL_GROUP_CLAUSE`: Illegal time-based grouping clause.
`0008`	`WRONG_TEMPORAL_GROUP`: Time-based group found over a non-time-based table or group.
`0009`	`FUTURE_TIME`: Inferred time constraint spans to the future.
`1001`	`UNKNOWN_ID`: Reference to an identifier (table field or as-defined) that is not known or available at that stage.
`1002`	`UNKNOWN_FUNCTION`: Unknown operation or known operation expecting arguments with other properties (type, constancy...)
`1003`	`REDEFINED_ID`: An identifier has been used more than once.
`1004`	`BOOLEAN_EXPECTED`: An expression with boolean type or a type that can by automatically converted to boolean was expected.
`1005`	`CONSTANT_ARGUMENT_EXPECTED`: The operation expects some arguments to be constant, but a non-constant expression was given.
`1006`	`INVALID_FILTER`: Invalid filter added to an operation.
`1007`	`UNKNOWN_FUNCTION_ARITY`: The operation cannot be used with one or several of the given arguments.
`1008`	`UNKNOWN_FUNCTION_TYPES`: The operation cannot be used with one or several of the given data types.
`1009`	`UNKNOWN_FUNCTION_ARGUMENTS`: The operation cannot be used with the given arguments.
`1010`	`UNKNOWN_FUNCTION_STAGE`: The operation cannot be called at stage 1.
`1011`	`AMBIGUOUS_OPERATION`: Given argument for the selected operation is ambiguous.
`3000`	`GROUP_KEY_WITHOUT_TYPE_INFO`: Grouping over a key correctly typed but with no computable tyre PR.
`3001`	`GROUP_KEY_WITHOUT_MEMORY_INFO`: Grouping over a key correctly typed but with no computable memory usage information.
`3002`	`GROUP_AGGR_WITHOUT_TYPE_INFO`: Grouping computing a correctly typed aggregation but with no computable tyre PR.
`3003`	`GROUP_AGGR_WITHOUT_MEMORY_INFO`: Grouping computing a properly typed aggregation but with no computable memory usage information.
`9000`	`INFERRED_TYPE_MISMATCH`: Inferred type does not match the explicit type given with the operation.

Explanation for specific error codes

Code	Recoverable (digit 1)	Kind (digit 2-3)	SpecificError (digits 4-7)	Detail

Code	Recoverable (digit 1)	Kind (digit 2-3)	SpecificError (digits 4-7)	Detail
`1000000`	NO	OTHER	UNKNOWN	Unknown internal error.
`1031001`	NO	SYSTEM_RESOURCE	UNAVAILABLE_REGISTRY	Required registry for a computation process is missing.
`1031002`	NO	SYSTEM_RESOURCE	UNSUITABLE_REGISTRY	Provided registry is not suitable for the required operation.
`1090001`	NO	QUERY_LIMIT	MAXIMUM_NUMBER_SURPASSED	Maximum number of elements surpassed for the selected operation.
`1100006`	NO	QUERY_PARSING_ERROR	CANNOT_PARSE_QUERY	Invalid filter added to an operation. Check your query carefully. Usually, this happens when the query is not syntactically correct (like missing a select statement)
`1101001`	NO	QUERY_PARSING_ERROR	UNKNOWN_ID	Reference to an identifier (table field or as-defined) that is not known or available at that stage. If you see this error in a my.synthesis table, check the availability of the underlying tables
`1101004`	NO	QUERY_PARSING_ERROR	BOOLEAN_EXPECTED	An expression with boolean type or a type that can by automatically converted to boolean was expected.
`1101005`	NO	QUERY_PARSING_ERROR	CONSTANT_ARGUMENT_EXPECTED	The operation expects some arguments to be constant, but a non-constant expression was given.
`1101008`	NO	QUERY_PARSING_ERROR	UNKNOWN_FUNCTION_TYPES	The operation cannot be used with one or several of the given data types. If you see this error in a my.synthesis table, check the availability of the underlying tables
`2014000`	MANUAL	CONNECTION_ERROR	AFFINITY_RULES_CHANGED	Affinity rules have changed during query execution and the query can no longer be processed.
`2040001`	MANUAL	SECURITY_ERROR	AUTH_FAILED	Authentication failed.
`2040002`	MANUAL	SECURITY_ERROR	CANNOT_CHANGE_AUTH_FOR_ACTIVE_CLUSTER	Cannot change authentication for active cluster.
`2064000`	MANUAL	CONFIG_PARSING_ERROR	INVALID_SEGMENT_FILE	Invalid cached data.
`2074004`	MANUAL	INTERNAL_ERROR	CANNOT_DELETE_ENTRY	Error while deleting cached data.
`2081000`	MANUAL	MISSING_RESOURCE	MISSING_PREAGGREGATED_DATA	Missing aggregated resource to execute the query (for example, an aggregation task).
`2082000`	MANUAL	MISSING_RESOURCE	RECURSIVE_UNION_TABLE	Recursive definition for a union table.
`2083000`	MANUAL	MISSING_RESOURCE	MISSING_MAXMIND_FILES	Missing files for Geolocation operations that use MaxMind
`2084000`	MANUAL	MISSING_RESOURCE	MISSING_PUBLICSUFFIX_FILES	Missing files for Public suffix operations.
`2085000`	MANUAL	MISSING_RESOURCE	MISSING_USERAGENT_FILES	Missing files for User agent operations.
`2086000`	MANUAL	MISSING_RESOURCE	UNKNOWN_TABLE	Unknown table.
`3031003`	MAYBE	SYSTEM_RESOURCE	MEMORY_SHORTAGE	Insufficient memory to continue the execution of the query.
`4014001`	YES	CONNECTION_ERROR	NO_CANDIDATE_SUITABLE	Affinity rules have changed during query execution and the query can no longer be processed.
`4070001`	YES	INTERNAL_ERROR	LOGFILE_LISTED_BUT_NOT_FOUND	A listed file cannot be found in the directory, usually because it has been compressed simultaneously.

Devo Additional Documentation