How to fix the warnings displayed in Dev tools?

Technical Support

Suggested Topics


  • 0 Votes
    7 Posts
    430 Views

    Your vm may have suffered an unclean shutdown. Note "may". In absence of more info, a couple things to try.

    If you have nodebb set up to be launched via systemd, disable that. And then stop just for good measure and then disable dependencies:

    systemctl disable nodebb systemctl stop nodebb systemctl disable nginx (sub apache if using apache) systemctl disable mongod (or whatever db backend you're using

    Then reboot the vm. When it comes back up we're going to restart all that in reverse order, verifying each is up and running before proceeding to next:

    systemctl status mongod systemctl status nginx systemctl status nodebb

    Those should now all report "disabled". So let's start them up, verifying each launches w/o error before proceeding to next

    systemctl start mongod

    If the startup messages are greek to you or pass by too quickly:

    systemctl status mongod

    Should report something very close to this:

    [root@forums ~]# systemctl status mongod ā— mongod.service - MongoDB Database Server Loaded: loaded (/usr/lib/systemd/system/mongod.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2021-03-05 06:57:52 UTC; 1 weeks 6 days ago Docs: https://docs.mongodb.org/manual Process: 457777 ExecStart=/usr/bin/mongod $OPTIONS (code=exited, status=0/SUCCESS) Process: 457762 ExecStartPre=/usr/bin/chmod 0755 /var/run/mongodb (code=exited, status=0/SUCCESS) Process: 457739 ExecStartPre=/usr/bin/chown mongod:mongod /var/run/mongodb (code=exited, status=0/SUCCESS) Process: 457725 ExecStartPre=/usr/bin/mkdir -p /var/run/mongodb (code=exited, status=0/SUCCESS) Main PID: 457824 (mongod) CGroup: /system.slice/mongod.service ā””ā”€457824 /usr/bin/mongod -f /etc/mongod.conf ā€£ 457824 /usr/bin/mongod -f /etc/mongod.conf

    If that all looks good, try starting nodebb:

    systemctl start nodebb

    A status check should look something like this:

    [root@forums ~]# systemctl status nodebb ā— nodebb.service - NodeBB Loaded: loaded (/etc/systemd/system/nodebb.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2021-03-05 06:59:17 UTC; 1 weeks 6 days ago Docs: https://docs.nodebb.org Process: 459055 ExecStart=/usr/bin/env node loader.js (code=exited, status=0/SUCCESS) Main PID: 459071 (node) CGroup: /system.slice/nodebb.service ā”œā”€459071 /usr/bin/node /opt/nodebb/loader.js ā”œā”€459082 /usr/bin/node /opt/nodebb/app.js

    If you are getting anything other than "SUCCESS" then stop just be sure:

    systemctl stop nodebb

    Then sudo to change to your nodebb user and then go try starting nodebb manually using the "log" flag:

    cd /where/ever/your/nodebb/lives ./nodebb start -l

    Then copy/pasta the ensuing spewage so the other gurus in the lurking can deconstruct. Good luck.

    Once you get this sorted, be sure to re-enable those services else they will not automatically restart after a shutdown/reboot.

    systemctl enable mongod systemctl enable nginx systemctl enable nodebb

    I'd even then reboot after that just to be sure all comes back up as expected.

    Yeah, this is not issue specific but when dealing with unknown glitches it is nice to rule out some low hanging fruit to help isolate.

  • 0 Votes
    4 Posts
    369 Views

    Sorry, I didn't really process your full message. At the end you state your guess these are users with connection problems who got reconnected... based on the relatively small number of times I see this warning, as compared to over-all traffic to the forum, it sounds like I can probably ignore the warning. Thanks for your help.

  • 0 Votes
    1 Posts
    2k Views

    I am spinning up a new community and found the following warnings during my install.

    Anything I should do about these?

    [root@bna-com ~]# nvm install v7.2.0 ######################################################################## 100.0% Computing checksum with sha256sum Checksums matched! Now using node v7.2.0 (npm v3.10.9) Creating default alias: default -> v7.2.0 [root@bna-com ~]# cd /opt/bnacmty/ [root@bna-com bnacmty]# git clone -b v1.x.x https://github.com/NodeBB/NodeBB nodebb Cloning into 'nodebb'... remote: Counting objects: 112796, done. remote: Compressing objects: 100% (101/101), done. remote: Total 112796 (delta 38), reused 2 (delta 2), pack-reused 112693 Receiving objects: 100% (112796/112796), 34.86 MiB | 9.87 MiB/s, done. Resolving deltas: 100% (84665/84665), done. [root@bna-com bnacmty]# cd nodebb [root@bna-com nodebb]# npm install npm WARN deprecated [email protected]: use uuid module instead npm WARN deprecated [email protected]: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years. npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree. [email protected] /opt/bnacmty/nodebb
  • 0 Votes
    29 Posts
    8k Views

    @PitaJ FTW:

    0_1476826201479_Post_tools_shortlink.png

    Thanks for the tip about bootbox!

  • 0 Votes
    7 Posts
    3k Views

    @psychobunny I hate to dig up this old topic but I'm interested in allowing users to display up to two badges in their posts as well.
    I'm pretty new to NodeBB and am not sure where to start make changes. Could you point me in the right direction?
    Thanks!