URGENT, Cannot install on Rocky 9

NodeHam

One post says you only need to restore the objects.bson. Is this the case then?

NodeHam

Nice, restoring only restores part of the board. Both are 3.1.3 no less.
I deleted the database then restored again. This time, most of it is there but even after copying the files back to public/uploads, some things are missing like logo and maybe other things along with the formatting I had.

Yup, feels like nodebb is for the few that know it inside out and the rest of us are 'non technical'.

NodeHam

Well, finally got the board fully up and running on Ubuntu from centos and there is no change. I still cannot accept new posts. What an ordeal this has been.

PitaJ

@NodeHam glad you got it up. What exactly is your issue? You can't accept posts on the queue? Do you get any errors client or server side? What version are you on now?

NodeHam

It's doing the same thing as it was on centos. I cannot accept new posts, it takes multiple times to log in sometimes and other weird things. As admin, I see a user that wants to be allowed but when I click on that user, he's never there.

I posted all the info I've got. There aren't any errors anywhere that I can see or I'm not noticing them.
I don't see any errors as I'm clicking on accept for example in the web sites or in the nodebb logs/ directory.

For some reason, it's very slow on ubuntu now yet there is no load on the server. It's typically around 0.30 or less.
I doubt it's ubuntu as I have a number of those running other applications and I'm not aware of any issues with the OS that could cause this.

To me, something has gotten corrupted in the database or one or more files but no way of finding enough help to fix this. I've been at this since yesterday non stop at this point and the only thing I've achieved is moving it to a server I didn't want to use. I wanted to use rocky 9 which I'll explore later now that I know it's not a server issue.

NodeHam

The only problem I'm really trying to solve right now is why I can't accept new signups and most importantly, first time posts. This seems like a bug since everything else is working.

NodeHam

I don't understand why not one person reading this is curious as to why this one thing is not working. Why is the rest of the forum working but I'm not able to accept new posts? Isn't there at least one developer here that is curious? You easily blame the user for being non technical yet I've shown and explained what is happening in great detail.

<baris>

@NodeHam send me your forum url so I can take a look ([email protected]), seems like it's a configuration issue. Accepting posts uses sockets so if you have issues with socket.io some functionality won't work.

NodeHam

@baris , are you one of the developers?
My concern is that since I've had to mess with it so much and rebuilding, I might now have caused some new problems accidentally. I've no way of knowing at this point.

If it helps;

$ npm update socket.io

up to date, audited 1390 packages in 10s

185 packages are looking for funding
  run `npm fund` for details

11 vulnerabilities (6 moderate, 5 high)

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

$ npm audit fix --force
npm WARN using --force Recommended protections disabled.
npm WARN audit Updating nodebb-plugin-spam-be-gone to 0.4.4, which is a SemVer major change.
npm WARN audit Updating request-promise-native to 0.0.0, which is a SemVer major change.
npm WARN audit No fix available for coveralls@*
npm WARN audit Updating nodebb-plugin-spam-be-gone to 0.4.4, which is a SemVer major change.
npm WARN audit No fix available for nodebb-plugin-emoji@>=2.0.0
npm WARN audit No fix available for nodebb-plugin-emoji-android@*
npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142

added 1 package, removed 13 packages, changed 3 packages, and audited 1378 packages in 9s

182 packages are looking for funding
  run `npm fund` for details

# npm audit report

dicer  *
Severity: high
Crash in HeaderParser in dicer - https://github.com/advisories/GHSA-wm7h-9275-46v2
No fix available
node_modules/dicer
  busboy  <=0.3.1
  Depends on vulnerable versions of dicer
  node_modules/busboy
    multer  <=2.0.0-rc.3
    Depends on vulnerable versions of busboy
    node_modules/multer
      nodebb-plugin-emoji  >=2.0.0
      Depends on vulnerable versions of multer
      node_modules/nodebb-plugin-emoji
        nodebb-plugin-emoji-android  *
        Depends on vulnerable versions of nodebb-plugin-emoji
        node_modules/nodebb-plugin-emoji-android

request  *
Severity: moderate
Server-Side Request Forgery in Request - https://github.com/advisories/GHSA-p8p7-x288-28g6
No fix available
node_modules/request
  coveralls  *
  Depends on vulnerable versions of request
  node_modules/coveralls

7 vulnerabilities (2 moderate, 5 high)

Some issues need review, and may require choosing
a different dependency.

<baris>

@NodeHam said in URGENT, Cannot install on Rocky 9:

@baris , are you one of the developers?

Yes. Send your forum url and I can tell if you have socket.io problems. If you have a configuration issue it will fail to connect and show up in the browser console/network tab.

NodeHam

Can you send me a private message please and I'll send you the url.

NodeHam

I do see this...

<baris>

@NodeHam That's the first time you posted the errors from your browser. That tells me what's wrong. https://github.com/NodeBB/NodeBB/issues/11612

If you are on persona theme try changing to harmony for now.

NodeHam

Hi,

Same thing, cannot accept posts. Similar error in the browser.

<baris>

You need to rebuild and restart after changing the theme.

NodeHam

Overlooked, I'll do it now.

NodeHam

Says it's restarting but it's been a while now. No load on the server so it's not because of that.
Do I need to build/restart or something else from the command line?

NodeHam

I tried switching back to the previous theme so I could compare errors but it went down and now it won't come up.
Looking at the log as I try to start it;

nodebun@nb01:~/nodebb$ ./nodebb log

Hit Ctrl-C to exit


    at Module._findPath (node:internal/modules/cjs/loader:678:18)
    at Module._resolveFilename (node:internal/modules/cjs/loader:1061:27)
    at Module._load (node:internal/modules/cjs/loader:920:27)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/home/nodebun/nodebb/src/plugins/index.js:9:17)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
[cluster] Child Process (3570) has exited (code: 0, signal: null)

<baris>

Type nano logs/output.log and then paste the full error from the bottom of the file.

NodeHam

Every time I try to change the theme from the command line it shows entire sub-directories missing. I know those were there so I don't know what's removing some of the directories.

This is at the developers level now which I am not.

Require stack:
- /home/node/nodebb/node_modules/request-promise-native/lib/rp.js
- /home/node/nodebb/src/plugins/index.js
- /home/node/nodebb/src/groups/index.js
- /home/node/nodebb/src/user/index.js
- /home/node/nodebb/src/events.js
- /home/node/nodebb/src/cli/reset.js
- /home/node/nodebb/src/cli/index.js
- /home/node/nodebb/nodebb
Error: Cannot find module 'stealthy-require'
Require stack:

When I rebuilt, I installed a new setup but there were complaints of missing directories. This one for example;

/node_modules/request-promise-native/lib/rp.js
So I copied those files from the backup I made to put the uploads/... stuff back.

2023-05-17T16:34:55.951Z [4567/1918] - ^[[33mwarn^[[39m: [plugins] "nodebb-plugin-question-and-answer" is active but not installed.
2023-05-17T16:34:56.291Z [4567/1918] - ^[[32minfo^[[39m: [api] Adding 0 route(s) to `api/v3/plugins`
2023-05-17T16:34:56.343Z [4567/1918] - ^[[32minfo^[[39m: [router] Routes added
2023-05-17T16:34:56.352Z [4567/1918] - ^[[32minfo^[[39m: 🎉 NodeBB Ready
2023-05-17T16:34:56.355Z [4567/1918] - ^[[32minfo^[[39m: 🤝 Enabling 'trust proxy'
2023-05-17T16:34:56.359Z [4567/1918] - ^[[32minfo^[[39m: 📡 NodeBB is now listening on: 0.0.0.0:4567
2023-05-17T16:34:56.359Z [4567/1918] - ^[[32minfo^[[39m: 🔗 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;
   │                                                            ^^^^^^^^
   ╵

WARNING: The keyword 'none' must be used as a single argument.
    ../../node_modules/bootstrap/scss/mixins/_box-shadow.scss 10:9   box-shadow()
    ../../node_modules/bootstrap/scss/forms/_form-control.scss 40:7  @import
    bootstrap/scss/_forms.scss 3:9                                   @import
    - 18:9                                                           root stylesheet

This error;
[plugins] "nodebb-plugin-question-and-answer" is active but not installed.
is especially odd because I did re-install that plugin.

I feel like I have to rebuild yet again because something is getting corrupted and it only seems to keep getting worse.