MISCONF: MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk
RedisWhat does it mean?
Redis is configured to take RDB snapshots but cannot write to disk. In this state, if stop-writes-on-bgsave-error is enabled, Redis rejects all write commands.
Why does it happen?
A full disk, file system permission problems, a non-writable directory, background save (BGSAVE) errors, fork failure due to insufficient memory, or a disk hardware problem.
How to fix it
Free up disk space and check write permission on the RDB directory (dir). Inspect the latest BGSAVE error: INFO persistence and the Redis logs. To temporarily allow writes until the problem is fixed, stop-writes-on-bgsave-error no can be set (mind the durability risk). Ensure sufficient memory for fork and the vm.overcommit_memory=1 setting. Verify the persistence configuration (save/appendonly).
More from this engine
- CLUSTERDOWNCLUSTERDOWN The cluster is down / Hash slot not served
- LOADINGLOADING Redis is loading the dataset in memory
- BUSYBUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE
- CROSSSLOTCROSSSLOT Keys in request don't hash to the same slot
- MOVEDMOVED slot ip:port (cluster redirect)
- ASKASK slot ip:port (cluster redirect)
- NOSCRIPTNOSCRIPT No matching script. Please use EVAL