every other 5 minutes, my browser console many errors, eg:
GET http://www.seenewyun.com/socket.io/?EIO=3&transport=polling&t=MOJNhdj 502 (Bad Gateway)
,but nodebb can auto connect.
@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.
@Raj said in Running NodeBB on multi core CPU:
@PitaJ Thanks. As I have 8 core CPU I want my NodeBB to use all of them. But by default NodeBB is using only one core!
Are you running your reverse proxy, SSL handling, or database on the same box? If so, you definitely don't want all of them for NodeBB.
Even if you aren't, why do you have so many cores, and what are you doing that makes you want to scale like this? How busy is your site? We've topped 191 million hits in a single month on a single core and aren't even working hard.
