NODEBB: Nginx error performance & High CPU

[phenomlab]

@DownPW I’d add another set of steps here. When you move the sessions away from mongo to redis you are going to encounter issues logging in as the session tables will no longer match meaning none of your users will be able to login

To resolve this issue

Review https://sudonix.com/topic/249/invalid-csrf-on-dev-install and implement all steps - note that you will also need the below string when connecting to mongodb

mongo -u admin -p <password> --authenticationDatabase=admin

Obviously, substitute <password> with the actual value. So in summary:

1. Open the mondogb console
2. Select your database - in my case use sudonix;
3. Issue this command db.objects.update({_key: "config"}, {$set: {cookieDomain: ""}});
4. Press enter and then type quit() into the mongodb shell
5. Restart NodeBB
6. Clear cache on browser
7. Try connection again

[DownPW]

@phenomlab

Hmm ok when perform these steps ?

[phenomlab]

@DownPW After you’ve setup the cluster and restarted NodeBB

[crazycells]

@phenomlab said in NODEBB: Nginx error performance & High CPU:

@crazycells said in NODEBB: Nginx error performance & High CPU:

4567, 4568, and 4569… Is your NodeBB set up this way?

It’s not (I set their server up). Sudonix is not configured this way either, but from memory, this also requires redis to handle the session data. I may configure this site to do exactly that.

yes, you might be right about the necessity. We have redis installed.

[crazycells]

@DownPW yes, this is the place to start:

https://docs.nodebb.org/configuring/scaling/

[crazycells]

@DownPW since you pointed it out, I just remembered. Since we know when this crowd will come and be online on our forum, that particular day, we switch off iframely and all preview plugins. That also helps to open the pages faster.

[crazycells]

@phenomlab a general but related question. Since opening three ports help, is it possible to increase this number? For example, can we run 5 ports NodeBB at the same time to smooth the web page experience; or is “3” goldilocks number for maximum efficiency?

[phenomlab]

@crazycells It’s not necessarily the “Goldilocks” standard - it really depends on the system resources you have available. You could easily extend it as long as you allow for the additional port(s) in the nginx.conf file also.

Personally, I don’t see the need for more than 3 though.

[DownPW]

@phenomlab

Ok redis is ok now. Thanks for your help

I would like know to obtain the connecting clients Real IP on Nginx log.

I read I have need ngx_http_realip_module for nginx but not active by default but I don’t know if virtualmin have this module enabled.

[DownPW]

@DownPW said in NODEBB: Nginx error performance & High CPU:

@phenomlab

Ok redis is ok now. Thanks for your help

I would like know to obtain the connecting clients Real IP on Nginx log.

I read I have need ngx_http_realip_modulefor nginx but not active by default but I don’t know if virtualmin have this module enabled.

EDIT: OK it will be enabled by default on virtualmin :

nginx -v

[DownPW]

@phenomlab

I have activate ngx_http_realip_module on /etc/nginx/nginx.conf on http block like this :

It seems to be good for you ?

[phenomlab]

@DownPW yes, that looks fine.

[DownPW]

@phenomlab

We have sometimes this error, what do you think about it ?

[phenomlab]

@DownPW I suspect that’s a failure of the socket server to talk to redis, but the NodeBB Devs would need to confirm.

[DownPW]

@phenomlab

Seems to be better with some scaling fix for redis on redis.conf. I haven’t seen the message yet since the changes I made

# I increase it to the value of /proc/sys/net/core/somaxconn
tcp-backlog 4096 


# I'm uncommenting because it can slow down Redis. Uncommented by default !!!!!!!!!!!!!!!!!!! 
#save 900 1
#save 300 10
#save 60 10000

If you have other Redis optimizations. I take all your advice

https://severalnines.com/blog/performance-tuning-redis/