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



  • @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.



  • @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.



  • @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.



  • 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...


  • Community Rep

    If there's no firewall it's completely possible


  • GNU/Linux

    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.



  • @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.


  • GNU/Linux

    @rbeer said:

    I'm curious about the contents of two files:

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

    @wellenreiter 😉



  • 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 ?


  • Global Moderator

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



  • Mine is Redis 2.8.17 (00000000/0) 64 bit



  • 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.



  • 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



  • @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.



  • @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



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



  • @AOKP
    To be honest, server migration does take time that I do not have for now (especially after the crash of this week), in the meantime I need to keep OVH because my server is hosting different applications that I can't move at the same time. So of course I will try it for new application or test but for now my dirty fix would be upgrading redis (I just compiled latest 3.0.5, it's ok) or upgrade nodeBB to another db, but seems I need to pay for this one.



  • @Charly86 it does not makes a lot of sense to compile a new version of Redis, which also has its difficuilties with OVH. If you want I can assist you, just PM me.



  • That's just silly theory. I have been using the same 32 GB dedicated OVH server for several years and I've never had any RAM or any other issues with the server.

    @AOKP said:

    @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.



  • @Pilvinen sure? OVH is known for having its difficuilties here and there. The other question then would also be why I didn't lost my data.

    And why all of you 3 (at least 2), who are using OVH have the same problem.




Looks like your connection to NodeBB was lost, please wait while we try to reconnect.