Skip to content

NodeBB Mess / Mongo DB

Solved Configure
  • Hi,

    Basically my nodebb installation I felt was a mess…Nothing was installing and so I decided to make a clean install. I thought that i had cleared mongodb but i am now thinking not properly.

    I ran use nodebb and then db.dropDatabase(); I had problems deleting the user nodebb also.

    Anyway I tried to reinstall but all traces of the old install was still there on the page. Not the browser as cleared all and tried others. Tried upgrading it but nothing was happening…all a mess 👎

    I am here. Deleted the nodebb folder and then tried again to db.dropDatabase(); in mongo. But i do that and get success but when i run show dbs nodebb is still there. 0.00 in it but still there. Is it traces of that db that is messing with the page? Showing parts of the old stuff? I cannot delete that mongo db. Do i have to delete user too? Don’t think that would matter but the db for sure i guess?

    Thanks guys.

  • @phenomlab Hi, yes i selected the db first.

    I have software also on the GUI that can delete and drop the db. A few seconds later when i refresh the db is back again.

    I tried all again and on ./nodebb setup it gets worse. I created the user again (with admin) Only thing i cannot start fresh is the db itself.

    2022-08-18T15:56:38.659Z [3984] - warn: NodeBB Setup Aborted.
     MongoServerError: Authentication failed.
        at Connection.onMessage (/home/smiley/nodebb/node_modules/mongodb/lib/cmap/connection.js:210:30)
        at MessageStream.<anonymous> (/home/smiley/nodebb/node_modules/mongodb/lib/cmap/connection.js:63:60)
        at MessageStream.emit (events.js:375:28)
        at processIncomingData (/home/smiley/nodebb/node_modules/mongodb/lib/cmap/message_stream.js:132:20)
        at MessageStream._write (/home/smiley/nodebb/node_modules/mongodb/lib/cmap/message_stream.js:33:9)
        at writeOrBuffer (internal/streams/writable.js:358:12)
        at MessageStream.Writable.write (internal/streams/writable.js:303:10)
        at Socket.ondata (internal/streams/readable.js:726:22)
        at Socket.emit (events.js:375:28)
        at addChunk (internal/streams/readable.js:290:12)
    

    I have nothing there so destroying it all and starting again is no problem but I need to remove all traces and from mongo too.

    ####QUICK UPDATE### I just rebooted my machine and have managed to dlete the db and the user…I will try and install again and see if i get this error.

  • @Sampo2910 Did you do it via the below method ? If you didn’t select a database first, then the drop doesn’t normally succeed.

    > use nodebb; 
    > db.dropDatabase();
    
  • @phenomlab Hi, yes i selected the db first.

    I have software also on the GUI that can delete and drop the db. A few seconds later when i refresh the db is back again.

    I tried all again and on ./nodebb setup it gets worse. I created the user again (with admin) Only thing i cannot start fresh is the db itself.

    2022-08-18T15:56:38.659Z [3984] - warn: NodeBB Setup Aborted.
     MongoServerError: Authentication failed.
        at Connection.onMessage (/home/smiley/nodebb/node_modules/mongodb/lib/cmap/connection.js:210:30)
        at MessageStream.<anonymous> (/home/smiley/nodebb/node_modules/mongodb/lib/cmap/connection.js:63:60)
        at MessageStream.emit (events.js:375:28)
        at processIncomingData (/home/smiley/nodebb/node_modules/mongodb/lib/cmap/message_stream.js:132:20)
        at MessageStream._write (/home/smiley/nodebb/node_modules/mongodb/lib/cmap/message_stream.js:33:9)
        at writeOrBuffer (internal/streams/writable.js:358:12)
        at MessageStream.Writable.write (internal/streams/writable.js:303:10)
        at Socket.ondata (internal/streams/readable.js:726:22)
        at Socket.emit (events.js:375:28)
        at addChunk (internal/streams/readable.js:290:12)
    

    I have nothing there so destroying it all and starting again is no problem but I need to remove all traces and from mongo too.

    ####QUICK UPDATE### I just rebooted my machine and have managed to dlete the db and the user…I will try and install again and see if i get this error.

  • Well no idea…after rebooting machine several times and several times of doing the same thing…( at least I think it was lol 🙂 ) Here w are again.

    Fell free to purge this post as it serves no purpose other than reminding of my own mistakes haha… Sorry for the fuss but really dont know what happened.

    2022-08-18 19_21_51-Home _ NodeBB.png

  • @Sampo2910 That looks like an authentication issue - is the password correct - can you provide the command you used to create the database ?

    Should be something like

    db.createUser( { user: "sudonixtest", pwd: "lkjklj9995485469dffgkjk-201x", roles: [ { role: "readWrite", db: "sudonixtest" }, { role: "clusterMonitor", db: "admin" } ] } )
    

    m

  • @Sampo2910 said in NodeBB Mess / Mongo DB:

    ####QUICK UPDATE### I just rebooted my machine and have managed to dlete the db and the user…I will try and install again and see if i get this error.

    🙂 That sounds like a database deadlock. If you have records in use, then of course, the drop will fail unless it’s forced.

    Glad to hear it’s sorted.

  • @phenomlab What amazes me and this is pretty much everytime with NodeBB haha. The VERY FIRST THING I try to do…Just makes me feel stupid. Surely this cant be just me haha.

    2022-08-18 19_40_07-Extend _ Plugins _ NodeBB Admin Control Panel.png

  • @Sampo2910 🙂 You’ll get that error if the .json file isn’t updated for latest release compliance - but you can still install from the CLI by using npm install nodebb-plugin-whateveritis

  • phenomlabundefined phenomlab has marked this topic as solved on

Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • NodeBB: Opening the Composer for replies

    Solved Configure
    2
    0 Votes
    2 Posts
    289 Views

    @mventures Quick reply is basically exactly that. However, it’s possible to trigger the full composer as below

    82ca1209-31be-4a51-a641-9887b5a238b8-image.png

    Failing that, you’ll need to use the reply button in the sticky toolbar

    1d230bcb-ff8e-4756-94f7-6e2fb7a94bc4-image.png

  • NodeBB: Upgrading to NodeBB v3.x

    Solved Configure
    6
    0 Votes
    6 Posts
    315 Views

    @mventures You’d need to connect to the server and execute it directly - not on your local terminal. Review the guide below, which will show you how to gain access via SSH to your server

    https://docs.ovh.com/gb/en/dedicated/ssh-introduction/

    Once you have access, you’ll need to navigate to the actual folder where NodeBB is installed

    You’ll then need to change to the directory as shown below

    /home/unbuntu/nodebb

    fdffe673-bf63-4b6d-a728-5506fddc1aff-image.png

    In most cases, initial access takes you to the root of the file system. You can always issue pwd in a Linux terminal which will show you the Present Working Directory. From there, you can issue the command

    cd /home/ubuntu/nodebb

    Once in the NodeBB directory, you’d use the below commands

    ./nodebb stop git fetch && git checkout develop && git reset --hard origin/develop ./nodebb upgrade ./nodebb start

    Line 1 stops the NodeBB instance
    Line 2 gets the latest files from GIT (repository) and then checks out the development branch. It then resets the version you are using to the development branch ready for v3
    Line 3 Runs the upgrade once the new branch is set, and code pulled
    Line 4 Restarts the NodeBB instance after the upgrade has completed

    Note that when you restart NodeBB and log back in, things will look very different to what you had in v2.

  • NodeBB: Privileges for the Announcement channel

    Solved Configure
    6
    1 Votes
    6 Posts
    288 Views

    Up to you really 🙂

  • restarting nodebb on boot

    Unsolved Configure
    3
    1 Votes
    3 Posts
    298 Views

    @eeeee said in restarting nodebb on boot:

    can I just run nodebb under nodemon for auto restarts?

    It’s a better method. Nodemon just looks for file system changes and would effectively die if the server was rebooted meaning you’d have to start it again anyway. Systemd is the defacto standard which is how the operating system interacts in terms of services, scheduled tasks etc.

  • Viewing Permission.

    Solved General
    33
    12 Votes
    33 Posts
    2k Views

    @phenomlab

    Ah Mark you are a star. Thank you very much. I just logged on and seen someone had worked their magic 🙂

    Again it is very much appreciated.

  • nodebb dropdown menu

    Solved Configure
    5
    0 Votes
    5 Posts
    525 Views

    @phenomlab said in nodebb dropdown menu:

    @kurulumu-net You set it like the below example taken from this site

    aae36790-3257-4bb2-ad5a-0d744309876a-image.png

    Which presents this

    77f47260-2941-4afe-9614-8e17dcfc8c19-image.png

    Very interesting…

    I actually thought this wasn’t possible, as I remember it being asked in the NodeBB forum.

    Is this something new that’s been implemented? I’ll 100% be doing that when I’m on the laptop over the weekend.

  • Iframely (Nodebb)

    Solved Configure
    40
    4 Votes
    40 Posts
    3k Views

    @DownPW This is now resolved. The issue was an incorrect URL specified in the Nodebb plugin. I’ve corrected this, and now it works as intended.

  • 3 Votes
    4 Posts
    553 Views

    @cagatay same here. Was previously an IONOS user, but moved to Hetzner to realise both savings and performance increase and have never looked back.