How to export from Redis to MongoDB? (My database got wiped)

Pilvinen

Here is /etc/redis/redis.conf:
http://pastie.org/private/rehppriwl3yfgcmkk4gtq

And it would be a lot more productive to say exactly which configs instead of "all of them" since I'm not power user - I don't know what you're talking about.

Like I said I have default settings except those which I've configured through ACP.

So tell me the config file names and paths and I'll see what I can pull up.

<baris>

Also post the output of free -m, make sure you have enough ram and swap enabled.

Pilvinen

free -m:

             total       used       free     shared    buffers     cached
Mem:         32141      29098       3043       3527        621      11891
-/+ buffers/cache:      16585      15555
Swap:         1025         37        988

? Offline

@Pilvinen I hope you have a password for Redis...
Otherwise I haven't found any issue.

What you can also try is the following:
service redis-server stop
apt-get remove redis*
apt-get purge redis*

apt-get install redis-server

So you have a fresh reinstall.

Pilvinen

@AOKP said:

@Pilvinen I hope you have a password for Redis...
Otherwise I haven't found any issue.

Well, since you can only connect to the database from the local machine I don't really see the point. If someone would compromise my system so far that they have access to the server's account then password protecting the database wouldn't really help at that point.

? Offline

@Pilvinen my config also is bind only to localhost, but I still can access it from the outter world.
Otherwise change the log level to debug as well.

Pilvinen

@AOKP said:

@Pilvinen my config also is bind only to localhost, but I still can access it from the outter world.

What... ? Why? How? What do you mean? Why would it accept connections from the outside? That makes no sense.

Pilvinen

I don't really see why it would accept connections from the outside - but since you scared me like that I have now password protected my database...

Bri

If there's no firewall it's completely possible

rbeer

Hi @Pilvinen

I hope you didn't purge redis, already. That could have deleted the log file, as well.

I'm curious about the contents of two files:

/var/log/redis/redis-server.log
/path/to/nodebb/log/nodebb.log

Like all the others, I suspect redis itself to be the source of failure here. NodeBB uses the DB's flush (wipe all data) only in its tests; even there on a test-databse you'd have to set up explicitly.

wellenreiter

@Kowlin I had exactly the same problem today.
overnight the redis db went empty.
persistence is enabled in the config as the config file is more or less the default one comming with the software. the only line changed is the name of the database file to save the data into.

rbeer

@rbeer said:

I'm curious about the contents of two files:

/var/log/redis/redis-server.log

/path/to/nodebb/log/nodebb.log

@wellenreiter

Charly86

Hi guys,
Experienced the same last night too, and again today!
logs (redis,nginx,nodebb) says everything is fine, it's just amazing.
I wrote a blog article on this problem with all my configuration/log files and what I've done to investigate but with no luck
you can read full article here
Any ideas are welcome, since I'm not the 1st having this problem

@Pilvinen would you share your bash backup scripts ?

PitaJ

@Charly86 @Pilvinen @wellenreiter What version of redis are you guys on?

Charly86

Mine is Redis 2.8.17 (00000000/0) 64 bit

? Offline

I use Redis 3.0.5 and I got it running since May.
Never had a problem except once, but it was my own fold as I overwrote the database during a NodeBB upgrade.

Do you guys all use OVH?
I cannot confirm any of this issues for me Redis seems to just work fine.

Charly86

I'm using it since may, just some pains during upgrade else all works fine.

OVH as VM provider ? is that what you mean ? Yes correct I'm on a VPS over OVH with 2.6.32 kernel

? Offline

@Charly86 thats interesting. I would suspect OVH to be responsible for the failure. It could be the case that their RAM has certain problems. Maybe try a setup on Kimsufi (OVH - dedicated servers) and see if it occurs again.

Charly86

@AOKP
Seems that we came to the same results, after checked everything I suspected may be shared RAM on OVH (it will not be my first issue with OVH)
Just followed your link, worth trying kimsufi, thanks

? Offline

@Charly86 keep us updated. I am very curious now. Think its time to write Oles an email