URGENT, Cannot install on Rocky 9
-
$ ./nodebb start && ./nodebb log Starting NodeBB "./nodebb stop" to stop the NodeBB server "./nodebb log" to view server output "./nodebb help" for more commands Process "3559" from pidfile not found, deleting pidfile Hit Ctrl-C to exit at Module.load (node:internal/modules/cjs/loader:1117:32) [cluster] Child Process (3570) has exited (code: 0, signal: null) NodeBB v3.1.3 Copyright (C) 2013-2023 NodeBB Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. For the full license, please visit: http://www.gnu.org/copyleft/gpl.html Clustering enabled: Spinning up 1 process(es). 2023-05-18T19:56:17.884Z [4567/4024] - info: Initializing NodeBB v3.1.3 https://support.domain.com 2023-05-18T19:56:22.248Z [4567/4024] - info: [socket.io] Restricting access to origin: https://support.domain.com:* 2023-05-18T19:56:23.110Z [4567/4024] - warn: [plugins] "nodebb-plugin-question-and-answer" is active but not installed. 2023-05-18T19:56:23.413Z [4567/4024] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it. * nodebb-rewards-essentials 2023-05-18T19:56:23.761Z [4567/4024] - warn: [plugins] "nodebb-plugin-question-and-answer" is active but not installed. 2023-05-18T19:56:24.730Z [4567/4024] - info: [api] Adding 0 route(s) to `api/v3/plugins` 2023-05-18T19:56:24.769Z [4567/4024] - info: [router] Routes added 2023-05-18T19:56:25.108Z [4567/4024] - info: 🎉 NodeBB Ready 2023-05-18T19:56:25.116Z [4567/4024] - info: 🤝 Enabling 'trust proxy' 2023-05-18T19:56:25.128Z [4567/4024] - info: 📡 NodeBB is now listening on: 0.0.0.0:4567 2023-05-18T19:56:25.128Z [4567/4024] - info: 🔗 Canonical URL: https://support.domain.com DEPRECATION WARNING on line 68, column 52 of ../../node_modules/bootswatch/dist/flatly/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 68 │ $nav-link-padding-y: .5rem !default !default; │ ^^^^^^^^ ╵ DEPRECATION WARNING on line 70, column 56 of ../../node_modules/bootswatch/dist/flatly/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 70 │ $nav-link-disabled-color: $gray-600 !default !default; │ ^^^^^^^^ ╵ DEPRECATION WARNING on line 79, column 60 of ../../node_modules/bootswatch/dist/litera/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 79 │ $input-group-addon-bg: $gray-200 !default !default; │ ^^^^^^^^ ╵ -
You need to create the indices in mongodb if they are missing. You can do by running these commands in mongodb.
db.objects.createIndex({ _key: 1, score: -1 }, { background: true }); db.objects.createIndex({ _key: 1, value: -1 }, { background: true, unique: true, sparse: true }); db.objects.createIndex({ expireAt: 1 }, { expireAfterSeconds: 0, background: true });Without indices everything will be super slow.
-
I can do that but I would have thought the restore would have taken care of that.
There are still some things I have to click more than once but maybe it's because of the slowness.
Here are some of those but I'll run your commands and see what happens.DEPRECATION WARNING on line 116, column 63 of ../../node_modules/bootswatch/dist/solar/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 116 │ $navbar-light-color: rgba($black, .4) !default !default; │ ^^^^^^^^ ╵ DEPRECATION WARNING on line 117, column 63 of ../../node_modules/bootswatch/dist/solar/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 117 │ $navbar-light-active-color: rgba($black, .7) !default !default; │ ^^^^^^^^ ╵ 2023-05-18T20:10:27.404Z [4567/4281] - error: posts.accept Error: [[error:no-post]] at canEditQueue (/home/nodebun/nodebb/src/socket.io/posts.js:154:9) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async SocketPosts.accept (/home/nodebun/nodebb/src/socket.io/posts.js:103:2) at async onMessage (/home/nodebun/nodebb/src/socket.io/index.js:182:19) 2023-05-18T20:11:34.510Z [4567/4281] - error: posts.accept Error: [[error:no-post]] at canEditQueue (/home/nodebun/nodebb/src/socket.io/posts.js:154:9) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async SocketPosts.accept (/home/nodebun/nodebb/src/socket.io/posts.js:103:2) at async onMessage (/home/nodebun/nodebb/src/socket.io/index.js:182:19) -
test> use nodebb switched to db nodebb nodebb> db.objects.createIndex({ _key: 1, score: -1 }, { background: true }); _key_1_score_-1 nodebb> db.objects.createIndex({ _key: 1, value: -1 }, { background: true, unique: true, sparse: true }); MongoServerError: Index build failed: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx: Collection nodebb.objects ( xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx ) :: caused by :: E11000 duplicate key error collection: nodebb.objects index: _key_1_value_-1 dup key: { _key: "analyticsKeys", value: "uniquevisitors" } nodebb> db.objects.createIndex({ expireAt: 1 }, { expireAfterSeconds: 0, background: true }); expireAt_1 -
Stop your forum and remove the offending keys until you can run the index create command.
db.objects.removeMany({_key: "analyticsKeys"});Then try
db.objects.createIndex({ _key: 1, value: -1 }, { background: true, unique: true, sparse: true });again. -
Ok, ran all four then ran build and restarted the board.
test> use nodebb switched to db nodebb nodebb> db.objects.removeMany({_key: "analyticsKeys"}); TypeError: db.objects.removeMany is not a function nodebb> db.objects.deleteMany({_key: "analyticsKeys"}); { acknowledged: true, deletedCount: 51 } nodebb> db.objects.createIndex({ _key: 1, score: -1 }, { background: true }); _key_1_score_-1 nodebb> db.objects.createIndex({ _key: 1, value: -1 }, { background: true, unique: true, sparse: true }); _key_1_value_-1 nodebb> db.objects.createIndex({ expireAt: 1 }, { expireAfterSeconds: 0, background: true }); expireAt_1 nodebb> exitIt always complains about the questions plugin;
nodebun@nb01:~/nodebb$ ./nodebb build started 2023-05-18T22:32:11.596Z [4567/4717] - warn: [plugins] "nodebb-plugin-question-and-answer" is active but not installed. 2023-05-18T22:32:11.642Z [4567/4717] - info: [build] Building in parallel mode 2023-05-18T22:32:11.645Z [4567/4717] - info: [build] plugin static dirs build started 2023-05-18T22:32:11.647Z [4567/4717] - info: [build] requirejs modules build started 2023-05-18T22:32:11.648Z [4567/4717] - info: [build] client js bundle build started 2023-05-18T22:32:11.649Z [4567/4717] - info: [build] admin js bundle build started 2023-05-18T22:32:11.650Z [4567/4717] - info: [build] client side styles build started 2023-05-18T22:32:11.651Z [4567/4717] - info: [build] admin control panel styles build started 2023-05-18T22:32:11.652Z [4567/4717] - info: [build] templates build started 2023-05-18T22:32:11.653Z [4567/4717] - info: [build] languages build started 2023-05-18T22:32:12.335Z [4567/4717] - info: [build] plugin static dirs build completed in 0.69sec 2023-05-18T22:32:13.868Z [4567/4717] - info: [build] client js bundle build completed in 2.22sec 2023-05-18T22:32:13.868Z [4567/4717] - info: [build] admin js bundle build completed in 2.219sec 2023-05-18T22:32:22.318Z [4567/4717] - info: [build] client side styles build completed in 10.667sec 2023-05-18T22:32:23.079Z [4567/4717] - info: [build] admin control panel styles build completed in 11.427sec 2023-05-18T22:32:23.510Z [4567/4717] - info: [build] languages build completed in 11.857sec 2023-05-18T22:32:24.053Z [4567/4717] - info: [build] templates build completed in 12.401sec 2023-05-18T22:32:24.212Z [4567/4717] - info: [build] requirejs modules build completed in 12.565sec 2023-05-18T22:32:24.212Z [4567/4717] - info: [build] Bundling with Webpack. 2023-05-18T22:32:24.235Z [4567/4717] - warn: [plugins] "nodebb-plugin-question-and-answer" is active but not installed. 2023-05-18T22:32:46.180Z [4567/4717] - info: [build] Bundling took 18077 ms 2023-05-18T22:32:46.199Z [4567/4717] - info: [build] Asset compilation successful. Completed in 34.537sec.However, I did install it when rebuilding the board.
$ history | grep question 63 npm install nodebb-plugin-question-and-answer 162 history | grep questionI've re-installed it and ran build again.
This time, no complaints so I started the board again.
Few complaints coming up but the board came up.DEPRECATION WARNING on line 68, column 52 of ../../node_modules/bootswatch/dist/flatly/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 68 │ $nav-link-padding-y: .5rem !default !default; │ ^^^^^^^^ ╵ DEPRECATION WARNING on line 70, column 56 of ../../node_modules/bootswatch/dist/flatly/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 70 │ $nav-link-disabled-color: $gray-600 !default !default; │ ^^^^^^^^ ╵ DEPRECATION WARNING on line 79, column 60 of ../../node_modules/bootswatch/dist/litera/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 79 │ $input-group-addon-bg: $gray-200 !default !default; │ ^^^^^^^^ ╵The errors keep showing up but the board is running now.
I'll test everything I can and see how it's going now. -
Is it too early to understand what happened? I can document all of the steps I took. Every time I goofed something up because I could not find enough documentation, I noted that and tried again so that eventually, I had all the steps needed. However, I still ended up with these problems.. maybe others?
-
You had 2 different problems .
Your package.json had a broken version for
request-promise-nativeand you didn't have indices when you restored your database.Not sure how the first one happened but the missing indices happens when you only export the objects collection from mongodb. If you want to export the whole database you can use
mongodump --db <name_of_db> -
But how do you think it originally started?
The fact that my backup had a broken package.json means it was a while that this started ago.
The indexes, I've no idea since all I did was to restore.All looks ok now but one weird thing. I noticed there was an upgrade so I upgraded. The text showed upgrade completed without errors but on the back end, it still shows 3.1.4 upgrade available. Also, can I get back to persona now?
