Error after upgrading to v1.13.1

Technical Support
  • Hello, i got this error

    1. Updating package.json file with defaults...  OK
    
    2. Bringing base dependencies up to date...  started
    
    > [email protected] install /home/user/forum/nodebb/node_modules/sharp
    > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
    
    info sharp Using cached /home/user/.npm/_libvips/libvips-8.8.1-linux-x64.tar.gz
    internal/modules/cjs/loader.js:638
        throw err;
        ^
    

    What can i do to fix this?

  • Hm, odd... how much memory do you have in your server? Could be it's running out of memory.

    Perhaps try moving node_modules/ to a different folder, then running npm i --production again.

  • After

    apt install make
    apt install g++
    

    it works.

    Looks like sharp need to build some files!?!?!??

     make: Entering directory '/home/user_radforum/radforum/nodebb/node_modules/sharp/build'
       TOUCH Release/obj.target/libvips-cpp.stamp
       CXX(target) Release/obj.target/sharp/src/common.o
       CXX(target) Release/obj.target/sharp/src/metadata.o
       CXX(target) Release/obj.target/sharp/src/stats.o
       CXX(target) Release/obj.target/sharp/src/operations.o
       CXX(target) Release/obj.target/sharp/src/pipeline.o
       CXX(target) Release/obj.target/sharp/src/sharp.o
       CXX(target) Release/obj.target/sharp/src/utilities.o
       SOLINK_MODULE(target) Release/obj.target/sharp.node
       COPY Release/sharp.node
     make: Leaving directory '/home/user_radforum/radforum/nodebb/node_modules/sharp/build'
    

    Why?? First time i need this, i think...

  • It depends on your platform... sharp usually downloads its dependencies, but on unsupported platforms it will need to build its own local copy.

    Perhaps the new version hasn't been updated with downloadable binaries yet 😄

  • I am on Debian Buster 10


Suggested Topics


  • 0 Votes
    2 Posts
    234 Views

    When I updated I forgot to mount config json to store it externally.

  • -1 Votes
    1 Posts
    162 Views

    here is the issue open in git
    https://github.com/NodeBB/NodeBB/issues/9125

    please request to check cluster support before launching update.

  • 0 Votes
    6 Posts
    2k Views

    @julian Unfortunately I ended up nuking the repostory and rechecking it out mulitple times trying to fix it.

    In the future I know I can't trust the database entirely. I'll have to backup all the files (that I thought were ephemeral).

  • 0 Votes
    3 Posts
    2k Views

    Thanks I bumped the memory. seems to work now.

  • Installation Errors

    Technical Support
    0 Votes
    1 Posts
    859 Views

    Installing on a KVM VM, Centos 6 64bit. Followed the tutorial https://docs.nodebb.org/en/latest/installing/os/centos.html

    Getting errors though...

    [root@localhost ~]# curl https://raw.githubusercontent.com/creationix/nvm/v0.13.1/install.sh | bash source ~/.bash_profile % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 101 3442 101 3442 0 0 16694 0 --:--:-- --:--:-- --:--:-- 98342 => Downloading nvm from git to '/root/.nvm' => Initialized empty Git repository in /root/.nvm/.git/ remote: Counting objects: 5491, done. remote: Compressing objects: 100% (7/7), done. Receiving objects: 100% (5491/5491), 1.58 MiB, done. remote: Total 5491 (delta 0), reused 0 (delta 0), pack-reused 5484 Resolving deltas: 100% (3321/3321), done. Note: checking out 'v0.13.1'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at eef12cc... v0.13.1 Deleted branch master (was f9e14b7). => Appending source string to /root/.bash_profile => Close and reopen your terminal to start using nvm [root@localhost ~]# source ~/.bash_profile /usr/bin/which: no node in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/root/bin) [root@localhost ~]# nvm install v0.12.7 # as of this writing check the result of the list-remote to see all choices ######################################################################## 100.0% -bash: manpath: command not found Now using node v0.12.7 [root@localhost ~]# systemctl start redis -bash: systemctl: command not found [root@localhost ~]# [root@localhost ~]# systemctl enable redis -bash: systemctl: command not found'