ArangoErrorNum

This maintenance action cannot be stopped once it is started

This maintenance action is still processing

Will be raised if the readDB or the spearHead cannot be rebuilt from the replicated log.

The inform message in the Agency must be an object.

The inform message in the Agency must contain an array 'active'.

The inform message in the Agency must contain a string parameter 'id'.

The inform message in the Agency must contain an object 'max ping'.

The inform message in the Agency must contain an object 'min ping'.

The inform message in the Agency must contain an object 'pool'.

The inform message in the Agency must contain a uint parameter 'term'.

The inform message in the Agency must contain an object 'timeoutMult'.

Malformed gossip message.

Malformed inquire request.

Malformed agency transaction.

During the execution of an AIR program an error occurred

Will be raised when parsing an attribute name definition failed.

Will be raised when storage engine is busy.

Will be raised when the collection cannot be created because a directory of the same name already exists.

Will be raised when a collection is accessed that is not yet loaded.

Will be raised when a collection should be unloaded, but has a different status.

Will be raised when the collection parameter is missing.

Will be raised when an invalid collection type is used in a request.

Will be raised when a collection has a different type from what has been expected.

Will be raised when updating or deleting a document and a conflict has been detected.

Will be raised when a collection contains one or more corrupted data files.

Will be raised when a corruption is detected in a datafile.

Will be raised when a cross-collection is requested.

Will be raised when an invalid database name is used.

Will be raised when a non-existing database is accessed.

Will be raised when a non-existing database directory was specified when starting the database.

Will be raised when the database directory is locked by a different process.

Will be raised when the server's database directory is not writable for the current user.

Will be raised when the server cannot lock the database directory on startup.

Will be raised when the datafile cannot be created or renamed because a file of the same name already exists.

Internal error that will be raised when a datafile is empty.

Will be raised when the datafile reaches its limit.

Internal error that will be raised when trying to write to a datafile.

Will be raised when a required datafile statistics object was not found.

Internal error that will be raised when a datafile is unreadable.

Will be raised when a collection or View with the given identifier or name is unknown.

Will be raised when a document identifier is corrupt.

Will be raised when a document key is corrupt.

Will be raised when a document key is missing.

Will be raised when a user-defined document key is supplied for collections with auto key generation.

Will be raised when a document with a given identifier is unknown.

Will be raised when a document revision is corrupt or is missing where needed.

Will be raised when the document cannot fit into any datafile because of it is too large.

Will be raised when there is an attempt to create a document with an invalid type.

Internal error that will be raised when a identifier duplicate is detected.

Will be raised when a name duplicate is detected.

Will be raised when encountering an empty server database directory.

Will be raised when the filesystem is full.

will be raised if icu operations failed

Will be raised when an illegal name is detected.

Will be raised if a parameter file is corrupted or cannot be read.

Internal error that will be raised when the datafile is not in the required state.

Will be raised by the storage engine when a read cannot be completed.

Will be raised when an attempt to create an index has failed.

Will be raised when a index identifier is corrupt.

Will be raised when an index with a given identifier is unknown.

will be raised when the _from or _to values of an edge are undefined or contain an invalid value.

Will be raised when an invalid key generator description is used.

Will be raised when storage engine encounters an I/O error.

Will be raised when the maximal size of the journal is too small.

Will be raised when storage engine has a datafile merge in progress and cannot complete the operation.

Will be raised when the system call mmap failed.

Will be raised when the system call msync failed.

Will be raised when no suitable index for the query is known.

Will be raised when a journal cannot be created.

Will be raised when a key generator runs out of keys.

Internal error that will be raised when trying to write to a read-only datafile or collection.

Will be raised when an error occurred during WAL log file recovery.

Will be raised when the server waited too long for a datafile to be synced to disk.

Will be raised when an operation should be retried.

Will be raised when there is a unique constraint violation.

Will be raised when an operation is requested in a database other than the system database.

