Node-sass: EPROTO/ETXTBUSY errors while installing

Created on 17 Aug 2016  路  3Comments  路  Source: sass/node-sass

Cannot install node-sass using npm install from package.json.

node v - 5.0.0
npm -v 3.3.6
node-sass 3.8.0

I can get around this by doing npm install node-sass --no-bin-links seperately but this doesn't fix the issue.

npm WARN install Couldn't install optional dependency: Unsupported
npm WARN install Couldn't install optional dependency: Unsupported
npm ERR! Linux 3.19.0-25-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "node-sass" "--save-dev"
npm ERR! node v5.0.0
npm ERR! npm  v3.3.6
npm ERR! path ../node-sass/bin/node-sass
npm ERR! code EPROTO
npm ERR! errno -71
npm ERR! syscall symlink

npm ERR! EPROTO: protocol error, symlink '../node-sass/bin/node-sass' -> '/home/vagrant/sales-demo/node_modules/.bin/node-sass'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
npm ERR! Linux 3.19.0-25-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "node-sass" "--save-dev"
npm ERR! node v5.0.0
npm ERR! npm  v3.3.6
npm ERR! path npm-debug.log.123c82f40b54eaaea2dd58792e6472d6
npm ERR! code ETXTBSY
npm ERR! errno -26
npm ERR! syscall rename

npm ERR! ETXTBSY: text file is busy, rename 'npm-debug.log.123c82f40b54eaaea2dd58792e6472d6' -> 'npm-debug.log'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /home/vagrant/sales-demo/npm-debug.log
External - NPM npm install

Most helpful comment

See https://github.com/npm/npm/issues/9901, one advice is to update VirtualBox or to run vagrant up as the system administrator if on Windows in order to create symbolic links (symlinks).

All 3 comments

What platform is this? What are the filesystems you build on (NFS, SMB, ZFS, ext3, etc.)? Are you trying to build on some kind of shared drive between host and virtual (Vagrant) environment?

See https://github.com/npm/npm/issues/9901, one advice is to update VirtualBox or to run vagrant up as the system administrator if on Windows in order to create symbolic links (symlinks).

Running Wndows CLI as administrator and doing npm install without --no bin-links works thanks

Was this page helpful?
0 / 5 - 0 ratings