@scottalanmiller So unfortunately none of the versions worked with our database any more. We even tried 1.11.2 and went back to 1.10.2 on mongodb 3.2 as well. Now, we've updated mongodb to 3.4 and picked up an old database backup to migrate from 3.2 to 3.4 on the latest nodebb (1.11.2). Its working properly now. However, a warning for people on older versions of mongodb when updating to 1.11.x onward.

MongoDB changes licensing creating cascade of open source requirements. Take a look, if you are deploying NodeBB with MongoDB ever, or write any code for anything that touches it, be aware that you may be forced to open source anything and everything.

thx, it worked

Does the forum logs give an error when it crashes? Do you have mongo and nginx logs on? There should be some useful information in one of the logs as to what is happening.

@alff0x1f excellent! Thank you very much for those printouts. Swap it is, then

@pichalite Thanks Rookie mistake by me

No they return the score of the value. db.sortedSetScore(set, data.name, function(err, score) { console.log(score); });

NodeBB w/ MongoDB still works just fine even though the kerberos dependency doesn't build, it just means you can't connect to MongoDB servers utilising kerberos authentication. Would prefer not to have to add libkrb5-dev to the list of dependencies, so investigating alternatives...

Well, damn. Didnt know that. Okay, Thanks for your phenomenal help, @pichalite. Gonna mess around with this proxying and nginx a bit now that everything is moving forward again.

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.

Thank you @markkus and @jarey for your replies. I did what you suggested about re-installation and the problem persisted. I then discovered something... ...the installation manual may be outdated. The file in question on Step 7 is mongod.conf instead of mongodb.conf. Can @psychobunny or whoever in charge of the Doc double check this and make the proper correction?

The structure looks not friendly at all.

Since I updated my NodeBB to the latest 0.7.0 version I've noticed that my "sessions" collection keeps increasing in size constantly, like if the sessions in it were never expiring and always being re-created. I'm experiencing this issue only with Openshift, while my instance in AWS Elasticbeanstalk is working just fine. Not sure if this info is relevant though, because in the Openshift instance I did some changes in NodeBB, like new routes and other node modules, but I haven't tested yet if they are the cause of this issue. In any case, if I just drop the "sessions" collection, it will show like 50 new empty sessions in less than 10 seconds. Some documents: { "_id": "pmJRsePD-ctzSQ0rtzW49k-KohSs2WHp", "session": "{\"cookie\":{\"originalMaxAge\":1209600000,\"expires\":\"2015-06-16T13:38:19.835Z\",\"httpOnly\":true,\"path\":\"/\"},\"passport\":{},\"csrfSecret\":\"F5RHBIVPiK9QyDhiE4iXWP_B\"}", "expires": { "$date": "2015-06-16T13:38:19.835Z" } } { "_id": "oqDkaZfvoY_J0b-iNe0pyzrKufeTHEjD", "session": "{\"cookie\":{\"originalMaxAge\":1209600000,\"expires\":\"2015-06-16T13:38:19.984Z\",\"httpOnly\":true,\"path\":\"/\"},\"passport\":{},\"csrfSecret\":\"smJWt0HbwNY9QSGTpr0w2wDx\"}", "expires": { "$date": "2015-06-16T13:38:19.984Z" } } { "_id": "14qrP1DtX3Qr2bbchAM4tcKIg3Uu9CnE", "session": "{\"cookie\":{\"originalMaxAge\":1209600000,\"expires\":\"2015-06-16T13:38:20.281Z\",\"httpOnly\":true,\"path\":\"/\"},\"passport\":{},\"csrfSecret\":\"WJhAT0xS5cQcL4lTU7kz3Qar\"}", "expires": { "$date": "2015-06-16T13:38:20.281Z" } } The closest thing that I could find on the web was this post which somewhat describes the issue I'm having, but I'm not sure if it's really related. Any help on this matter? Regards!

@psychobunny Yes it is Well, that was just the entire upgrade process from 0.5.2-dev to 0.7.0-dev hahaha So I guess this thread will only serve as a "tutorial" or feedback lol... But yeah, everything's fine and running smooth! Had to rebase 33 commits on top of your master branch but all good... so far

Anyone know if Minimongo could be used in a plugin to enable redis-style caching to a full mongodb instance? The redis (live) to mongodb (persist) route looks daunting... JB

@julian said in Mongo vs Redis: which one is better for a huge community?: 64GB -- that is a lot of memory We host larger databases on much less RAM (as we're using a cloud provider and high memory installs are crazy expensive)... There is definitely a speed difference though. Navigating between pages on here takes a split second longer than a Redis database... if you want to see NodeBB fly, use Redis. @scottalanmiller was replying to somebody talking about a 50 GB data community though.

Something went wrong with setting up connection to MongoDB. Could you please provide some more information about your configuration?

If you install mongo via apt, I believe it is mongod, but via the 10gen repository, it is mongodb

i wasn't sure to do it.. : ) it seems to work.. thanks..

Well, I have this issue that I need to do following things: 1.Mongo Find 2. Foreach 3. MongoFind 4 one more Foreach. because of asynchronaus mongo calls it is difficult to get proper result, however process.nextTick should handle this problem and still I have problem: function find(dbComm) { dbComm.forEach(function (current) { id= parseFloat(current.ID); db.anotherCollection.find({ ID: id}, function (error, result) { result.forEach(function (rank) { if (parseFloat(result.ID) == parseFloat(current.ID)) { rank.rank = 'Some calculations'; } }); }); }); } app.get('/someparams', function (req, res) { db.collection.find().sort({ "rank": order }).skip(pagenumber).limit(5, function (err, result) { process.nextTick(function () { find(result, function () { }) }); process.nextTick(function () { res.send(result); }); }); And on client side I should recive an array where the rank equals 'Some Calculations' but unfortunetly it is not... However...! If I add setTimeout(function(){}) before res.send(result) (and res.send(result) will be placed inside setTimeout) it actually does work and on client side I recive data with "Some Calculations" but it is just timeout and it fails sometimes and client dont recive "Some Calculations" if I put process.nextTick instead of setTimeout it doesnt work and "Some calc..." are not sent. Something is beeing done eralier then it should (probably in forEach in find() function) and my question is how to deal with it? maybe I should put process.nextTick in different function ?