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.
@mikep I used NodeBB 0.7.2, 0.8.x and now 0.9. 16GB DDR4 ECC RAM, Intel Xeon E5-2690v3, RAID10 Intel 750 NVMe.
I even had Redis 2.8.x running (current one is 3.0.5).
By the way, it means NodeBB or something else would have to make a "FLUSHDB" request, except it is a memory error.
@mikep said:
FYI I have had the same problem. I am using a digital ocean 4GB RAM/2CPU VPS with Ubuntu 14.04, nodebb 0.81 and redis 3.04, so I don't think that it is provider/config related.
mmmm, wait. That is almost exactly our dev forum setup. The only difference is nodebb .9
Lost two days of talk between devs and admins...
I had back this problem a 2nd time 2 days ago, I don't know if it's related but I was doing iptables FW settings on the VM, I had nodeBB running, and also redis and from my computer desktop redis desktop manager connected to DB.
Then I made a mistake in iptables, blocked all redis port (even local), saying nodebb unable to connect to redis (so as redis desktop manager) then when I openned back 6379 port, all data was gone, not sure if it's related, just an information.
