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 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.

  • @cagatay Sorry - my mistake.

    wrote on last edited by
    #21

    @phenomlab not fixed yet.

  • @phenomlab not fixed yet.

    wrote on last edited by
    #22

    @cagatay are you installing this plugin as root, or as the user running NodeBB?


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
  • NodeBB recent cards customisation

    Solved Customisation nodebb recent cards
    3
    1
    2 Votes
    3 Posts
    1k Views
    JAC
    @phenomlab thank you very much for the assistance Mark, massively appreciated as always. The great thing about this is it’s all documented for other NodeBB users that come looking for solutions . Looks far better .
  • 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.
  • Page control arrows for PWA

    Solved Customisation nodebb
    27
    25 Votes
    27 Posts
    15k Views
    phenomlab
    @crazycells it is, yes - I think I’ll leave it as there is no specific PWA CSS classes I know of. Well, you could use something like the below, but this means multiple CSS files for different operating systems. /** * Determine the mobile operating system. * This function returns one of 'iOS', 'Android', 'Windows Phone', or 'unknown'. * * @returns {String} */ function getMobileOperatingSystem() { var userAgent = navigator.userAgent || navigator.vendor || window.opera; // Windows Phone must come first because its UA also contains "Android" if (/windows phone/i.test(userAgent)) { return "Windows Phone"; } if (/android/i.test(userAgent)) { return "Android"; } if (/iPad|iPhone|iPod/.test(userAgent) && !window.MSStream) { return "iOS"; } return "unknown"; // return “Android” - one should either handle the unknown or fallback to a specific platform, let’s say Android } Once you’re in that rabbit hole, it’s impossible to get out of it.
  • 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
  • Interesting Widget code, but can't fetch API

    Solved Customisation nodebb
    26
    2 Votes
    26 Posts
    11k Views
    phenomlab
    @Panda said in Interesting Widget code, but can’t fetch API: How did you drop that widget into the post there? I hadnt seen this BSgenerator anywhere on sudonix site, do you use it somewhere already? Yes, here https://sudonix.org/topic/414/corporate-bullshit-generator?_=1687774393044 It’s not a “post” or “topic” in the common sense. It is actually a page in it’s own right and leverages nodebb-plugin-custom-pages. This in turn creates a new “route” which behaves like a page, meaning it is then exposed for widgets. @Panda said in Interesting Widget code, but can’t fetch API: Also can you explain more what you mean by calling the code externally. In my API call example, how would I go about doing that? By this, I mean create all the required code in an external JS file that is reachable by the NodeBB instance - so, in “public” for example - or in my case /public/js. The widget then “calls” that file and because it runs outside of the scope of NodeBB, you just need to return the values to the widget. Hope this makes sense?
  • NodeBB upgrade now cant post

    Solved Bugs nodebb
    5
    2 Votes
    5 Posts
    2k Views
    phenomlab
    @Panda yes, for some reason, that is the case. If you need an urgent response, it’s probably better to post here because of the time difference.
  • 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.
  • NodeBB 3.0 alpha1 : Error on install

    Solved Configure nodebb version 3 install error
    19
    2 Votes
    19 Posts
    7k Views
    DownPW
    @phenomlab Work now