Will be raised when the server is write-throttled and a write operation has waited too long for the server to process queued operations.

The hot backup set cannot be restored on non matching cluster topology

Will be raised when the parameter does not fulfill the requirements.

Will be raised when an attempt to create a directory fails.

Will be raised when an attempt to create a temporary file fails.

This smart collection cannot be dropped, it dictates sharding in the graph.

Will be raised when an attempt is made to overwrite an existing file.

Will be raised when a file cannot be read.

Will be raised when a file cannot be written.

Will be raised if after various retries an Agency operation could not be performed successfully.

Will be raised if a collection needed during query execution is out of sync. This currently can only happen when using SatelliteCollections

Will be raised if the internal communication of the cluster for AQL produces an error.

Will be raised if a required DB-Server can't be reached.

Will be raised if one tries to create a collection with a distributeShardsLike attribute which points to another collection that also has one.

Will be raised when a Coordinator in a cluster loses an HTTP connection to a DB-Server in the cluster whilst transferring data.

Will be raised when a Coordinator in a cluster notices that some DB-Servers report problems when creating shards for a new collection.

Will be raised when a Coordinator in a cluster cannot create an entry for a new collection in the Plan hierarchy in the Agency.

Will be raised when a Coordinator in a cluster notices that some DB-Servers report problems when creating databases for a new cluster wide database.

Will be raised when a Coordinator in a cluster cannot create an entry for a new database in the Plan hierarchy in the Agency.

Will be raised when a Coordinator in a cluster cannot create an entry for a new index in the Plan hierarchy in the Agency.

Will be raised when a Coordinator in a cluster cannot create an entry for a new View in the Plan hierarchy in the Agency.

Will be raised when a Coordinator in a cluster cannot drop a collection entry in the Plan hierarchy in the Agency.

Will be raised if a follower that ought to be dropped could not be dropped in the Agency (under Current).

Will be raised when a Coordinator in a cluster cannot remove an index from the Plan hierarchy in the Agency.

Plan could not be modified while creating or deleting Analyzers revision

Will be raised when a Coordinator in a cluster cannot remove an entry for a collection in the Plan hierarchy in the Agency.

Will be raised when a Coordinator in a cluster cannot remove an entry for a database in the Current hierarchy in the Agency.

Will be raised when a Coordinator in a cluster cannot remove an entry for a database in the Plan hierarchy in the Agency.

Will be raised if a Coordinator cannot truncate all shards of a cluster collection.

Will be raised when updating the plan on collection creation failed.

Will be raised when a follower transaction has already performed an intermediate commit and must be rolled back.

Will be raised if a Coordinator in a cluster gets conflicting results from different shards, which should never happen.

Will be raised if one tries to create a collection with a replicationFactor greater than the available number of DB-Servers.

Will be raised when servers are currently competing for leadership, and the result is still unknown.

Will be raised if there is an attempt to update the value of a shard attribute.

Will be raised if there is an attempt to update the value of the smartJoinAttribute.

Will be raised if one tries to drop a collection to which another collection points with its distributeShardsLike attribute.

Will be raised when a Coordinator in a cluster finds that the _key attribute was specified in a sharded collection the uses not only _key as sharding attribute.

Will be raised if a Coordinator tries to find out which shard is responsible for a partial document, but cannot do this because not all sharding attributes are specified.

Will be raised when an operation is sent to a non-leading server.

Will be raised if there is an attempt to run a Coordinator-only operation on a different type of node.

Will be raised if there is an attempt to run a DB-Server-only operation on a different type of node.

Will be raised if a Coordinator or DB-Server cannot read the Plan in the Agency.

General error during cluster repairs

Will be raised if a collection that is fixed does (not) have distributeShardsLike when it is expected, or does (not) have repairingDistributeShardsLike when it is expected

Will be raised if a move shard job in the Agency cannot be found anymore before it finished

Will be raised if a move shard job in the Agency failed during cluster repairs

