@AOKP
I agree, upgrading to 3.0.5 will certainly not solve the issue, but does not hurt to try 
@AOKP Well, it persists it to HDD on shutdown. Maybe the server was forced shutdown, and redis didn't have time to save, or the save corrupted the db?
If it helps clarifying the issue - when I noticed the forum had crashed and database was gone I tried to use redis-cli to do a proper shutdown - I connected which worked fine and tried running commands - And I got no response to the commands like Redis normally gives.
In my case it's saved every 5 minutes onto disk, so I should have lost only 5 minutes, except if as you says, it saved corrupted db.
297] 08 Nov 02:19:36.116 * Background saving terminated with success
[297] 08 Nov 02:24:37.088 * 10 changes in 300 seconds. Saving...
[297] 08 Nov 02:24:37.091 * Background saving started by pid 4508
[4508] 08 Nov 02:24:37.114 * DB saved on disk
[4508] 08 Nov 02:24:37.115 * RDB: 0 MB of memory used by copy-on-write
[297] 08 Nov 02:24:37.192 * Background saving terminated with success
[297] 08 Nov 02:29:38.091 * 10 changes in 300 seconds. Saving...
[297] 08 Nov 02:29:38.092 * Background saving started by pid 4511
[4511] 08 Nov 02:29:38.110 * DB saved on disk
[4511] 08 Nov 02:29:38.110 * RDB: 0 MB of memory used by copy-on-write
[297] 08 Nov 02:29:38.193 * Background saving terminated with success
[297] 08 Nov 02:34:39.034 * 10 changes in 300 seconds. Saving...
[297] 08 Nov 02:34:39.035 * Background saving started by pid 4514
[4514] 08 Nov 02:34:39.059 * DB saved on disk
after corruption I connected to redis without issue but database structure was
instead of
Why don't you try AOF instead of RDB?
It can save every second, without any certain performance loss. The only disadvantage is that it uses more disk space.
yeah no problem for me using AOF, I need to set it in redis.conf ?
@Charly86 yep.
I'll check this thanks
Another idea would be to configure a cronjob running every X minutes, copying the database.
cp -R /var/lib/redis.rdb /root
Yeah I've already put a backup into /etc/cron.hourly as a fix
@pitaj My version is this:
web02:~$ redis-server -v
Redis server v=3.0.3 sha=00000000:0 malloc=jemalloc-3.6.0 bits=64 build=e1e08a07153b9ea1
@wellenreiter are you also a OVH user?
@AOKP not sure what you mean with OVH and I'm not the one who leased the host, but it's a linode server, so I assume it's a virtual machine
@wellenreiter OVH is an ISP, providing servers.
However, I can only assume that something is wrong with your Redis setup or servers.
Does anyone uses the Redis repo from Chris Lea?
@AOKP said:
@wellenreiter OVH is an ISP, providing servers.
However, I can only assume that something is wrong with your Redis setup or servers.
Then, why occurs the problem to a number of different installations in just a couple of days on systems that have run fine for month before?
Also as mentioned above, my redis configuration is 99.9% the default config
@wellenreiter as said. I am running Redis since May and never had a problem similar to this.
The whole case is indeed very strange...
It is really strange and if you count all the different installations mentioned here and in the thread 'lost all my data' I doubt, that it is related to the redis configuration
@wellenreiter but then again, why the issue appears also on different NodeBB versions?
Maybe really give the PPA Repo from Chris Lea a try or switch to MongoDB.
