You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2 days ago my host suspended my server for having "20k+ UNREPLIED conntrack sessions", when I contacted them they unsuspected it and I logged in to the server to find it rebooted. I started everything up, and noticed that the data redis was using was almost 4 months old (from when I first setup the server).
I had the default save config
save 900 1
save 300 10
save 60 10000
appendonly was off, but I've since turned it on with appendfsync everysec. locate *.rdb only finds the /var/lib/redis/dump.rdb and locate *.aof only finds the newly created /var/lib/redis/appendonly.aof
Checking the logs from a week ago up until 2 days ago when the server was suspended, I don't see any DB saved on disk in the logs like I do in my most recent one after re-setting everything up, it consists entirely of this:
10899:S 20 Jan 01:02:03.578 # Error condition on socket for SYNC: Connection refused
10899:S 20 Jan 01:02:04.434 * Connecting to MASTER IP:PORT
10899:S 20 Jan 01:02:04.435 * MASTER <-> SLAVE sync started
10899:S 20 Jan 01:02:04.583 # Error condition on socket for SYNC: Connection refused
10899:S 20 Jan 01:02:05.444 * Connecting to MASTER IP:PORT
10899:S 20 Jan 01:02:05.444 * MASTER <-> SLAVE sync started
with 1 10899:S 28 Jan 00:08:40.426 # Timeout connecting to the MASTER...
When re-setting everything up I did re-chown and re-chmod /var/lib/redis and dump.rdb so maybe that was the issue? or could have it of been something else?
The text was updated successfully, but these errors were encountered:
Hello @PCPisChill
1 It seems like your slave node have problem connecting your master node. So please check the slaveof IP:PORT and masterauth in redis.conf on your slave node.
2 The log information DB saved on disk will not show out at once when persistence is triggered. You can set loglevel debug for more information or read the source code: int rdbSave in rdb.c.
3 Usually persistence can be triggered by these items: new data\MASTER <-> SLAVE sync\exit in the correct way. So make sure that you have done at least one of them successfully.
Hope these would help a little.
2 days ago my host suspended my server for having "20k+ UNREPLIED conntrack sessions", when I contacted them they unsuspected it and I logged in to the server to find it rebooted. I started everything up, and noticed that the data redis was using was almost 4 months old (from when I first setup the server).
I had the default save config
appendonly was off, but I've since turned it on with
appendfsync everysec
.locate *.rdb
only finds the/var/lib/redis/dump.rdb
andlocate *.aof
only finds the newly created/var/lib/redis/appendonly.aof
Checking the logs from a week ago up until 2 days ago when the server was suspended, I don't see any
DB saved on disk
in the logs like I do in my most recent one after re-setting everything up, it consists entirely of this:with 1
10899:S 28 Jan 00:08:40.426 # Timeout connecting to the MASTER...
When re-setting everything up I did re-chown and re-chmod
/var/lib/redis
anddump.rdb
so maybe that was the issue? or could have it of been something else?The text was updated successfully, but these errors were encountered: