This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
npm EEXIST error 47 #6309
Comments
|
This is another case of #6238 and #6248. Everybody encountering it is running large, complicated builds of one kind or another, which leads me to believe that it's yet another undiagnosed race condition. My current attempt to address it is #6294, which I'd hoped to get out to |
|
Thanks for the quick reply! I'll keep an eye out for updates. -Ryan Grigsby |
|
Seeing the same problem here myself on npm 2.0.2: |
|
Rolling back to |
|
There are many, many other problems with 1.3.x, including the fact that they are not safe to publish with, and in many cases not capable of publishing. I'm close to finishing a fix for this that makes some substantial changes to the locking code that should address this issue. Everybody hold tight. |
|
I believe that f24b552, which is included in |
|
I have same problem: Now (After git clone npm, and using "node link", because 2.1.0 is not published still) |
|
Thanks for testing this for me; that narrows the problem down to
It's published, it's just not dist-tagged |
|
Still seeing the same problem unfortunately.
|
|
Thanks, @F21. You're the second person to confirm that this isn't fixed yet. See #6318 for what I now believe needs to be done. The good news is that doing this trades a tiny amount of extra work being done (because multiple processes can be putting the same tarball in the cache at the same time) for a lot less locking within npm, which should make it both more robust and (in some cases) slightly faster. |
|
@othiym23 Thought I would post more info on my setup (maybe it can help you reproduce the issue). OS: {
"name": "mypackage",
"version": "0.0.1",
"devDependencies": {
"gulp" : "~3.8.8",
"gulp-sass" : "~1.0.0",
"gulp-autoprefixer" : "~1.0.1",
"gulp-load-plugins" : "~0.6.0",
"gulp-imagemin" : "~1.0.1",
"gulp.spritesmith" : "~1.3.0",
"gulp-webpack" : "~0.3.0",
"gulp-cache" : "~0.2.2",
"gulp-notify" : "~1.8.0",
"gulp-tap" : "~0.1.1",
"gulp-watch": "~1.0.7",
"gulp-plumber" : "0.6.5",
"del" : "~0.1.3"
}
} |
|
I'm also encountering the same problem on npm@2.0.2 and after updating to npm@2.1.0. Removing 'gulp-imagemin' from my package.json allowed all other packages to install without error. Trying to install just 'gulp-imagemin' succeeds with WARNs for optional dependencies (basically renders it useless) Erroring package.json: {
"name": "mypackage",
"version": "0.0.1",
"devDependencies": {
"bower": "~1.3.11",
"gulp": "~3.8.8",
"gulp-autoprefixer": "~1.0.1",
"gulp-compass": "~1.3.1",
"gulp-concat": "~2.4.1",
"gulp-imagemin": "~1.0.1",
"gulp-jshint": "~1.8.4",
"gulp-livereload": "~2.1.1",
"gulp-load-plugins": "~0.6.0",
"gulp-minify-css": "~0.3.10",
"gulp-plumber": "~0.6.5",
"gulp-rename": "~1.2.0",
"gulp-ruby-sass": "~0.7.1",
"gulp-size": "~1.1.0",
"gulp-sym": "~0.0.14",
"gulp-uglify": "~1.0.1",
"gulp-util": "~3.0.1",
"tiny-lr": "~0.1.4"
}
}Environment: |
|
Interestingly, changing the way that chef installs produces different results. Using grunt_cookbook or the I've run the install using The system I'm using is an AWS EC2 64-bit Ubuntu 14.04 ami. |
|
Good news! See #6318 for details, but I now believe (with more confidence this time than last) that this issue has been addressed for real. |
|
@othiym23 I can confirm that everything works perfectly with |
|
@othiym23 All lights are green here too with |
This was referenced Oct 21, 2014
|
Just perfect with 2.1.1 |
|
I had this problem, seemingly out of the blue today and found my way here. I tried to install with the recommended Just now I tried installing from my MORE OF SAME... |
Closed
|
Was only having this problem on Windows and spent a good while trying to track down what the issue was. This fixed it, I installed the latest npm release as of now which was 2.6.0 and retried "npm install". It worked |
|
For the record, the bin conflict part of this issue is still happening with recent versions like npm v2.4.1. Refer to #7130 (comment) for that. |
|
|
|
npm -g install npm@2.1.1 doesn't install any new version. How can I really install this? |
|
@papazov3d Are you asking how to upgrade to the latest stable release? We have a guide if so. |
|
Just wanted to install 2.1.1 because of other issues. Did it according to option 3 in the guide. Thanks. |
manthey
added a commit
to girder/girder
that referenced
this issue
May 7, 2015
Occasionally npm install would fail with an EEXIST error message. This was caused by a race condition in npm (see npm/npm#6309). Upgrading to the latest npm version avoids this problem. I've occasionally seen this failure in a travis build, but it is fairly rare.
CloudNiner
added a commit
to WorldBank-Transport/DRIVER
that referenced
this issue
May 7, 2015
evolchek
pushed a commit
to evolchek/docker-teamcity-agent-klika
that referenced
this issue
Jul 17, 2015
davidemoro
pushed a commit
to substancek/substancek_cms_theme
that referenced
this issue
Aug 14, 2015
|
I am still having this issue on shippable build. I tried with nodejs 0.11 and 4.1.1 too make: Leaving directory `/root/workspace/src/github.com/Cloudkibo/CloudKibo/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/build' npm ERR! System Linux 3.13.0-57-generic |
|
npm ERR! Linux 2.6.32-573.12.1.el6.x86_64 |
|
node: 5.4.1 "dependencies": {
"express": "4.13.3",
"serve-favicon": "2.3.0",
"morgan": "1.6.1",
"body-parser": "1.13.3",
"express-session": "1.11.3",
"method-override": "2.3.5",
"cookie-parser": "1.3.5",
"errorhandler": "1.4.2",
"ejs": "0.8.4",
"moment": "2.3.1",
"underscore": "1.5.2",
"qs": "0.6.5",
"nodemailer": "0.5.5",
"i18n": "0.4.1",
"async": "0.9.0",
"csso": "1.3.11",
"uglify-js": "2.4.24",
"node-vger": "git+ssh://git@bitbucket.org/jombay/node-vger.git#26a3c378c6478ee6f97b83a5deddd31076fbc521",
"connect-assets": "5.0.1"
}Error |
can't update npm to 5.5trying to update |
|
# trying to update the same problem C:\WINDOWS\system32>npm -g install npm@next npm ERR! A complete log of this run can be found in: |
|
Resolved, I have deleted the folder C:\Users\aog\AppData\Roaming\npm and then the executed npm -g and npm@5.5.1 and it has been installed correctly. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
and others
Attempting to run
npm installduring an automated chef deployment is causing a consistent error during deployment, while running the same command interactively in the shell succeeds about 90% of the time, but I have seen the failure interactively. Have attempted the install using both versions 1.4.8 and 2.0.0.The text was updated successfully, but these errors were encountered: