Build Failure in BrainVisualizer session_fresh source install


#1

Dear HBP community,

I’ve been trying to reinstall NRP from source code since 2020/4/30,
but keep facing with the same problem during 9. Build NRP by command

./configure_nrp # don’t answer N to the question about creating a local database (if you answer nothing, it assumes Y)
and
./update_nrp build all

I’ve checked my permission to the directory of /home/gary0517/Documents/NRP/brainvisualizer/node_modules
and seems no problem,

Is there any way to solve the problem?

Thank you very much,

Best Regards.


#2

Error code for ./configure_nrp

Removing existing config files for nginx, ExDFrontend, ExDBackend, CLE, nrpBackendProxy and the gzserver/gzbridge scripts.
Would you like to NOT backup your local versions? (this also purges your existing backups) (y/N)

  • Stopping nginx nginx [ OK ]
    Backed up /home/gary0517/Documents/NRP/ExDFrontend/app/config.json.bak9
    Backed up /home/gary0517/Documents/NRP/CLE/hbp_nrp_cle/hbp_nrp_cle/config.ini.bak9
    Backed up /home/gary0517/Documents/NRP/nrpBackendProxy/config.json.bak9
    Backed up /home/gary0517/Documents/NRP/ExDBackend/hbp-flask-restful-swagger-master/flask_restful_swagger/static/config.json.bak9
    Backed up /home/gary0517/Documents/NRP/VirtualCoach/hbp_nrp_virtual_coach/hbp_nrp_virtual_coach/config.json.bak9
    DONE
    mkdir: created directory ‘/home/gary0517/.local/etc/nginx’
    mkdir: created directory ‘/home/gary0517/.local/etc/default’
    mkdir: created directory ‘/home/gary0517/nginx’
    mkdir: created directory ‘/home/gary0517/.local/var/log/nginx’
    mkdir: created directory ‘/home/gary0517/.local/etc/nginx/lua’
    mkdir: created directory ‘/home/gary0517/.local/etc/nginx/conf.d’
    mkdir: created directory ‘/home/gary0517/.opt/bbp’
    Copying user_makefile to python repos
    Copying Frontend config.json file
    Copying start/stop scripts for gzserver and gzbridge
    Copying CLE config.ini file
    Copying hbp-flask-restful config files.
    Copying Proxy config files.
    Copying Nginx config files
    Copying uwsgi config file
    Copying VirtualCoach config.json file
    Copying VirtualCoach bbpclient
    Generating schema parsers for ExDBackend
    Python for http://schemas.humanbrainproject.eu/SP10/2014/BIBI requires 1 modules
    Python for http://schemas.humanbrainproject.eu/SP10/2014/ExDConfig requires 2 modules
    Python for http://schemas.humanbrainproject.eu/SP10/2017/environment_model_config requires 1 modules
    Python for http://schemas.humanbrainproject.eu/SP10/2017/robot_model_config requires 1 modules
    Would you like to setup your local storage database with a default user? (Y/n)
    Setting up local storage database
    STORAGE_PATH is set to ‘/home/gary0517/.opt/nrpStorage’
    /home/gary0517/Documents/NRP/user-scripts/nrp_functions: line 551: node_modules/ts-node/dist/bin.js: No such file or directory
    ERROR
    Would you like to apply the XML transfer function migration script to your local experiments? (y/N)
    Skipping…
    Setting configuration files to default mode (offline mode)
    Editing Backend config.json
    Editing nginx conf files
    Using the proxy config file containing your localhost as backend, and your FS as storage
  • Restarting nginx nginx [fail]
    Done
    DONE

Warning: your running mode has been switched to full local (2).
you might want to run running_mode to change it.


#3

Error for ./update_nrp build all


brainvisualizer

up to date in 1.012s
found 0 vulnerabilities

