Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[rush] pnpm: EBUSY: resource busy or locked when running rush install #5164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ChathuraIshara opened this issue Mar 12, 2025 · 2 comments
Open

[rush] pnpm: EBUSY: resource busy or locked when running rush install #5164

ChathuraIshara opened this issue Mar 12, 2025 · 2 comments

Comments

@ChathuraIshara
Copy link

Summary

I encountered an issue when running rush install on Windows. The installation fails with the following error message:

pnpm: EBUSY: resource busy or locked

Repro steps

  1. Navigate to the root of the Rush monorepo.
  2. Run the command: 
    rush install

Expected result: Dependencies should be installed successfully without encountering a resource lock error.

Actual result: The installation fails with an EBUSY error, indicating that some files or directories are locked by another process.

Details

This issue occurs repeatedly even after clearing npm and pnpm caches.
Restarting the terminal and system didn’t resolve the issue.
Additionally, I have:

  • Cleared temporary files on my PC.
  • Run the command in Administrator mode.

Standard questions

Question Answer
@microsoft/rush globally installed version? 5.109.2
rushVersion from rush.json? 5.109.2
useWorkspaces from rush.json? false
Operating system? Windows
Would you consider contributing a PR? No
Node.js version (node -v)? 18.20.4
@github-project-automation github-project-automation bot moved this to Needs triage in Bug Triage Mar 12, 2025
@iclanton
Copy link
Member

iclanton commented Mar 24, 2025 •
edited
Loading

Can you share a log? Is this Rush or PNPM throwing the error?

Is Windows Defender or another virus scanner locking a subfolder of the store or the common/temp/node_modules folder?

@iclanton iclanton moved this from Needs triage to Waiting for Author in Bug Triage Mar 24, 2025
@ChathuraIshara
Copy link
Author

@iclanton Here is the log.

BUSY  EBUSY: resource busy or locked, copyfile '\common\temp\pnpm-store\v3\files\1d\03aff5233ccd84f83a5d142d58a0576c748f868a946d2f5a8c29371c26d86114dfb7a46b6d603fa30cea6d692e2fc88df083d404804baa1a679efe3cad7214' -> '\common\temp\node_modules.pnpm@swagger-api+apidom-parser-adapter-api-design-systems-json@1.0.0-alpha.5\node_modules@swagger-api_tmp_17636_bfca96d92508175e95ea25b9f6698c40\cjs\adapter.cjs'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Bug Triage
Status: Waiting for Author
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iclanton @ChathuraIshara