Will be raised if a shard in collection and its prototype in the corresponding distributeShardsLike collection don't have the same followers (when they should already have been adjusted)

Will be raised if a shard in collection and its prototype in the corresponding distributeShardsLike collection have mismatching leaders (when they should already have been fixed)

Will be raised if in a collection and its distributeShardsLike prototype collection some shard and its prototype have an unequal number of DB-Servers

Will be raised when, during repairDistributeShardsLike, there must be a free DB-Server to move a shard, but there is no candidate or none is healthy.

Will be raised if a collection that is fixed has some shard without DB-Servers

Will be raised if an agency transaction failed during either sending or executing it.

Will be raised on various inconsistencies regarding the replication factor

Will be raised on some occasions when one server gets a request from another, which has not (yet?) been made known via the Agency.

Will be raised if a non-replication operation is refused by a shard follower.

Will be raised when a Coordinator in a cluster cannot determine the shard that is responsible for a given document.

Will be raised if a replication operation is refused by a shard leader.

Will be raised if a non-replication operation is refused by a former shard leader that has found out that it is no longer the leader.

Will be raised when a Coordinator in a cluster runs into a timeout for some cluster wide operation.

Will be raised when the number of shards for a collection is higher than allowed.

Will be raised if one tries to create a collection which points to an unknown collection in its distributeShardsLike attribute.

Will be raised when there is an attempt to carry out an operation that is not supported in the context of a sharded collection.

Will be raised when a Coordinator in a cluster tries to create a View and the View ID already exists.

Will be raised when encountering a corrupt csv line.

Will be raised when a cursor is requested via its id but a concurrent request is still using the cursor.

Will be raised when a cursor is requested via its id but a cursor with that id cannot be found.

Will be raised when a deadlock is detected when accessing collections.

Will be raised when a PID without a living process was found.

Will be raised intentionally during debugging.

Will be raised when a requested resource is not enabled.

Will be raised when a general error occurred.

Failed to download hot backup set from remote source

Failed to upload hot backup set to remote target

Will be raised when a file already exists.

Will be raised when a file is not found.

Will be raised when you are missing permission for the operation.

the collection is used as the initial collection of this graph and is not allowed to be removed manually.

the orphan list argument is malformed. It has to be an array of strings.

the collection used as a relation is existing, but is a document collection, it cannot be used here.

The requested graph has no edge collections.

The _graphs collection contains invalid data.

Will be raised when an invalid edge id is passed to the server.

Will be raised when an invalid filter result is returned in a graph traversal.

Will be raised when an invalid name is passed to the server.

during the graph creation process no collection could be selected as the needed initial collection. Happens if a distributeShardsLike or replicationFactor mismatch was found.

the _from or _to collection specified for the edge refers to a vertex collection which is not used in any edge definition of the graph.

Will be raised when too many iterations are done in a graph traversal.

Conflict of multiple hot backup processes.

One or more DB-Servers could not be reached for hot backup inquiry

Failed to create hot backup set

Failed to restore to hot backup set

Will be raised when the HTTP request does not fulfill the requirements.

Will be raised when a conflict occurs in an HTTP operation.

Will be raised when a string representation of a JSON object is corrupt.

Will be raised when the operation is forbidden.

Will be raised when a service contacted by ArangoDB does not respond in a timely manner.

Will be raised when the requested content has been permanently deleted.

Will be raised when an unsupported HTTP method is used for an operation.

Will be raised when an unsupported HTTP content type is used for an operation, or if a request is not acceptable for a leader or follower.

Will be raised when an URI is unknown.

Will be raised when an API is called this is not implemented in general, or not implemented for the current setup.

Will be raised when a precondition for an HTTP request is not met.

Will be raised when a timeout occured.

Will be raised when an internal server is encountered.

Will be raised when a service is temporarily unavailable.

Will be raised when the URL contains superfluous suffices.

Will be raised when authorization is required but the user is not authorized.

