Skip to content

URGENT, Cannot install on Rocky 9

General Discussion
  • You can ignore those scss warnings, they will be fixed once bootswatch updates their scss files.

  • 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-native and 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?

  • @NodeHam did you stop NodeBB before attempting the upgrade?

  • Yes, I always do.
    I just found it crashed again. This time, when I restarted it, now it shows that it's running 3.1.4.
    I'll keep the log open in a shell session and maybe catch some error.

  • So far, no problems since it stopped. I should not say it crashed, only that I found it stopped but it's been working since.

  • Well, I just found it crashed again. It seemed to be running fine then this.

    e01231f3-a279-4f8a-9404-67e069124116-image.png

    While this seems to be OS related, the forum won't come up. I then ran 'nodebb build' and restarted it and it came up but with some errors.

    2023-06-07T19:18:37.188Z [4567/1968] - 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-06-07T19:18:37.545Z [4567/1968] - info: [api] Adding 1 route(s) to api/v3/plugins
    2023-06-07T19:18:37.600Z [4567/1968] - info: [router] Routes added
    2023-06-07T19:18:37.612Z [4567/1968] - info: 🎉 NodeBB Ready
    2023-06-07T19:18:37.616Z [4567/1968] - info: 🤝 Enabling 'trust proxy'
    2023-06-07T19:18:37.622Z [4567/1968] - info: 📡 NodeBB is now listening on: 0.0.0.0:4567

    And it keeps showing warnings;

    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
    
    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-select.scss 31:7  @import
        bootstrap/scss/_forms.scss 4:9                                  @import
        - 18:9                                                          root stylesheet
    
    DEPRECATION WARNING on line 62, column 208 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.
       ╷
    62 │ $font-family-sans-serif:      "Source Sans Pro", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol" !default !default;
       │                                                                                                                                                                                                                ^^^^^^^^
       ╵
    
    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;
        │                                                               ^^^^^^^^
        ╵
    
    
  • @NodeHam Are you sure you added the forum to autorun when you restart the server?

    This warnings from bootswatch about errors in default styles, you can ignore this.

  • What's autorun? I just run './nodebb start'

  • @NodeHam it's essentially systemd which is a daemon like a startup script that executes when the server reboots.

  • LOL, I thought a nodebb option was being mentioned.
    Yes, I usually have it set as a service but I wanted to monitor it for a while before doing that on the new server.


Suggested Topics


  • 4 Votes
    9 Posts
    3k Views
    Per0xP
    @ᴅᴀʀᴛʜ-ᴠᴀᴅᴇʀ It probably crashes because of the plugins you installed and nodebb can't find them (nodebb-theme-oxide in particular) I suggest you backup the redis database by copying the /data folder somewhere, then delete the contents of the original folder and also remove the config.json volume. Erase and restart redis and nodebb container (It should be like a fresh install) then installs the plugins and themes listed in the log file (nodebb-plugin-teamspeak-verify, nodebb-widget-search-bar, nodebb-theme-oxide, etc) When all plugins are installed and enabled, stop the nodebb container and restore the /data redis database with your backup, and remap config.json volume and I think it should be up. Next time you want to upgrade, disable all plugins before restarting the container with the new image.
  • Install NodeBB Forum

    General Discussion
    4
    0 Votes
    4 Posts
    4k Views
    J
    @per0x ?
  • Installation problem

    General Discussion
    8
    0 Votes
    8 Posts
    3k Views
    SANTO007S
    Thanks to @a_5mith and @Peter-Zoltan-Keresztes
  • Can't get the install done...

    General Discussion
    11
    0 Votes
    11 Posts
    5k Views
    S
    @a_5mith True, but honestly, it's easier to set up a quick Linux VM (and I say this as someone who is not at all a fan of Linux) and the support is far better.
  • [solved] NPM install killed during recent install

    Bug Reports
    3
    0 Votes
    3 Posts
    3k Views
    T
    @julian That's got to be it, thanks mate!

Looks like your connection to NodeBB Community was lost, please wait while we try to reconnect.