Damn and is my own post ! Haha I fixed it but when I redeployed lost the "fix". Sorry for the noise

I believe the issue is with nodebb-plugin-mentions so for now I'll just disable it.

Hello guys.

My forum is down right now with this issue:

nodebb  | 2024-07-01T13:35:21.489Z [4567/282] - error: GET /foro
nodebb  | TypeError: categories.getCidByHandle is not a function
nodebb  |     at /usr/src/app/nodebb/node_modules/nodebb-plugin-mentions/library.js:413:21
nodebb  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
nodebb  |     at async Promise.all (index 0)
nodebb  |     at async Mentions.parseRaw (/usr/src/app/nodebb/node_modules/nodebb-plugin-mentions/library.js:404:2)
nodebb  |     at async Mentions.parsePost [as method] (/usr/src/app/nodebb/node_modules/nodebb-plugin-mentions/library.js:340:17)
nodebb  |     at async fireMethod (/usr/src/app/nodebb/src/plugins/hooks.js:256:11)
nodebb  |     at async Object.fireFilterHook [as filter] (/usr/src/app/nodebb/src/plugins/hooks.js:263:12)
nodebb  |     at async Hooks.fire (/usr/src/app/nodebb/src/plugins/hooks.js:192:17)
nodebb  |     at async Posts.parsePost (/usr/src/app/nodebb/src/posts/parse.js:64:16)
nodebb  |     at async Promise.all (index 0)

I did a quick search on this forum and did not find any previous posters mentioning this issue.

Does anyone have any idea what might be the issue here ?

Any help is much appretiated.

@baris said in 3.8.0 Upgrade Support:

@fgallese install nodebb 3.8.1 or install mentions plugin version 4.4.3.

Thank you will try

@baris said in 3.8.0 Upgrade Support:

@bornelite do you have a stack trace from your nodebb log?

Im having the same error, my forum is down with this stacktrace:

nodebb  | 2024-05-23T14:36:47.794Z [4567/284] - info: 📡 NodeBB is now listening on: 0.0.0.0:4567
nodebb  | 2024-05-23T14:36:47.794Z [4567/284] - info: 🔗 Canonical URL: https://forobolso.uy/foro
nodebb  | WARNING: The keyword 'none' must be used as a single argument.
nodebb  |     ../../../bootstrap/scss/mixins/_box-shadow.scss 10:9   box-shadow()
nodebb  |     ../../../bootstrap/scss/forms/_form-control.scss 40:7  @import
nodebb  |     bootstrap/scss/_forms.scss 3:9                         @import
nodebb  |     - 19:9                                                 root stylesheet
nodebb  | 
nodebb  | WARNING: The keyword 'none' must be used as a single argument.
nodebb  |     ../../../bootstrap/scss/mixins/_box-shadow.scss 10:9  box-shadow()
nodebb  |     ../../../bootstrap/scss/forms/_form-select.scss 32:7  @import
nodebb  |     bootstrap/scss/_forms.scss 4:9                        @import
nodebb  |     - 19:9                                                root stylesheet
nodebb  | 
nodebb  | 2024-05-23T14:37:31.866Z [4567/284] - error: GET /foro
nodebb  | TypeError: categories.getCidByHandle is not a function
nodebb  |     at /usr/src/app/nodebb/node_modules/nodebb-plugin-mentions/library.js:402:32
nodebb  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
nodebb  |     at async Promise.all (index 0)
nodebb  |     at async Mentions.parseRaw (/usr/src/app/nodebb/node_modules/nodebb-plugin-mentions/library.js:398:2)
nodebb  |     at async Mentions.parsePost [as method] (/usr/src/app/nodebb/node_modules/nodebb-plugin-mentions/library.js:339:17)
nodebb  |     at async fireMethod (/usr/src/app/nodebb/src/plugins/hooks.js:256:11)
nodebb  |     at async Object.fireFilterHook [as filter] (/usr/src/app/nodebb/src/plugins/hooks.js:263:12)
nodebb  |     at async Hooks.fire (/usr/src/app/nodebb/src/plugins/hooks.js:192:17)
nodebb  |     at async Posts.parsePost (/usr/src/app/nodebb/src/posts/parse.js:63:16)
nodebb  |     at async Promise.all (index 0)