Will be raised when an illegal representation of a number was given.

Will be raised when an unknown option was supplied by the user.

The given smartGraph attribute is illegal and cannot be used for sharding. All system attributes are forbidden.

Will be raised when a server is running an incompatible version of ArangoDB.

An AQL block did not copy its input registers

Will be raised when an internal error occurred.

Internal error during AQL execution

Will be raised if there is an attempt to create an edge between separated graph components.

The service options contain invalid values.

The service mountpath contains invalid characters.

The service manifest contains invalid values.

Will be raised when the smartJoinAttribute declaration is invalid.

Will be raised when the structure of an IP address is invalid.

In a smart vertex collection _key must be prefixed with the value of the SmartGraph attribute.

when using smartJoinAttribute for a collection, the shard key value must be prefixed with the value of the SmartJoin attribute.

can not bind to a LDAP server

can not init a LDAP connection

can not search the LDAP server

can not set a LDAP option

can not star a TLS LDAP session

can not unbind from a LDAP server

LDAP didn't found any objects with the specified search query

cant distinguish a valid mode for provided LDAP configuration

LDAP found zero ore more than one user

LDAP returned an operations error

LDAP found a user, but its not the desired one

Some of the DB-Servers cannot be reached for transaction locks.

Some of the DB-Servers cannot be reached for transaction locks.

Will be raised when a resource or an operation is locked.

Will be raised when there's a timeout waiting for a lock.

Will be raised when a JSON string could not be parsed.

The service manifest file is not well-formed JSON.

Failed to invoke the module in its context.

The module path could not be resolved.

The module could not be parsed because of a syntax error.

Will be raised when hitting an unimplemented feature.

No error has occurred.

The requested collection needs to be smart, but it ain't

The given document does not have the SmartGraph attribute set.

The given document does not have the required SmartJoin attribute set or it has an invalid value.

No space left on device

No such maintenance action exists

Cannot find a hot backup set with this Id

Will be raised when a numeric overflow occurred.

Will be raised when an Enterprise Edition feature is requested from the Community Edition.

Will be raised when there is a memory shortage.

Will be raised when there is a memory shortage.

Will be raised when collection data are accessed after a data-modification operation.

Will be raised when a non-array operand is used for an operation that expects an array argument operand.

Will be raised when an HTTP API for a query got an invalid JSON object.

Will be raised when the structure of bind parameters passed has an unexpected format.

Will be raised when a bind parameter was declared in the query but the query is being executed with no value for that parameter.

Will be raised when a bind parameter has an invalid value or type.

Will be raised when a value gets specified for an undeclared bind parameter.

Will be raised when a read lock on the collection cannot be acquired.

Will be raised when an AQL data-modification query contains options that cannot be figured out at query compile time.

Will be raised when a dynamic function call is made to a function that cannot be called dynamically.

Will be raised when there is an attempt to divide by zero.

Will be raised when an empty query is specified.

Will be raised when the function FAIL() is called from inside a query.

Will be raised when forceIndexHint is specified, and the hint cannot be used to serve the query.

Will be raised when a fulltext query is performed on a collection without a suitable fulltext index.

Will be raised when the number of arguments used in a function call does not match the expected number of arguments for the function.

Will be raised when the type of an argument used in a function call does not match the expected argument type.

Will be raised when a user function is registered with invalid code.

Will be raised when a user function with an invalid name is registered.

Will be raised when an undefined function is called.

Will be raised when a user function is accessed but not found.

Will be raised when a user function throws a runtime exception.

Will be raised when a geo restriction was specified but no suitable geo index is found to resolve it.

Will be raised when an AQL query contains an invalid aggregate expression.

Will be raised when a non-numeric value is used in an arithmetic operation.

Will be raised when a value cannot be converted to a date.

Will be raised when a geo index coordinate is invalid or out of range.

Will be raised when an invalid regex argument value is used in a call to a function that expects a regex.

