Raid + Nginx + NodeJs fails while running "npm install"

    • Resolved
    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Raid + Nginx + NodeJs

      Hi,

      I use the nginx plugin to serve my dev websites. The websites are stored on a Raid5 build of 3 disks. One of the website uses NodeJS so I installed v8.9.4 (nodejs.org/en/download/package…based-linux-distributions). Afterwards I tried running "npm install" which failed with:

      Source Code

      1. > node-sass@4.7.2 install /sharedfolders/Web/webtrees-2.0/node_modules/node-sass
      2. > node scripts/install.js
      3. Cached binary found at /root/.npm/node-sass/4.7.2/linux-x64-57_binding.node
      4. > uglifyjs-webpack-plugin@0.4.6 postinstall /sharedfolders/Web/webtrees-2.0/node_modules/webpack/node_modules/uglifyjs-webpack-plugin
      5. > node lib/post_install.js
      6. > node-sass@4.7.2 postinstall /sharedfolders/Web/webtrees-2.0/node_modules/node-sass
      7. > node scripts/build.js
      8. Binary found at /sharedfolders/Web/webtrees-2.0/node_modules/node-sass/vendor/linux-x64-57/binding.node
      9. Testing binary
      10. Binary has a problem: Error: /sharedfolders/Web/webtrees-2.0/node_modules/node-sass/vendor/linux-x64-57/binding.node: failed to map segment from shared object
      11. at Object.Module._extensions..node (module.js:672:18)
      12. at Module.load (module.js:556:32)
      13. at tryModuleLoad (module.js:499:12)
      14. at Function.Module._load (module.js:491:3)
      15. at Module.require (module.js:587:17)
      16. at require (internal/module.js:11:18)
      17. at module.exports (/sharedfolders/Web/webtrees-2.0/node_modules/node-sass/lib/binding.js:19:10)
      18. at Object.<anonymous> (/sharedfolders/Web/webtrees-2.0/node_modules/node-sass/lib/index.js:14:35)
      19. at Module._compile (module.js:643:30)
      20. at Object.Module._extensions..js (module.js:654:10)
      Display All

      Digging around I finally found this bug report on node-sass and the proposed solution: github.com/sass/node-sass/issues/1407#issuecomment-255406068

      After updating the /etc/fstab by adding "exec" to the configuration of the Raid, the "npm install" runs fine without any errors.

      All data disks (not only the Raid) are configured this way: defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl,


      Questions:

      :?: Is it save to add this "exec"?
      :?: Why issn't "exec" already added there?
      :?: Will it be removed on some kind of dist upgrade or config change? When is the /etc/fstab updated normally by OMV?
      :?: Is there any other way to set "exec" using the OMV GUI?
    • Sunday wrote:

      Is it save to add this "exec"?
      Why issn't "exec" already added there?
      Will it be removed on some kind of dist upgrade or config change? When is the /etc/fstab updated normally by OMV?
      Is there any other way to set "exec" using the OMV GUI?
      Too many questions, hope they are all answered here

      openmediavault.readthedocs.io/…/various/fs_env_vars.html
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server