redis
Redis Errors
Error type prefixes returned by the Redis server. Each error response begins with an uppercase word identifying the error type, followed by a human-readable message.
16 codes
· All codes 16 codes
- ASK Ask Redirect The key's hash slot is being migrated to another node. The client should send ASKING to the specified node and retry the command there, but should not update its slot map.
- BUSYKEY Destination Key Busy The destination key already exists. Returned by commands such as COPY or RENAME when the target key is occupied and no REPLACE flag is given.
- CLUSTERDOWN Cluster Down The cluster is down or unable to reach a quorum of master nodes. Commands cannot be served until the cluster recovers.
- CROSSSLOT Cross-slot Keys The command references keys that hash to different cluster slots. Multi-key commands in cluster mode require all keys to reside in the same slot.
- ERR Generic Error Generic error prefix for unrecognised commands, wrong argument counts, or general failures not covered by a more specific error type.
- EXECABORT Transaction Aborted EXEC aborted because watched keys were modified since WATCH was called, or because a command in the MULTI block had an error.
- LOADING Loading Dataset The server is loading the dataset from disk after a restart and is not yet ready to serve requests.
- MOVED Key Moved In cluster mode, the key's hash slot is served by a different node. The response includes the slot number and the address of the responsible node. The client should redirect and retry.
- NOAUTH Authentication Required The server requires authentication. The client must issue AUTH before sending any other commands.
- NOPERM No Permission The authenticated user does not have permission to execute the command. Controlled by Redis ACL rules.
- NOSCRIPT No Script EVALSHA was called with a SHA1 digest that does not correspond to any script loaded on the server. Use SCRIPT LOAD to load the script first.
- NOTBUSY Not Busy SCRIPT KILL or FUNCTION KILL was called but no script or function is currently executing.
- OOM Out of Memory Server has reached its maxmemory limit and the configured eviction policy does not allow new writes to proceed.
- READONLY Read Only Replica A write command was sent to a read-only replica. Redirect write commands to the master node.
- TRYAGAIN Try Again A multi-key command could not be executed atomically because the involved slots are being migrated. Retry after a brief delay.
- WRONGTYPE Wrong Type Command issued against a key holding the wrong data type. For example, calling LPUSH on a key that holds a string.