Will be raised when a running query is killed by an explicit admin command.

Will be raised when an AQL query contains more than one data-modifying operation.

Will be raised when an Id of a query is not found by the HTTP API.

Will be raised when a number is outside the expected range.

Will be raised when query is parsed and is found to be syntactically invalid.

Will be raised when a runtime error is caused by the query.

Will be raised when the number of collections or shards in a query is beyond the allowed value.

Will be raised if and user provided expression fails to evaluate to true

Will be raised if and user provided expression fails to evaluate to true

Will be raised when an invalid variable name is used.

Will be raised when an unknown variable is used or the variable is undefined the context it is used.

Will be raised when a variable gets re-assigned in a query.

Will be raised when a window node is created after a data-modification operation.

Will be returned if a queue with this name is full.

The configuration given for upload or download operation to/from remote hot backup repositories is wrong.

Special error code used to indicate the replication applier was stopped by a user.

Will be raised when the configuration for the replication applier is invalid.

Will be raised when an invalid replication applier state file is found.

Will be raised when the replication applier receives an invalid response from the leader.

Will be raised when the replication applier connects to a different leader than before.

Will be raised when the replication applier receives a server error from the leader.

Will be raised when the replication applier connects to a leader that has an incompatible version.

Will be raised when the replication applier is asked to connect to itself for replication.

Will be raised when the replication applier does not receive any or an incomplete response from the leader.

Will be raised when the replication applier is started without a known start tick value.

Will be raised when there is an attempt to perform an operation while the replication applier is running.

Will be raised when a shard is not empty and the follower tries a shortcut

Will be raised when the replication applier fetches data using a start tick, but that start tick is not present on the logger server anymore.

Will be raised when an unexpected marker is found in the replication log stream.

Will be raised when an unexpected transaction id is found.

Will be raised when a new born follower submits a wrong checksum

Will be raised when a request is canceled by the user.

Will be raised when the resources used by an operation exceed the configured maximum value.

The API for managing Foxx services has been disabled on this server.

Will be raised when a service download from the central repository failed.

The service folder or bundle does not exist on this server.

The local service bundle does not match the checksum in the database.

The service directory does not contain a manifest file.

A service already exists at the given mountpath.

The service is missing configuration or dependencies.

No service found at the given mountpath.

The service options are not well-formed JSON.

The source path could not be resolved.

The source path does not match a file or directory.

The service does not have a script with this name.

Will be raised when a service upload from the client to the ArangoDB server failed.

Will be raised when a session is expired.

Will be raised when an invalid/unknown session id is passed to the server.

Will be raised when a call cannot succeed because a server shutdown is already in progress.

Will be raised when the client could not connect to the server.

Will be raised when the client could not read data.

Will be raised when the client could not write data.

This error should not happen.

The SmartGraph attribute of the given collection does not match the SmartGraph attribute of the graph.

General supervision failure.

Will be raised when operating system error occurred.

Will be raised when a task id is created with a duplicate id.

Will be raised when a task is created with an invalid id.

Will be raised when a task with the specified id could not be found.

Will be raised when a transaction was aborted.

Will be raised when a disallowed operation is carried out in a transaction.

Will be raised when a wrong usage of transactions is detected. this is an internal error and indicates a bug in ArangoDB.

Will be raised when transactions are nested.

Will be raised when a transaction was not found.

Will be raised when a collection is used in the middle of a transaction but was not registered at transaction start.

Will be raised when a type error is encountered.

Will be raised when a user name already exists.

Will be raised when the user is authenticated by an external server.

Will be raised when an invalid user name is used.

Will be raised when a user name is updated that does not exist.

Will be raised when the schema description is invalid.

Will be raised when a document does not pass schema validation.

Will be raised if was erlaube?!

An AQL block wrote in a register that is not its output

An AQL block wrote an output register twice

An AQL block wrote too few output registers

An AQL block wrote too many output registers