npm WARN deprecated request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated grunt-ng-annotate@3.0.0: grunt-ng-annotate is deprecated. Switch to babel-plugin-angularjs-annotate or provide annotations by yourself.
npm WARN deprecated coffee-script@1.10.0: CoffeeScript on NPM has moved to “coffeescript” (no hyphen)
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated istanbul@0.4.5: This module is no longer maintained, try this instead:
npm WARN deprecated npm i nyc
npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated fsevents@1.2.12: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated circular-json@0.5.9: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated nodemailer@2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated request@2.74.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated request@2.75.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated mailcomposer@4.0.1: This project is unmaintained
npm WARN deprecated socks@1.1.9: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated uws@9.14.0: New code is available at github.com/uNetworking/uWebSockets.js
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated buildmail@4.0.1: This project is unmaintained
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN notsup Unsupported engine for got@5.7.1: wanted: {“node”:">=0.10.0 <7"} (current: {“node”:“8.17.0”,“npm”:“6.13.4”})
npm WARN notsup Not compatible with your version of node/npm: got@5.7.1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
npm WARN brainvisualizer@3.0.0 No repository field.
npm WARN brainvisualizer@3.0.0 license should be a valid SPDX license expression

npm ERR! code EACCES
npm ERR! syscall rename
npm ERR! path /home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/npm-2f4b5433/node_modules/which
npm ERR! dest /home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/which-a273e105
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/npm-2f4b5433/node_modules/which’ -> ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/which-a273e105’
npm ERR! { Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/npm-2f4b5433/node_modules/which’ -> ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/which-a273e105’
npm ERR! cause:
npm ERR! { Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/npm-2f4b5433/node_modules/which’ -> ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/which-a273e105’
npm ERR! errno: -13,
npm ERR! code: ‘EACCES’,
npm ERR! syscall: ‘rename’,
npm ERR! path: ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/npm-2f4b5433/node_modules/which’,
npm ERR! dest: ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/which-a273e105’ },
npm ERR! stack: ‘Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/npm-2f4b5433/node_modules/which’ -> ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/which-a273e105’’,
npm ERR! errno: -13,
npm ERR! code: ‘EACCES’,
npm ERR! syscall: ‘rename’,
npm ERR! path: ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/npm-2f4b5433/node_modules/which’,
npm ERR! dest: ‘/home/gary0517/Documents/NRP/brainvisualizer/node_modules/.staging/which-a273e105’,
npm ERR! parent: ‘brainvisualizer’ }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/gary0517/.npm/_logs/2020-05-05T13_42_35_424Z-debug.log
brainvisualizer INSTALL ERROR


#4

Hi,

It seems like there is something wrong with the premissions in this folder, can you make sure that it is not owned by root but by your user? Also other users have reported similar problems, one such example is the discussion here. Unfortunately it does not seem NRP specific, so I would try searching for solutions related to this problem online. Hope it helps.

Edit: It looks like there is some generic problem with javascript packages on your machine, as this error on your previous message

/home/gary0517/Documents/NRP/user-scripts/nrp_functions: line 551: node_modules/ts-node/dist/bin.js: No such file or directory

shows that the npm install probably failed in $HBP/nrpBackendProxy too

Best,
Manos


#5

I followed the npm install at $HBP/nrpBackendProxy and returned similar problem.

The results showed as follow:
npm WARN deprecated request@2.83.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated iplocation@5.0.1: Version 6.x or earlier is no longer supported.
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated formatio@1.1.1: This package is unmaintained. Use @sinonjs/formatio instead
npm WARN deprecated samsam@1.1.2: This package has been deprecated in favour of @sinonjs/samsam
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated hawk@6.0.2: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated bson@0.2.22: Fixed a critical issue with BSON serialization documented in CVE-2019-2391, see https://bit.ly/2KcpXdo for more details
npm WARN deprecated samsam@1.1.3: This package has been deprecated in favour of @sinonjs/samsam
npm WARN deprecated request@2.69.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated cryptiles@3.1.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp@2.1.0: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated boom@4.3.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated boom@5.2.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN tar ENOENT: no such file or directory, open ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/grpc-1ff52859/ext/byte_buffer.h’
npm WARN tar ENOENT: no such file or directory, open ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/grpc-1ff52859/deps/grpc/third_party/boringssl/include/openssl/bytestring.h’
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

npm ERR! code EACCES
npm ERR! syscall rename
npm ERR! path /home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi
npm ERR! dest /home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’ -> ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’
npm ERR! { Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’ -> ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’
npm ERR! cause:
npm ERR! { Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’ -> ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’
npm ERR! errno: -13,
npm ERR! code: ‘EACCES’,
npm ERR! syscall: ‘rename’,
npm ERR! path: ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’,
npm ERR! dest: ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’ },
npm ERR! stack: ‘Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’ -> ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’’,
npm ERR! errno: -13,
npm ERR! code: ‘EACCES’,
npm ERR! syscall: ‘rename’,
npm ERR! path: ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’,
npm ERR! dest: ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’,
npm ERR! parent: ‘nrpBackendProxy’ }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/gary0517/.npm/_logs/2020-05-06T00_45_23_198Z-debug.log


