You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
Problem occurred when 2 builds of the exact same code branch running. I have the first build started in Austin then 4 minutes later I started the same build in different geographic location. The second build succeeded but the first one failed with "Unknown system error -116" during npm install. With no fix at all, I restarted the first build and it completed successfully.
We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining package.community and asking your question there.
For more information about our new issue aging policies and why we've instituted them please see our blog post.
I'm opening this issue because:
What's going wrong?
npm install exited with Unknown system error -116
How can the CLI team reproduce the problem?
Problem occurred when 2 builds of the exact same code branch running. I have the first build started in Austin then 4 minutes later I started the same build in different geographic location. The second build succeeded but the first one failed with "Unknown system error -116" during npm install. With no fix at all, I restarted the first build and it completed successfully.
supporting information:
npm -v
prints:node -v
prints:npm config get registry
prints:bash-4.1$ npm -v
3.9.3
bash-4.1$ node -v
v6.2.1
bash-4.1$ npm config get registry
http://xxxxxx-rh66-nexus:8081/nexus/content/repositories/serverjnpmproxy/
Windows, OS X/macOS, or Linux?: Linux
Network issues:
npm-debug.log.zip
] I use a proxy to connect to the npm registry.
The text was updated successfully, but these errors were encountered: