High CPU, 503 blue screen error.

[Nuran Akimbek]

The communtiy (https://forum.orleu-edu.kz/) has been taking a long time to load for a month now. I have already created several topics in order to solve my problem.

• 

  Please help me. High CPU, but only 25 users on system

  Hi everyone https://forum.orleu-edu.kz/ - course listeners community. Our community loads very slow and when active users increase up to 20-30 it shows blue ...

  

  NodeBB Community (community.nodebb.org)

• 

  After scaling cpu is still high

  @baris Last warning or error message from output log is - Failed to fetch latest version error - rate limit exceeded Community works well when users at least...

  

  NodeBB Community (community.nodebb.org)

• list item

But problem not solved yet. My one process apache proxy version works better than nginx with scaling so I upload all needed screens.

last logs

For information, also we have a integration between our course platform and community using nodebb read and write api. Registration, join to group, reset password, edit account processes occured using this platform

[baris]

On that last screenshot there is an error and nodebb restarted, but the rest of the error is missing. Take alook at /path/to/nodebb/logs/output.log and post the full error message.

If nodebb is crashing and restarting regulary it would explain why you are seeing the error page and high cpu usage.

[Nuran Akimbek]

output log
2024-04-12T09:11:41.395Z [4567/608008] - info: NodeBB Ready
2024-04-12T09:11:41.396Z [4567/608008] - info: Enabling 'trust proxy'
2024-04-12T09:11:41.398Z [4567/608008] - info: NodeBB is now listening on: 0.0.0.0:4567
2024-04-12T09:11:41.398Z [4567/608008] - info: Canonical URL: http://forum.orleu-edu.kz
2024-04-12T09:11:43.690Z [4567/607127] - info: [app] Live analytics saved.
2024-04-12T09:11:43.721Z [4567/607127] - info: [app] Database connection closed.
2024-04-12T09:11:43.721Z [4567/607127] - info: [app] Shutdown complete.
[cluster] Child Process (607127) has exited (code: 0, signal: null)
2024-04-12T09:18:50.872Z [4567/608008] - error: [acp] Failed to fetch latest versionTimeoutError: The operation was aborted due to timeout
at node:internal/deps/undici/undici:12345:11
at runNextTicks (node:internal/process/task_queues:60:5)
at process.processTimers (node:internal/timers:511:9)
at async call (/nodebb/src/request.js:37:19)
at async getLatestVersion (/nodebb/src/admin/versions.js:22:44)
at async getLatestVersion (/nodebb/src/middleware/render.js:500:11)
at async Promise.all (index 4)
at async loadAdminHeaderFooterData (/nodebb/src/middleware/render.js:253:19)
at async loadHeaderFooterData (/nodebb/src/middleware/render.js:137:11)
at async renderMethod (/nodebb/src/middleware/render.js:87:30)

In order to solve my problem I edit apache vhost, other files and by the end I restart/rebuild nodebb regularly. I still use in my nodebb with read api also third party write-api plugin. May be cause of this?

[PitaJ]

Is that the entire contents of output.log? The message you posted is pretty useless

[baris]

I restart/rebuild nodebb regularly

You shouldn't do this, rebuild and restart are pretty expensive. You should find the actual error messages and crashes in the nodebb log and fix those.

[nhl.pl]

Are you sure you want to use Apache web server? Even lightweight nginx working as reverse proxy can be easily overloaded with normal traffic. And you will see a result like this. Similar to attacking php-based forum with ddos-bots traffic.

Bluescreen rate-limiting high traffic will help to reduce server load so you want to leave it as it is.

A better idea is to install firewall or similar software to deny traffic from problematic IPs/countries/etc.