#6

So I checked my permission of the following folder by ls -l
but it seems not the problem of permission…

gary0517@LAPTOP-17IRGJM0:~/Documents/NRP/nrpBackendProxy$ ls -l
total 112
-rw-r–r-- 1 gary0517 gary0517 18092 May 5 15:31 LICENSE
-rw-r–r-- 1 gary0517 gary0517 1226 May 5 15:31 README.md
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 activity_logs
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 admin
-rw-r–r-- 1 gary0517 gary0517 24803 May 5 15:31 app.ts
-rw-r–r-- 1 gary0517 gary0517 793 May 5 15:31 bitbucket-pipelines.yml
-rw-r–r-- 1 gary0517 gary0517 982 May 6 00:22 config.json
-rw-r–r-- 1 gary0517 gary0517 982 May 5 16:44 config.json.bak1
-rw-r–r-- 1 gary0517 gary0517 982 May 5 22:52 config.json.bak10
-rw-r–r-- 1 gary0517 gary0517 982 May 5 16:44 config.json.bak2
-rw-r–r-- 1 gary0517 gary0517 982 May 5 16:50 config.json.bak3
-rw-r–r-- 1 gary0517 gary0517 982 May 5 16:50 config.json.bak4
-rw-r–r-- 1 gary0517 gary0517 982 May 5 16:58 config.json.bak5
-rw-r–r-- 1 gary0517 gary0517 982 May 5 19:32 config.json.bak6
-rw-r–r-- 1 gary0517 gary0517 982 May 5 21:55 config.json.bak7
-rw-r–r-- 1 gary0517 gary0517 982 May 5 22:50 config.json.bak8
-rw-r–r-- 1 gary0517 gary0517 982 May 5 22:51 config.json.bak9
lrwxrwxrwx 1 gary0517 gary0517 95 May 6 00:21 config.json.sample.local -> /home/gary0517/Documents/NRP/user-scripts/config_files/nrpBackendProxy/config.json.sample.local
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 img
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 migration_scripts
drwxr-xr-x 1 gary0517 gary0517 512 May 6 09:45 node_modules
-rw-r–r-- 1 gary0517 gary0517 3887 May 5 15:31 package.json
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 piz_daint
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 proxy
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 storage
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 test
-rw-r–r-- 1 gary0517 gary0517 601 May 5 15:31 tsconfig.json
-rw-r–r-- 1 gary0517 gary0517 1160 May 5 15:31 tslint.json
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 utils
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 xmlns


#7

@ManosAngelidis
For my permission list into brainvisualizer , here the following:
gary0517@LAPTOP-17IRGJM0:~/Documents/NRP/brainvisualizer$ ls -l
total 44
-rw-r–r-- 1 gary0517 gary0517 5599 May 5 15:31 Gruntfile.js
-rw-r–r-- 1 gary0517 gary0517 18092 May 5 15:31 LICENSE
-rw-r–r-- 1 gary0517 gary0517 1226 May 5 15:31 README.md
-rw-r–r-- 1 gary0517 gary0517 2681 May 5 15:31 bitbucket-pipelines.yml
-rw-r–r-- 1 gary0517 gary0517 522 May 5 15:31 bower.json
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 img
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 lib
drwxr-xr-x 1 gary0517 gary0517 512 May 6 01:59 node_modules
-rw-r–r-- 1 gary0517 gary0517 78 May 5 19:08 package-lock.json
-rw-r–r-- 1 gary0517 gary0517 1049 May 6 01:58 package.json
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 script
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 shaders
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 src
drwxr-xr-x 1 gary0517 gary0517 512 May 5 15:31 test


#8

Hi,

Permissions look fine, I would try the following steps for all the Javascript builds that might fail,

rm -rf package-lock.json
rm -rf node_modules
npm install

One problem which I saw people had is that they tried running npm install through visual studio code, and this was causing the permissions. If you are trying that, it would be better to do it from a plain bash terminal. though I assume this is not the case. I hope it helps, else I will try to dig deeper into the problem.

Best,
Manos


#9

Also, your npm version is slighly above the one that we use ({“node”:“8.17.0”,“npm”:“6.13.4”}), it is a longshot, but it might help downgrading it to version 8.16.0. To do that you can just write

nvm install v8.16
nvm use 8.16
nvm uninstall v8.17

Best,
Manos


#10

Here’s what I got:

gary0517@LAPTOP-17IRGJM0:~/Documents/NRP/nrpBackendProxy$ rm -rf package-lock.json
gary0517@LAPTOP-17IRGJM0:~/Documents/NRP/nrpBackendProxy$ rm -rf node_modules
gary0517@LAPTOP-17IRGJM0:~/Documents/NRP/nrpBackendProxy$ npm install
npm WARN deprecated iplocation@5.0.1: Version 6.x or earlier is no longer supported.
npm WARN deprecated request@2.83.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated formatio@1.1.1: This package is unmaintained. Use @sinonjs/formatio instead
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated samsam@1.1.2: This package has been deprecated in favour of @sinonjs/samsam
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated bson@0.2.22: Fixed a critical issue with BSON serialization documented in CVE-2019-2391, see https://bit.ly/2KcpXdo for more details
npm WARN deprecated hawk@6.0.2: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated request@2.69.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated samsam@1.1.3: This package has been deprecated in favour of @sinonjs/samsam
npm WARN deprecated hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated boom@4.3.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated sntp@2.1.0: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated cryptiles@3.1.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated boom@5.2.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN tar ENOENT: no such file or directory, open ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/grpc-1ff52859/deps/grpc/third_party/abseil-cpp/absl/synchronization/blocking_counter.h’
npm WARN tar ENOENT: no such file or directory, open ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/grpc-1ff52859/deps/grpc/third_party/boringssl/include/openssl/blowfish.h’
npm WARN tar ENOENT: no such file or directory, open ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/grpc-1ff52859/deps/grpc/third_party/boringssl/include/openssl/bn.h’
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

npm ERR! path /home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall rename
npm ERR! Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’ -> ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’
npm ERR! { Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’ -> ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’
npm ERR! cause:
npm ERR! { Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’ -> ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’
npm ERR! errno: -13,
npm ERR! code: ‘EACCES’,
npm ERR! syscall: ‘rename’,
npm ERR! path: ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’,
npm ERR! dest: ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’ },
npm ERR! stack: ‘Error: EACCES: permission denied, rename ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’ -> ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’’,
npm ERR! errno: -13,
npm ERR! code: ‘EACCES’,
npm ERR! syscall: ‘rename’,
npm ERR! path: ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/nyc-1f732f11/node_modules/wrap-ansi’,
npm ERR! dest: ‘/home/gary0517/Documents/NRP/nrpBackendProxy/node_modules/.staging/wrap-ansi-3ea6d071’,
npm ERR! parent: ‘nrp_backend_proxy’ }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).

npm ERR! A complete log of this run can be found in:
npm ERR! /home/gary0517/.npm/_logs/2020-05-06T10_14_53_831Z-debug.log


#11

Hi,

I would try the downgrading. Also could you type

which npm
which node

and paste the results?


#12

maybe this could help https://stackoverflow.com/questions/48910876/error-eacces-permission-denied-access-usr-local-lib-node-modules-react


#13

I may have forgot to mention, I’m using WSL Ubuntu 18.04 LTS, Hope this helps.

gary0517@LAPTOP-17IRGJM0:~$ which npm
/home/gary0517/.nvm/versions/node/v8.16.2/bin/npm
gary0517@LAPTOP-17IRGJM0:~$ which node
/home/gary0517/.nvm/versions/node/v8.16.2/bin/node


#14

Hi,

I would try the downgrading, but I would suspect that the problem comes from the WSL. Unfortunately we do not support other approaches than plain Ubuntu, so I am afraid I cannot help further. If you figure out the problem please let us know and we will be happy to add it to our documentation for users that try in in the future.

Best,
Manos


#15

Okay, So I’ve tried installation in
Ubuntu 18.04 on a new external SSD and it worked smoothly,

so the problem can come from some internal problem on WSL Ubuntu.