Skip to content

MogoDB v6 to v7 upgrade

Solved Configure
5 2 2.4k 1
  • wrote on last edited by Panda
    #1

    Running nodeBB on v6 of MongoDB and tried to upgrade to v7
    Is there any benefit to upgrading?

    Anyway I did
    sudo apt update
    and saw these lines (which still references v6?)
    …https://repo.mongodb.org/apt/ubuntu jammy/mongodb-org/6.0 InRelease
    Hit:10 https://repo.mongodb.org/apt/ubuntu jammy/mongodb-org/6.0 Release

    Then
    sudo apt upgrade mongodb
    didnt work

    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    Package mongodb is not available, but is referred to by another package.
    This may mean that the package is missing, has been obsoleted, or
    is only available from another source
    
    E: Package 'mongodb' has no installation candidate
    

    Can anyone explain what failed there?

  • wrote on last edited by
    #2

    Just to add, the server is running Ubuntu. I read something once about Ubuntu having its own list of where it gets updates from?
    Im not sure if that is the case, and is relevant

  • Just to add, the server is running Ubuntu. I read something once about Ubuntu having its own list of where it gets updates from?
    Im not sure if that is the case, and is relevant

    wrote on last edited by
    #3

    @Panda yes, Ubuntu does have its own PPA repository for most software, but not for mongodb. This should help in terms of the upgrade

    https://www.mongodb.com/docs/manual/tutorial/install-mongodb-on-ubuntu/

  • @Panda yes, Ubuntu does have its own PPA repository for most software, but not for mongodb. This should help in terms of the upgrade

    https://www.mongodb.com/docs/manual/tutorial/install-mongodb-on-ubuntu/

    wrote on last edited by
    #4

    @phenomlab ok thanks, so any idea what caused it not to upgrade?

  • @phenomlab ok thanks, so any idea what caused it not to upgrade?

    wrote on last edited by
    #5

    @Panda if you used the Ubuntu PPA, I think this only goes as far as 6.x if I recall correctly.

  • Panda Panda has marked this topic as solved on

Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee ☕
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • Upgrade issues

    Solved Configure nodebb
    2
    1
    2 Votes
    2 Posts
    1k Views
    DownPW
    Use this code git fetch # Grab the latest code from the NodeBB repository git checkout v3.x git reset --hard origin/v3.x And you will have the latest version without specifying it https://docs.nodebb.org/configuring/upgrade/
  • Difficult to move posts now, on mobile.

    Bugs nodebb
    16
    1
    5 Votes
    16 Posts
    5k Views
    phenomlab
    @DownPW Yes, it is. It’s set far too low meaning other elements with a higher preference will sit over the top of it.
  • NodeBB: Upgrading to NodeBB v3.x

    Solved Configure nodebb v3.x
    6
    0 Votes
    6 Posts
    3k Views
    phenomlab
    @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 [image: 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.
  • Upgrade Problem from 2.8.9 to 2.8.10

    Moved Solved Configure upgrade nodebb
    15
    1
    1 Votes
    15 Posts
    4k Views
    phenomlab
    @cagatay Were any errors displayed during the upgrade process?
  • Upgrade Problem from 2.8.3 to 2.8.4

    Solved Configure nodebb
    35
    1
    8 Votes
    35 Posts
    12k Views
    phenomlab
    @cagatay No, you can ignore that.
  • Custom badges

    Solved Customisation nodebb
    103
    2
    49 Votes
    103 Posts
    60k Views
    DownPW
    Perfect
  • who is read NodeBB

    Customisation read post nodebb
    6
    0 Votes
    6 Posts
    3k Views
    phenomlab
    @cagatay You should ask in the NodeBB forums. Perhaps reference this post https://discuss.flarum.org/d/23066-who-read
  • NodeBB vs Discourse

    Chitchat nodebb discourse board
    25
    6 Votes
    25 Posts
    14k Views
    RiekMedia
    @phenomlab said in NodeBB vs Discourse: Hetzner eh ? I use them also. In fact, Sudonix is hosted in Nuremberg yes i’m also at hetzner, i have been a customer there for years with a reseller account for domains. My VPS that I host there are also in Nuremberg