NPM: EBUSY: resource busy or locked: “update-notifier-npm.json”
I've got an issue with NPM. It seems to be having an issue updating, which I don't care about. However, when I run an NPM command I'm getting:
npm ERR! path D:Users[user].configconfigstoreupdate-notifier-npm.json
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall open
npm ERR! EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
If I run the command 3 or 4 times, it eventually works. However, some of my scripts have 3-4 steps, each one having a 30% chance of succeeding becomes intolerably frustrating. I have to run it over and over again to get a 'clean' run where none of them fail.
Might be related to this message:
┌────────────────────────────────────────────────────────────────┐
│ npm update check failed │
│ Try running with sudo or get access │
│ to the local update config store via │
│ sudo chown -R $USER:$(id -gn $USER) D:Users[user].config │
└────────────────────────────────────────────────────────────────┘
I don't care that it can't update, Is there any way to stop it constantly creating and deleting this file so it can get on with things?
Current user has permission to modify the file/folder (it does, sometimes).
Even get the error doing npm -v
:
D:Projectssocos-process>npm -V
npm ERR! path D:Users[user].configconfigstoreupdate-notifier-npm.json
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall open
npm ERR! EBUSY: resource busy or locked, open 'D:Users[user].configconfi
gstoreupdate-notifier-npm.json'
npm ERR! A complete log of this run can be found in:
npm ERR! D:Users[user]AppDataRoamingnpm-cache_logs2018-11-19T15_1
7_19_049Z-debug.log
That log file shows:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'prefix',
1 verbose cli '-g' ]
2 info using npm@6.4.1
3 info using node@v10.13.0
4 verbose stack Error: EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
4 verbose stack at Object.openSync (fs.js:436:3)
4 verbose stack at Object.readFileSync (fs.js:341:35)
4 verbose stack at Configstore.get all [as all] (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesconfigstoreindex.js:30:25)
4 verbose stack at Configstore.get (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesconfigstoreindex.js:74:27)
4 verbose stack at UpdateNotifier.check (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesupdate-notifierindex.js:78:16)
4 verbose stack at module.exports.options (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesupdate-notifierindex.js:151:17)
4 verbose stack at EventEmitter.<anonymous> (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmbinnpm-cli.js:85:48)
4 verbose stack at process._tickCallback (internal/process/next_tick.js:61:11)
5 verbose cwd D:Projectssocos-process
6 verbose Windows_NT 6.1.7601
7 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "prefix" "-g"
8 verbose node v10.13.0
9 verbose npm v6.4.1
10 error path D:Users[user].configconfigstoreupdate-notifier-npm.json
11 error code EBUSY
12 error errno -4082
13 error syscall open
14 error EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
15 verbose exit [ -4082, true ]
I've tried uinstalling and reinstalling.
Edit: Now having this problem on 3 different machines. Maybe caused by anti-virus, but I can't turn that off.
npm
add a comment |
I've got an issue with NPM. It seems to be having an issue updating, which I don't care about. However, when I run an NPM command I'm getting:
npm ERR! path D:Users[user].configconfigstoreupdate-notifier-npm.json
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall open
npm ERR! EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
If I run the command 3 or 4 times, it eventually works. However, some of my scripts have 3-4 steps, each one having a 30% chance of succeeding becomes intolerably frustrating. I have to run it over and over again to get a 'clean' run where none of them fail.
Might be related to this message:
┌────────────────────────────────────────────────────────────────┐
│ npm update check failed │
│ Try running with sudo or get access │
│ to the local update config store via │
│ sudo chown -R $USER:$(id -gn $USER) D:Users[user].config │
└────────────────────────────────────────────────────────────────┘
I don't care that it can't update, Is there any way to stop it constantly creating and deleting this file so it can get on with things?
Current user has permission to modify the file/folder (it does, sometimes).
Even get the error doing npm -v
:
D:Projectssocos-process>npm -V
npm ERR! path D:Users[user].configconfigstoreupdate-notifier-npm.json
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall open
npm ERR! EBUSY: resource busy or locked, open 'D:Users[user].configconfi
gstoreupdate-notifier-npm.json'
npm ERR! A complete log of this run can be found in:
npm ERR! D:Users[user]AppDataRoamingnpm-cache_logs2018-11-19T15_1
7_19_049Z-debug.log
That log file shows:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'prefix',
1 verbose cli '-g' ]
2 info using npm@6.4.1
3 info using node@v10.13.0
4 verbose stack Error: EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
4 verbose stack at Object.openSync (fs.js:436:3)
4 verbose stack at Object.readFileSync (fs.js:341:35)
4 verbose stack at Configstore.get all [as all] (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesconfigstoreindex.js:30:25)
4 verbose stack at Configstore.get (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesconfigstoreindex.js:74:27)
4 verbose stack at UpdateNotifier.check (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesupdate-notifierindex.js:78:16)
4 verbose stack at module.exports.options (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesupdate-notifierindex.js:151:17)
4 verbose stack at EventEmitter.<anonymous> (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmbinnpm-cli.js:85:48)
4 verbose stack at process._tickCallback (internal/process/next_tick.js:61:11)
5 verbose cwd D:Projectssocos-process
6 verbose Windows_NT 6.1.7601
7 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "prefix" "-g"
8 verbose node v10.13.0
9 verbose npm v6.4.1
10 error path D:Users[user].configconfigstoreupdate-notifier-npm.json
11 error code EBUSY
12 error errno -4082
13 error syscall open
14 error EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
15 verbose exit [ -4082, true ]
I've tried uinstalling and reinstalling.
Edit: Now having this problem on 3 different machines. Maybe caused by anti-virus, but I can't turn that off.
npm
add a comment |
I've got an issue with NPM. It seems to be having an issue updating, which I don't care about. However, when I run an NPM command I'm getting:
npm ERR! path D:Users[user].configconfigstoreupdate-notifier-npm.json
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall open
npm ERR! EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
If I run the command 3 or 4 times, it eventually works. However, some of my scripts have 3-4 steps, each one having a 30% chance of succeeding becomes intolerably frustrating. I have to run it over and over again to get a 'clean' run where none of them fail.
Might be related to this message:
┌────────────────────────────────────────────────────────────────┐
│ npm update check failed │
│ Try running with sudo or get access │
│ to the local update config store via │
│ sudo chown -R $USER:$(id -gn $USER) D:Users[user].config │
└────────────────────────────────────────────────────────────────┘
I don't care that it can't update, Is there any way to stop it constantly creating and deleting this file so it can get on with things?
Current user has permission to modify the file/folder (it does, sometimes).
Even get the error doing npm -v
:
D:Projectssocos-process>npm -V
npm ERR! path D:Users[user].configconfigstoreupdate-notifier-npm.json
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall open
npm ERR! EBUSY: resource busy or locked, open 'D:Users[user].configconfi
gstoreupdate-notifier-npm.json'
npm ERR! A complete log of this run can be found in:
npm ERR! D:Users[user]AppDataRoamingnpm-cache_logs2018-11-19T15_1
7_19_049Z-debug.log
That log file shows:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'prefix',
1 verbose cli '-g' ]
2 info using npm@6.4.1
3 info using node@v10.13.0
4 verbose stack Error: EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
4 verbose stack at Object.openSync (fs.js:436:3)
4 verbose stack at Object.readFileSync (fs.js:341:35)
4 verbose stack at Configstore.get all [as all] (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesconfigstoreindex.js:30:25)
4 verbose stack at Configstore.get (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesconfigstoreindex.js:74:27)
4 verbose stack at UpdateNotifier.check (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesupdate-notifierindex.js:78:16)
4 verbose stack at module.exports.options (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesupdate-notifierindex.js:151:17)
4 verbose stack at EventEmitter.<anonymous> (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmbinnpm-cli.js:85:48)
4 verbose stack at process._tickCallback (internal/process/next_tick.js:61:11)
5 verbose cwd D:Projectssocos-process
6 verbose Windows_NT 6.1.7601
7 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "prefix" "-g"
8 verbose node v10.13.0
9 verbose npm v6.4.1
10 error path D:Users[user].configconfigstoreupdate-notifier-npm.json
11 error code EBUSY
12 error errno -4082
13 error syscall open
14 error EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
15 verbose exit [ -4082, true ]
I've tried uinstalling and reinstalling.
Edit: Now having this problem on 3 different machines. Maybe caused by anti-virus, but I can't turn that off.
npm
I've got an issue with NPM. It seems to be having an issue updating, which I don't care about. However, when I run an NPM command I'm getting:
npm ERR! path D:Users[user].configconfigstoreupdate-notifier-npm.json
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall open
npm ERR! EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
If I run the command 3 or 4 times, it eventually works. However, some of my scripts have 3-4 steps, each one having a 30% chance of succeeding becomes intolerably frustrating. I have to run it over and over again to get a 'clean' run where none of them fail.
Might be related to this message:
┌────────────────────────────────────────────────────────────────┐
│ npm update check failed │
│ Try running with sudo or get access │
│ to the local update config store via │
│ sudo chown -R $USER:$(id -gn $USER) D:Users[user].config │
└────────────────────────────────────────────────────────────────┘
I don't care that it can't update, Is there any way to stop it constantly creating and deleting this file so it can get on with things?
Current user has permission to modify the file/folder (it does, sometimes).
Even get the error doing npm -v
:
D:Projectssocos-process>npm -V
npm ERR! path D:Users[user].configconfigstoreupdate-notifier-npm.json
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall open
npm ERR! EBUSY: resource busy or locked, open 'D:Users[user].configconfi
gstoreupdate-notifier-npm.json'
npm ERR! A complete log of this run can be found in:
npm ERR! D:Users[user]AppDataRoamingnpm-cache_logs2018-11-19T15_1
7_19_049Z-debug.log
That log file shows:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'prefix',
1 verbose cli '-g' ]
2 info using npm@6.4.1
3 info using node@v10.13.0
4 verbose stack Error: EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
4 verbose stack at Object.openSync (fs.js:436:3)
4 verbose stack at Object.readFileSync (fs.js:341:35)
4 verbose stack at Configstore.get all [as all] (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesconfigstoreindex.js:30:25)
4 verbose stack at Configstore.get (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesconfigstoreindex.js:74:27)
4 verbose stack at UpdateNotifier.check (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesupdate-notifierindex.js:78:16)
4 verbose stack at module.exports.options (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmnode_modulesupdate-notifierindex.js:151:17)
4 verbose stack at EventEmitter.<anonymous> (D:Users[user]AppDataRoamingnvmv10.13.0node_modulesnpmbinnpm-cli.js:85:48)
4 verbose stack at process._tickCallback (internal/process/next_tick.js:61:11)
5 verbose cwd D:Projectssocos-process
6 verbose Windows_NT 6.1.7601
7 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "prefix" "-g"
8 verbose node v10.13.0
9 verbose npm v6.4.1
10 error path D:Users[user].configconfigstoreupdate-notifier-npm.json
11 error code EBUSY
12 error errno -4082
13 error syscall open
14 error EBUSY: resource busy or locked, open 'D:Users[user].configconfigstoreupdate-notifier-npm.json'
15 verbose exit [ -4082, true ]
I've tried uinstalling and reinstalling.
Edit: Now having this problem on 3 different machines. Maybe caused by anti-virus, but I can't turn that off.
npm
npm
edited Dec 10 '18 at 12:31
Joe
asked Nov 19 '18 at 14:46
JoeJoe
3,6122047
3,6122047
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53377061%2fnpm-ebusy-resource-busy-or-locked-update-notifier-npm-json%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53377061%2fnpm-ebusy-resource-busy-or-locked-update-notifier-npm-json%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown