Gary Sieling

Fix to error installing “forever” for nodejs

After doing “npm install forever” in a VirtualBox instance you may get an error like the following. This is caused by running the install from a folder shared with the host machine. Certain file operations fail when crossing the machine/file system boundary in VirtualBox.

npm ERR! error rolling back forever@0.8.5 Error: UNKNOWN, unlink '/vagrant/node_modules/forever/node_modules/winston/docs/winston/transports.html'

npm ERR! Error: UNKNOWN, symlink '../ncp/bin/ncp'
npm ERR! You may report this log at:
npm ERR! <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR! <npm-@googlegroups.com>
npm ERR!
npm ERR! System Linux 2.6.32-33-generic
npm ERR! command "node" "/usr/local/bin/npm" "install" "forever"
npm ERR! cwd /vagrant
npm ERR! node -v v0.6.13
npm ERR! npm -v 1.1.9
npm ERR! path ../ncp/bin/ncp
npm ERR! code UNKNOWN
npm ERR! message UNKNOWN, symlink '../ncp/bin/ncp'
npm ERR! errno {}
npm http GET https://registry.npmjs.org/wordwrap
npm http GET https://registry.npmjs.org/colors
npm http GET https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/wordwrap
npm http 304 https://registry.npmjs.org/colors
npm http 304 https://registry.npmjs.org/async
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /vagrant/npm-debug.log
npm not ok
Exit mobile version