ArangoDB Manual

The following errors might be raised when running ArangoDB:

0: no error No error has occurred.
1: failed Will be raised when a general error occurred.
2: system error Will be raised when operating system error occurred.
3: out of memory Will be raised when there is a memory shortage.
4: internal error Will be raised when an internal error occurred.
5: illegal number Will be raised when an illegal representation of a number was given.
6: numeric overflow Will be raised when a numeric overflow occurred.
7: illegal option Will be raised when an unknown option was supplied by the user.
8: dead process identifier Will be raised when a PID without a living process was found.
9: not implemented Will be raised when hitting an unimplemented feature.
10: bad parameter Will be raised when the parameter does not fulfill the requirements.
11: forbidden Will be raised when you are missing permission for the operation.
12: out of memory in mmap Will be raised when there is a memory shortage.
13: csv is corrupt Will be raised when encountering a corrupt csv line.
400: bad parameter Will be raised when the HTTP request does not fulfill the requirements.
403: forbidden Will be raised when the operation is forbidden.
404: not found Will be raised when an URI is unknown.
405: method not supported Will be raised when an unsupported HTTP method is used for an operation.
500: internal server error Will be raised when an internal server is encountered.
600: invalid JSON object Will be raised when a string representation of a JSON object is corrupt.
601: superfluous URL suffices Will be raised when the URL contains superfluous suffices.
1000: illegal state Internal error that will be raised when the datafile is not in the required state.
1001: illegal shaper Internal error that will be raised when the shaper encountered a porblem.
1002: datafile sealed Internal error that will be raised when trying to write to a datafile.
1003: unknown type Internal error that will be raised when an unknown collection type is encountered.
1004: ready only Internal error that will be raised when trying to write to a read-only datafile or collection.
1005: duplicate identifier Internal error that will be raised when a identifier duplicate is detected.
1006: datafile unreadable Internal error that will be raised when the datafile is unreadable.
1100: corrupted datafile Will be raised when a corruption is detected in a datafile.
1101: illegal parameter file Will be raised if a parameter file is corrupted.
1102: corrupted collection Will be raised when a collection contains one or more corrupted datafiles.
1103: mmap failed Will be raised when the system call mmap failed.
1104: filesystem full Will be raised when the filesystem is full.
1105: no journal Will be raised when a journal cannot be created.
1106: cannot create/rename datafile because it already exists Will be raised when the datafile cannot be created or renamed because a file of the same name already exists.
1107: database is locked Will be raised when the database is locked by a different process.
1108: cannot create/rename collection because directory already exists Will be raised when the collection cannot be created because a directory of the same name already exists.
1200: conflict Will be raised when updating or deleting a document and a conflict has been detected.
1201: wrong path for database Will be raised when a non-existing directory was specified as path for the database.
1202: document not found Will be raised when a document with a given identifier or handle is unknown.
1203: collection not found Will be raised when a collection with a given identifier or name is unknown.
1204: parameter 'collection' not found Will be raised when the collection parameter is missing.
1205: illegal document handle Will be raised when a document handle is corrupt.
1206: maixaml size of journal too small Will be raised when the maximal size of the journal is too small.
1207: duplicate name Will be raised when a name duplicate is detected.
1208: illegal name Will be raised when an illegal name is detected.
1209: no suitable index known Will be raised when no suitable index for the query is known.
1210: unique constraint violated Will be raised when there is a unique constraint violation.
1211: geo index violated Will be raised when a illegale coordinate is used.
1212: index not found Will be raised when an index with a given identifier is unknown.
1213: cross collection request not allowed Will be raised when a cross-collection is requested.
1214: illegal index handle Will be raised when a index handle is corrupt.
1215: cap constraint already defined Will be raised when a cap constraint was already defined.
1216: document too large Will be raised when the document cannot fit into any datafile because of it is too large.
1217: collection must be unloaded Will be raised when a collection should be unloaded, but has a different status.
1218: collection type invalid Will be raised when an invalid collection type is used in a request.
1300: datafile full Will be raised when the datafile reaches its limit.
1500: query killed Will be raised when a running query is killed by an explicit admin command.
1501: %s Will be raised when query is parsed and is found to be syntactially invalid.
1502: query is empty Will be raised when an empty query is specified.
1503: runtime error '%s' Will be raised when a runtime error is caused by the query.
1504: number out of range Will be raised when a number is outside the expected range.
1510: variable name '%s' has an invalid format Will be raised when an invalid variable name is used.
1511: variable '%s' is assigned multiple times Will be raised when a variable gets re-assigned in a query.
1512: unknown variable '%s' Will be raised when an unknown variable is used or the variable is undefined the context it is used.
1520: unable to open collection '%s' Will be raised when one of the collections referenced in the query was not found.
1521: unable to read-lock collection %s Will be raised when a read lock on the collection cannot be acquired.
1522: too many collections Will be raised when the number of collections in a query is beyond the allowed value.
1530: document attribute '%s' is assigned multiple times Will be raised when a document attribute is re-assigned.
1540: usage of unknown function '%s' Will be raised when an undefined function is called.
1541: invalid number of arguments for function '%s' Will be raised when the number of arguments used in a function call does not match the expected number of arguments for the function.
1542: invalid argument type used in call to function '%s()' Will be raised when the type of an argument used in a function call does not match the expected argument type.
1550: invalid structure of bind parameters Will be raised when the structure of bind parameters passed has an unexpected format.
1551: no value specified for declared bind parameter '%s' Will be raised when a bind parameter was declared in the query but the query is being executed with no value for that parameter.
1552: bind parameter '%s' was not declared in the query Will be raised when a value gets specified for an undeclared bind parameter.
1553: bind parameter '%s' has an invalid value or type Will be raised when a bind parameter has an invalid value or type.
1560: invalid logical value Will be raised when a non-boolean value is used in a logical operation.
1561: invalid arithmetic value Will be raised when a non-numeric value is used in an arithmetic operation.
1562: division by zero Will be raised when there is an attempt to divide by zero.
1563: list expected Will be raised when a non-list operand is used for an operation that expects a list argument operand.
1569: FAIL(%s) called Will be raised when the function FAIL() is called from inside a query.
1570: no suitable geo index found for geo restriction on '%s' Will be raised when a geo restriction was specified but no suitable geo index is found to resolve it.
1600: cursor not found Will be raised when a cursor is requested via its id but a cursor with that id cannot be found.
1700: expecting <prefix>/user/<username> TODO
1701: cannot create user TODO
1702: role not found TODO
1703: no permission to create user with that role TODO
1704: user not found TODO
1705: cannot manage password for user TODO
1706: expecting POST <prefix>/session TODO
1707: expecting GET <prefix>/session/<sid> TODO
1708: expecting PUT <prefix>/session/<sid>/<method> TODO
1709: expecting DELETE <prefix>/session/<sid> TODO
1710: unknown session TODO
1711: session has not bound to user TODO
1712: cannot login with session TODO
1713: expecting GET <prefix>/users TODO
1714: expecting /directory/sessionvoc/<token> TODO
1715: directory server is not configured TODO
1800: invalid key declaration Will be raised when an invalid key specification is passed to the server
1801: key already exists Will be raised when a key is to be created that already exists
1802: key not found Will be raised when the specified key is not found
1803: key is not unique Will be raised when the specified key is not unique
1804: key value not changed Will be raised when updating the value for a key does not work
1805: key value not removed Will be raised when deleting a key/value pair does not work
1806: missing value Will be raised when the value is missing
1901: invalid graph Will be raised when an invalid name is passed to the server
1902: could not create graph Will be raised when an invalid name, vertices or edges is passed to the server
1903: invalid vertex Will be raised when an invalid vertex id is passed to the server
1904: could not create vertex Will be raised when the vertex could not be created
1905: could not change vertex Will be raised when the vertex could not be changed
1906: invalid edge Will be raised when an invalid edge id is passed to the server
1907: could not create edge Will be raised when the edge could not be created
1908: could not change edge Will be raised when the edge could not be changed
2000: unknown client error This error should not happen.
2001: could not connect to server Will be raised when the client could not connect to the server.
2002: could not write to server Will be raised when the client could not write data.
2003: could not read from server Will be raised when the client could not read data.
3100: priority queue insert failure Will be raised when an attempt to insert a document into a priority queue index fails for some reason.
3110: priority queue remove failure Will be raised when an attempt to remove a document from a priority queue index fails for some reason.
3111: priority queue remove failure - item missing in index Will be raised when an attempt to remove a document from a priority queue index fails when document can not be located within the index.
3312: (non-unique) hash index insert failure - document duplicated in index Will be raised when an attempt to insert a document into a non-unique hash index fails due to the fact that document is duplicated within that index.
3313: (non-unique) skiplist index insert failure - document duplicated in index Will be raised when an attempt to insert a document into a non-unique skiplist index fails due to the fact that document is duplicated within that index.
3200: hash index insertion warning - attribute missing in document Will be raised when an attempt to insert a document into a hash index is caused by the document not having one or more attributes which are required by the hash index.
3202: hash index update warning - attribute missing in revised document Will be raised when an attempt to update a document results in the revised document not having one or more attributes which are required by the hash index.
3211: hash index remove failure - item missing in index Will be raised when an attempt to remove a document from a hash index fails when document can not be located within that index.
3300: skiplist index insertion warning - attribute missing in document Will be raised when an attempt to insert a document into a skiplist index is caused by in the document not having one or more attributes which are required by the skiplist index.
3302: skiplist index update warning - attribute missing in revised document Will be raised when an attempt to update a document results in the revised document not having one or more attributes which are required by the skiplist index.
3311: skiplist index remove failure - item missing in index Will be raised when an attempt to remove a document from a skiplist index fails when document can not be located within that index.
3400: bitarray index insertion warning - attribute missing in document Will be raised when an attempt to insert a document into a bitarray index is caused by in the document not having one or more attributes which are required by the bitarray index.
3402: bitarray index update warning - attribute missing in revised document Will be raised when an attempt to update a document results in the revised document not having one or more attributes which are required by the bitarray index.
3411: bitarray index remove failure - item missing in index Will be raised when an attempt to remove a document from a bitarray index fails when document can not be located within that index.
3413: bitarray index insert failure - document attribute value unsupported in index Will be raised when an attempt to insert a document into a bitarray index fails due to the fact that one or more values for an index attribute is not supported within that index.

Error codes and meanings