Skip to content

Upgrade Problem from 2.8.3 to 2.8.4

Solved Configure
35 3 11.6k 1
  • wrote on last edited by
    #1

    This is my problem that faced when upgrade from 2.8.3 to 2.8.4.

    e7f8bb6c-82d3-48c5-bf38-070e5149f2f0-image.png

  • wrote on last edited by
    #27

    You are getting that message because you have the three plugins below installed which all depend on nodebb-plugin-emoji so you cannot remove the main plugin without first removing those

    1679316592601-a88285fb-6417-419a-9f27-731cae619e78-image.png

    I’ve done it for you anyway 🙂

    image.png

    You should be able to upgrade now.

  • This is my problem that faced when upgrade from 2.8.3 to 2.8.4.

    e7f8bb6c-82d3-48c5-bf38-070e5149f2f0-image.png

    wrote on last edited by
    #2

    @cagatay that looks very much like a permissions error. Are you attempting the upgrade as the user running NodeBB ?

  • wrote on last edited by DownPW
    #3

    Seems to be a permission problem.

    test ./nodebb upgrade command with root user. (not good but I have this problem one time ago resolved like this) (Mark will yell at me 🙂 )

    go to normal nodebb user and ./nodebb upgrade again

  • @cagatay that looks very much like a permissions error. Are you attempting the upgrade as the user running NodeBB ?

    wrote on last edited by
    #4

    @phenomlab its very interesting but upgrade is done when i login admin panel and nodebb is working without problem.

    so sould i upgrade again by root?

    PS: i always use user not root but user has sudo command 🙂

  • @phenomlab its very interesting but upgrade is done when i login admin panel and nodebb is working without problem.

    so sould i upgrade again by root?

    PS: i always use user not root but user has sudo command 🙂

    wrote on last edited by
    #5

    @cagatay If the upgrade appears to have worked, then you don’t need to run it again, but I would certainly take a look at the nodebb-plugin-emoji issue in more detail as this is 100% a permissions issue

    4d5466ed-cbe5-4752-b90c-0b239e40b3e8-image.png

  • @cagatay If the upgrade appears to have worked, then you don’t need to run it again, but I would certainly take a look at the nodebb-plugin-emoji issue in more detail as this is 100% a permissions issue

    4d5466ed-cbe5-4752-b90c-0b239e40b3e8-image.png

    wrote on last edited by cagatay
    #6

    @phenomlab faced same problem for upgrade to 2.8.5

    f770a39a-e568-4073-9995-576d0b6034a5-image.png

    Mark do you have this plugin on Sudonix? And which version are you running?

  • @phenomlab faced same problem for upgrade to 2.8.5

    f770a39a-e568-4073-9995-576d0b6034a5-image.png

    Mark do you have this plugin on Sudonix? And which version are you running?

    wrote on last edited by
    #7

    @cagatay Yes, I do, but it’s not a version issue - it’s permissions.

  • @cagatay Yes, I do, but it’s not a version issue - it’s permissions.

    wrote on last edited by cagatay
    #8

    @phenomlab permission for user right? so i did not change any permison for nodebb user so why it caused or what i should do for to give permision to nodebb user? till 2.8.2 nodebb user can upgrade any permission case what happened with 2.8.4 🙂

  • @phenomlab permission for user right? so i did not change any permison for nodebb user so why it caused or what i should do for to give permision to nodebb user? till 2.8.2 nodebb user can upgrade any permission case what happened with 2.8.4 🙂

    wrote on last edited by
    #9

    @cagatay are you able to remove that plugin and reinstall or does it present the same error?

  • @cagatay are you able to remove that plugin and reinstall or does it present the same error?

    wrote on last edited by
    #10

    @phenomlab yeap i removed the plugin and reinstall it problem is fixed.

  • phenomlab phenomlab has marked this topic as solved on
  • @cagatay are you able to remove that plugin and reinstall or does it present the same error?

    wrote on last edited by
    #11

    @phenomlab i deleted emoji plugin but while upgraded to 2.8.6 faced same problem.
    cant understand whats going on.

  • @phenomlab i deleted emoji plugin but while upgraded to 2.8.6 faced same problem.
    cant understand whats going on.

    wrote on last edited by
    #12

    @cagatay can you provide the logs?

  • @cagatay can you provide the logs?

    wrote on last edited by
    #13

    @phenomlab from now like this;

    71faca9a-4e66-4c73-b521-084272c6ab0a-image.png

    but when upgrading;

    97aa618c-efd9-4edd-be72-a294d35a303d-image.png

  • @phenomlab from now like this;

    71faca9a-4e66-4c73-b521-084272c6ab0a-image.png

    but when upgrading;

    97aa618c-efd9-4edd-be72-a294d35a303d-image.png

    wrote on last edited by
    #14

    @cagatay does it work if you remove this plugin, perform the upgrade, and then put it back afterwards?

  • @cagatay does it work if you remove this plugin, perform the upgrade, and then put it back afterwards?

    wrote on last edited by
    #15

    @phenomlab i removed the plugin then upgraded but faced same eror…

  • @phenomlab i removed the plugin then upgraded but faced same eror…

    wrote on last edited by DownPW
    #16

    @cagatay @phenomlab

    Maybe reset permissions on all nodebb directory like this ?

    chown -R yournodebbuser:yournodebbuser /home/youruser/yournodebbdirectory
    
    chown -R nodes:nodes /home/nodes/nodebb
    

    because I see permissions error on /home/nodes/nodebb/builds/.... in the last screenshot

    And .upgrade and or rebuild nodebb

    ??

  • @cagatay @phenomlab

    Maybe reset permissions on all nodebb directory like this ?

    chown -R yournodebbuser:yournodebbuser /home/youruser/yournodebbdirectory
    
    chown -R nodes:nodes /home/nodes/nodebb
    

    because I see permissions error on /home/nodes/nodebb/builds/.... in the last screenshot

    And .upgrade and or rebuild nodebb

    ??

    wrote on last edited by
    #17

    @DownPW yes, but we really need to understand why and how these permissions are changing.

  • @DownPW yes, but we really need to understand why and how these permissions are changing.

    wrote on last edited by phenomlab
    #18

    @DownPW @cagatay I found the reason why. This plugin is in fact faulty. I installed it myself because I wanted to add that feature to Sudonix. Not only does it push socket.io through the roof (and adds at least 2 seconds lag to each transaction)

    https://community.nodebb.org/topic/10225/nodebb-plugin-reactions-reactions-plugin-for-nodebb/60?_=1675778336803

    It also is impossible to remove by using the GUI - see my experience below, which is exactly the same as @cagatay

    5b8bb524-bc24-4376-8f57-9c5656c1d96c-image.png

    Not great. The only way to remove this cleanly is from the CLI

    npm remove @nodebb/nodebb-plugin-reactions
    ./nodebb build
    ./nodebb restart
    

    I remember flagging this a while back - it’s here

    https://github.com/NodeBB/NodeBB/issues/10582

    And here (one I raised)

    https://github.com/NodeBB-Community/nodebb-plugin-reactions/issues/8

    So, my advice is NOT to use this plugin currently as the unnecessary load it places on your forum isn’t worth the functionality it provides.

  • @DownPW @cagatay I found the reason why. This plugin is in fact faulty. I installed it myself because I wanted to add that feature to Sudonix. Not only does it push socket.io through the roof (and adds at least 2 seconds lag to each transaction)

    https://community.nodebb.org/topic/10225/nodebb-plugin-reactions-reactions-plugin-for-nodebb/60?_=1675778336803

    It also is impossible to remove by using the GUI - see my experience below, which is exactly the same as @cagatay

    5b8bb524-bc24-4376-8f57-9c5656c1d96c-image.png

    Not great. The only way to remove this cleanly is from the CLI

    npm remove @nodebb/nodebb-plugin-reactions
    ./nodebb build
    ./nodebb restart
    

    I remember flagging this a while back - it’s here

    https://github.com/NodeBB/NodeBB/issues/10582

    And here (one I raised)

    https://github.com/NodeBB-Community/nodebb-plugin-reactions/issues/8

    So, my advice is NOT to use this plugin currently as the unnecessary load it places on your forum isn’t worth the functionality it provides.

    wrote on last edited by
    #19

    @phenomlab i dont have this plugin Mark. So the problem is currently continue.

  • @phenomlab i dont have this plugin Mark. So the problem is currently continue.

    wrote on last edited by
    #20

    @cagatay Sorry - my mistake.


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
  • MogoDB v6 to v7 upgrade

    Solved Configure nodebb
    5
    1 Votes
    5 Posts
    2k Views
    phenomlab
    @Panda if you used the Ubuntu PPA, I think this only goes as far as 6.x if I recall correctly.
  • What plugins are being used here on Sudonix?

    Solved General nodebb plugins development
    6
    5 Votes
    6 Posts
    2k Views
    phenomlab
    @Roki-Antic Welcome! This site isn’t running Persona, but Harmony - a very heavily customised version at that. Do you have a URL where your site is currently located that is publicly accessible? Feel free to PM this info if you do not want to disclose here. Happy to help with any customisation needs.
  • mongodb backup problem

    Moved Configure mongodb
    3
    1
    1 Votes
    3 Posts
    1k Views
    phenomlab
    You might want to also review this post https://sudonix.org/topic/389/mongodb-backup-script
  • 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.
  • Setting up a beta NodeBB v3 environment

    Moved Let's Build It nodebb upgrades beta1
    14
    3
    11 Votes
    14 Posts
    6k Views
    phenomlab
    @dave1904 excellent news. Thanks for the feedback
  • what does sound/mute button do?

    Solved Customisation nodebb
    20
    1
    9 Votes
    20 Posts
    6k Views
    phenomlab
    @crazycells Yeah, looking at the plugin itself, that’s a hard coded limit [image: 3d6dbc10-185b-4102-9470-0c2731a10750-image.png] I’ll probably remove that… eventually…