-
-
Save kapkaev/4619127 to your computer and use it in GitHub Desktop.
$ redis-cli | |
> config set stop-writes-on-bgsave-error no |
thanks!
Thanks!
Works!
Still works!
Great ! 👍
Thank you!
I encountered this issue and my senior was unreachable. I thought I was booked for the day, but this code helped me fix the issue in minutes.
++++
Thanks man !
CONFIG SET dbfilename temp.rdb
This is the way,
What u should be doing is :
# redis-cli 127.0.0.1:6379> CONFIG SET dir /data/tmp OK 127.0.0.1:6379> CONFIG SET dbfilename temp.rdb OK 127.0.0.1:6379> BGSAVE Background saving started 127.0.0.1:6379>
Please Make sure
/data/tmp
has enough disk space.
this is the way. Thank you for solving the root problem :)
Yep, this happing because current use does not have the permission to modify the "dump.rdb".
So, instead of creating a new RDB file, You can also give permission to old file(change the ownership of it).
In redis-cli enter:
config get dir
you will get "/usr/local/var/db/redis" (this is the location where redis writes the data)
go to this location using terminal
cd
cd /usr/local/var/db
Type this command(with our username):
sudo chown -R [username] db
This will change to owner.
This works for me.
Yep, this happing because current use does not have the permission to modify the "dump.rdb".
So, instead of creating a new RDB file, You can also give permission to old file(change the ownership of it).
In redis-cli enter:
config get dir
you will get "/usr/local/var/db/redis" (this is the location where redis writes the data)
go to this location using terminal
cd cd /usr/local/var/db
Type this command(with our username):
sudo chown -R [username] db
This will change to owner.
This works for me.
This worked with the addtion of stopping and starting redis
brew services stop redis
brew services start redis
Thanks, that great 👍
It was helped for me 👍
For me, my hard disk is out of space
Thanks it's work
Thank you!
Thanks!
that's what the command does
According to Redis documentation, this is recommended only if you don't have RDB snapshots enabled or if you don't care about data persistence in the snapshots.
"By default Redis will stop accepting writes if RDB snapshots are enabled (at least one save point) and the latest background save failed. This will make the user aware (in a hard way) that data is not persisting on disk properly, otherwise,strong text chances are that no one will notice and some disaster will happen."
https://stackoverflow.com/questions/19581059/misconf-redis-is-configured-to-save-rdb-snapshots
in addition, I want to say that such errors can appear if the radis server is accessible from outside. You need to configure the radis server to listen only localhost. To do this, in the /etc/redis/redis.conf file, change bind parameter to 127.0.0.1
nano /etc/redis/redis.conf
bing 127.0.0.1
After this:
netstat -lnp | grep redis
should show that redis listning 127.0.0.1 insteed 0.0.0.0:*
thank you from 2022
Thank you!
CONFIG SET dbfilename temp.rdb
This is the way,
What u should be doing is :
# redis-cli 127.0.0.1:6379> CONFIG SET dir /data/tmp OK 127.0.0.1:6379> CONFIG SET dbfilename temp.rdb OK 127.0.0.1:6379> BGSAVE Background saving started 127.0.0.1:6379>
Please Make sure
/data/tmp
has enough disk space.this is the way. Thank you for solving the root problem :)
i keep getting "ERR Changing directory: No such file or directory" im not that good with ubuntu and ideas why?
Thanks bro