Any ideas ?

While testing this new version 3.3.3, I notice a lot of 400 errors while requesting https://ourforum.com/foro/socket.io does anyone have idea why this could be happening ?

This is the payload of the response:
{"code":1,"message":"Session ID unknown"}

Thank you @baris for all your help and support, our forum is back online thanks to you.

@baris said in 3.3.0 Upgrade Support:

Looks like mongodb cursors have a lifetime of 10minutes so it might be throwing that error after that

Can you run this in your mongo cli?

db.objects.count({_key: "chat:room:<replace_with_global_chat_roomid>:uids"});
db.objects.count({_key: "uid:<replace_with_your_uid>chat:room:<replace_with_global_chat_roomid>:mids"});

So we can get an idea of how many users/messages are in that global chat room.

You can trim those zsets in mongo cli since this is most like only caused by that one room that has all users in the forum but that is a last resort.


This is after I removed messages (which btw I believe did not help, I might need to recover a backup of the db).

@baris said in 3.3.0 Upgrade Support:

@fgallese Which version are you using now? Are you on 3.3.3 or a previous version?

I was in 3.2 and i am trying to migrate to 3.3.3.

@baris I am still unable to do the upgrade.. the mongo connection goes down after several minutes running the update:

nodebb  | Parsing upgrade scripts... 
nodebb  | OK | 5 script(s) found, 124 skipped
nodebb  |   → [2023/7/2] Update chat messages to add roomId field...
nodebb  | Error occurred
    [###          ] (502/1775) 28% 2023-08-19T18:27:29.351Z [4567/10] - warn: NodeBB Setup Aborted.
nodebb  |  MongoServerError: cursor id 8839582387884439579 not found
nodebb  |     at Connection.onMessage (/usr/src/app/nodebb/node_modules/mongodb/lib/cmap/connection.js:202:26)
nodebb  |     at MessageStream.<anonymous> (/usr/src/app/nodebb/node_modules/mongodb/lib/cmap/connection.js:61:60)
nodebb  |     at MessageStream.emit (node:events:513:28)
nodebb  |     at processIncomingData (/usr/src/app/nodebb/node_modules/mongodb/lib/cmap/message_stream.js:124:16)
nodebb  |     at MessageStream._write (/usr/src/app/nodebb/node_modules/mongodb/lib/cmap/message_stream.js:33:9)
nodebb  |     at writeOrBuffer (node:internal/streams/writable:392:12)
nodebb  |     at _write (node:internal/streams/writable:333:10)
nodebb  |     at Writable.write (node:internal/streams/writable:337:10)
nodebb  |     at Socket.ondata (node:internal/streams/readable:766:22)
nodebb  |     at Socket.emit (node:events:513:28)
nodebb exited with code 1

I guess my only option is to remove chat messages. Is there any tool for this or am I gonna have to figure it out in the DB ? Can I just run a delete on {_key:"message:*"} where the timestamp is older than 1 month or something ?

If I run this, would i break something ?

db.objects.deleteMany({
  "_key": {
    "$regex": /^message:\d+$/
  },
  "timestamp": { "$lt": oneMonthAgoTimestamp }
});

@baris said in 3.3.0 Upgrade Support:

You could try adding .allowDiskUse(true) to the query at https://github.com/NodeBB/NodeBB/blob/master/src/database/mongo/sorted.js#L397-L401.

It throws that error because the data is too big to sort in memory (the default limit is 100mb).

I am working on the new upgrade script that should be aviable later today as 3.3.1.

Hello @baris . Today after update to 3.3.1 I see a new error:

Parsing upgrade scripts... 
OK | 5 script(s) found, 124 skipped
  → [2023/7/2] Update chat messages to add roomId field...
Error occurred
2023-08-18T19:43:48.782Z [4567/9] - warn: NodeBB Setup Aborted.
 TypeError: midsSeen.hasOwnProperty is not a function
    at /usr/src/app/nodebb/src/upgrades/3.3.0/chat_room_refactor.js:41:55
    at Array.filter (<anonymous>)
    at batch.processSortedSet.batch (/usr/src/app/nodebb/src/upgrades/3.3.0/chat_room_refactor.js:41:31)
    at module.processSortedSet (/usr/src/app/nodebb/src/database/mongo/sorted.js:588:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async exports.processSortedSet (/usr/src/app/nodebb/src/batch.js:30:10)
    at async batch.processSortedSet.batch (/usr/src/app/nodebb/src/upgrades/3.3.0/chat_room_refactor.js:40:8)
    at async module.processSortedSet (/usr/src/app/nodebb/src/database/mongo/sorted.js:588:5)
    at async exports.processSortedSet (/usr/src/app/nodebb/src/batch.js:30:10)
    at async batch.processArray.batch (/usr/src/app/nodebb/src/upgrades/3.3.0/chat_room_refactor.js:38:6)

Any idea how can I fix this ?

Thank you

@baris said in NodeBB 3.3.0:

Hmm in that case I will have to modify that upgrade script so it doesn't load all uids/messageIds in the room.

Do you think there is any quick workaround I can apply in my db to help this ? Like message trimming or similar ?

@baris said in NodeBB 3.3.0:

@fgallese do you have a room with a lot of users by any chance? Or were you using nodebb-plugin-global-chat?

Yes and yes. We have a chat room with all users which sees a lot of usage, so it is expected for us to have a lot of messages in the history I guess.

I am getting this error when upgrading:

Parsing upgrade scripts... 
OK | 5 script(s) found, 124 skipped
  → [2023/7/2] Update chat messages to add roomId field...
Error occurred
    [##############] (401/401) 100% 2023-08-17T20:42:31.417Z [4567/9] - warn: NodeBB Setup Aborted.
 MongoServerError: error while multiplanner was selecting best plan :: caused by :: Sort exceeded memory limit of 104857600 bytes, but did not opt in to external sorting.
    at Connection.onMessage (/usr/src/app/nodebb/node_modules/mongodb/lib/cmap/connection.js:202:26)
    at MessageStream.<anonymous> (/usr/src/app/nodebb/node_modules/mongodb/lib/cmap/connection.js:61:60)
    at MessageStream.emit (node:events:513:28)
    at processIncomingData (/usr/src/app/nodebb/node_modules/mongodb/lib/cmap/message_stream.js:124:16)
    at MessageStream._write (/usr/src/app/nodebb/node_modules/mongodb/lib/cmap/message_stream.js:33:9)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Writable.write (node:internal/streams/writable:337:10)
    at Socket.ondata (node:internal/streams/readable:766:22)
    at Socket.emit (node:events:513:28)

Anyone else seen this issue ?

Just wanted to chime in and say that we migrated to v3.0.0-rc2 a couple days ago and it's been smooth sailing, we are very pleased with the new theme. Great job !

@pitaj thank you for letting me know, much appreciated.
No worries, it's not critical.

Hello guys.

Just FYI, I see an error 500 to https://community.nodebb.org/api/post/upload while trying to upload an image here in this forum.

This does not happen to us in our forum, but we use imgur plugin so I guess that's the reason.

I started getting this errors with the latest upgrade:


Any idea what might be happening ?

Edit: Seems I cannot upload images here, so here is the link: https://imgur.com/a/1UsdCUY

Try removing the /var/run/mongodb/mongod.pid file and then stopping it. If it doesn't work, just kill the process.

Hello All,

Just updated our forum to the latest version of nodebb, and we are facing an issue with the global chat plugin:

The global chat room is displaying a message constantly:

Invitado has renamed this room: Chat ForoBolso

It's been like this for long time now and it doesn't seem to have an ending in sight.

Any ideas what the issue might be ?

This is a screenshot of this: