Skip to content
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.

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

Thread pool panic "Resource temporarily unavailable" #4134

Open
2 tasks done
liniea opened this issue Dec 30, 2024 · 2 comments
Open
2 tasks done

Thread pool panic "Resource temporarily unavailable" #4134

liniea opened this issue Dec 30, 2024 · 2 comments
Labels

Comments

@liniea
Copy link

liniea commented Dec 30, 2024

Verification

Problem

When running the installer on https://rustup.rs/, and entering 1 for default options, rustup panics while downloading stuff.

thread 'main' panicked at /cargo/registry/src/index.crates.io-6f17d22bba15001f/threadpool-1.8.1/src/lib.rs:777:10:
called `Result::unwrap()` on an `Err` value: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }

Steps

  1. Run curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
  2. Choose 1) Proceed with standard installation (default - just press enter)
  3. Rustup panics roughly when it starts downloading cargo. rustup-backtrace.txt

Possible Solution(s)

No response

Notes

No response

Rustup version

[ Rustup does not succesfully install. ]

Installed toolchains

[ Rustup does not succesfully install. ]

OS version

Debian 10 (buster), x86_64
@liniea liniea added the bug label Dec 30, 2024
@djc
Copy link
Contributor

djc commented Jan 6, 2025

Can you try this with RUSTUP_IO_THREADS=1? It appears to fail when spawning a new thread. What kind of environment are you running in, is it particularly constrained?

@liniea
Copy link
Author

liniea commented Jan 7, 2025

RUSTUP_IO_THREADS=1 worked!
The environment is a multi-user server with a lot going on at once, but I wouldn't describe it as particularly constrained.

If it's feasable you might want to handle the errors, but I'm happy there's a solution on the web now at least.

Thank you either way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants