Closed cgole closed 10 years ago
Note that node-syslog is an optional dependency, not expected to build on windows, the real issues start at about
npm ERR! fstream_path C:\Users\Administrator\AppData\Roaming\npm\node_modules\strong-supervisor\node_modules\strong-agen
t\src\extras.h
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack C:\Program Files\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (evalmachine.:107:15)
npm ERR! error rolling back Error: EPERM, unlink 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\strong-supervi
sor\node_modules\strong-cluster-control\node_modules\lodash\lodash.js'
npm ERR! error rolling back strong-supervisor@0.3.0 { [Error: EPERM, unlink 'C:\Users\Administrator\AppData\Roaming\npm
\node_modules\strong-supervisor\node_modules\strong-cluster-control\node_modules\lodash\lodash.js']
npm ERR! error rolling back errno: 50,
npm ERR! error rolling back code: 'EPERM',
npm ERR! error rolling back path: 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\strong-supervisor\n
Where npm starts spitting ENOENT and EPERM errors on trying to unlink the lodash deps, and header files that are definitely in the tar package archive for strong-agent.
It appears to me that race conditions are common on windows. This is a large package, with lots of deps, but the problem is very reproduceable.
npm has been playing a game of whack-a-mole with various locking and race condition issues; as of npm@2.0.0
and npm@1.4.28
, I believe that we've finally gotten on top of them. See #6043 for details on the resolution of this issue (which was specifically related to rolling back from failed installs of optionalDependencies
), as well as instructions on how to install the new versions and test the fix. Thanks for your patience, and sorry for taking a while to get this resolved!
I have having trouble installing the strongloop module on Windows Server 2008. I could reproduce the same error on Windows Server 2012.
Link to npm-debug.log - https://gist.github.com/cgole/621023b96909e4fab24c