Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

NodeBB v1.0.4-auto.2 many crashes

Bug Reports

1

1

766

Log in to reply

Павел Субач

NodeBB v1.0.4-auto.2

29/5 02:45 [782] - [32minfo[39m: [app] Shutdown (SIGTERM/SIGINT) Initialised.
29/5 02:45 [779] - [32minfo[39m: [app] Shutdown (SIGTERM/SIGINT) Initialised.
(node) warning: possible EventEmitter memory leak detected. 11 connect listeners added. Use emitter.setMaxListeners() to increase limit.
29/5 02:45 [774] - [32minfo[39m: [app] Shutdown (SIGTERM/SIGINT) Initialised.
Trace
    at Socket.addListener (events.js:252:17)
    at Socket.Readable.on (_stream_readable.js:673:33)
29/5 02:45 [779] - [32minfo[39m: [app] Database connection closed.
29/5 02:45 [774] - [32minfo[39m: [app] Database connection closed.
    at Socket.once (events.js:278:8)
29/5 02:45 [779] - [32minfo[39m: [app] Web server closed to connections.
29/5 02:45 [774] - [32minfo[39m: [app] Web server closed to connections.
    at Socket.unref (net.js:1013:10)
29/5 02:45 [779] - [32minfo[39m: [app] Shutdown complete.
29/5 02:45 [774] - [32minfo[39m: [app] Shutdown complete.
    at Connection.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/connection/connection.js:453:23)
    at /home/wing/nodebb/node_modules/mongodb-core/lib/connection/pool.js:189:7
    at Array.forEach (native)
    at Pool.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/connection/pool.js:182:15)
    at Server.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/topologies/server.js:1072:31)
    at Server.close (/home/wing/nodebb/node_modules/mongodb/lib/server.js:417:17)
29/5 02:45 [782] - [32minfo[39m: [app] Database connection closed.
29/5 02:45 [782] - [32minfo[39m: [app] Web server closed to connections.
29/5 02:45 [782] - [32minfo[39m: [app] Shutdown complete.
[cluster] Child Process (774) has exited (code: 0, signal: null)
[cluster] Child Process (779) has exited (code: 0, signal: null)
[cluster] Child Process (782) has exited (code: 0, signal: null)

Suggested Topics

Nodebb benchmarking userslug api issues
Bug Reports • • venkat123

7

0
Votes

7
Posts

254
Views

@pitaj

Environment setup details
NodeBB => 12 Pods(each pod of 4GB RAM)
MondeDB => 1pod(4 core machine)

We are using NodeBB in "Sunbird platform". While we do benchmark of NodeBB API's, we have noticed this issue.

Most of the {userslug} API's are not performaing well(throughput around 140) as metioned by @venkat123 in the above thread.
/api/user/venkat123 /api/user/venkat123/upvoted /api/user/venkat123/downvoted
Where as Category read API's are performing well. We are alble to get better through put around 1200.
/api/category/:cid
Digest duplicating emails on scaled nodebb
Bug Reports • • exodo

4

0
Votes

4
Posts

1019
Views

@baris Can you add this to the docs under "Scaling NodeBB" page? 😄
Change of Site Title in Settings General changes site title of all NodeBB installations on server
Bug Reports • • v4

6

0
Votes

6
Posts

1979
Views

great! thanks so much for the quick fix! meanwhile I found a quick workaround through restarting everything. will wait with the merge...
S

When you update Nodebb to latest code,guest and normal user can't see the website.
Bug Reports • • song19891121

8

0
Votes

8
Posts

2756
Views

@song19891121 The permissions were refactored so that by default, if a category has no permissions checked (in the Access Control modal), nobody can access it.

This is a departure from the previous behaviour, which was:
Registered users can access and post Guests can access but cannot post
Which was confusing for some.
Long story shot
The upgrade script should transparently convert your existing permissions properly, but clearly there are some bugs. When you upgrade, go through all of your categories and ensure the permissions are set correctly.
D

Welcome to NodeBB Wrapping - ACP Theme
Bug Reports • • dylenbrivera

1

0
Votes

1
Posts

577
Views

D

This is not a bug that affects production, however I've noticed on several machines that when the boxes in the "Welcome to NodeBB" box wrap, they slightly overlap. Does this happen to anyone else?bug.png

| | |

Copyright © 2022 NodeBB | Contributors

1 / 1

Get Started

Resources

Company

© 2014 – 2022 NodeBB, Inc. — Made in Canada.