-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
cargo install fails to update registry #4245
Comments
Is there perhaps an HTTP proxy configured? I believe libcurl reads a number of environment variables and that may cause curl/cargo to behave slightly different than the bare system itself. |
I don't think so. My laptop is directly connected to the wireless router provided by my ISP. I'm not aware of changing any network settings recently. |
If you run |
I don't see any environment variables that seem related to networking except one related to SSH. Anything in particular I should look out for? I don't have a file named |
Is this something like an ipv4/ipv6 problem maybe? Or maybe |
Funny that you should mention How would I debug an ipv4/ipv6 problem? |
Sorry I basically have no idea what's going on here, I'm just throwing out ideas. All your guesses are basically as good as mine at this point. I don't know how to debug this problem, just wondering if anything rings a bell with you. |
Thanks for your help anyway.. However the problem became even stranger (TL;DR: it's now working again!): I tried adding
If I remove the entry in That led me to think that maybe something got corrupt in cargo's application data and I renamed the
So it seems like my cargo works again like it used to.. I'm not sure what went wrong. Do you need more information from me to investigate further or should we close this issue? |
That does indeed sound odd! "Too man open files" seems suspicious but I'm not sure how we'd fix it. If it's working now though that's great! In that case yeah let's close |
As a follow up, I had the same thing happen the other week. I was running MacOS High Sierra Beta, not sure if that makes a difference. I removed the registry and |
Just had this happen to me on mac os Sierra. wiping out the ~/.cargo/registry directory fixed it. |
Same issue on 10.12.6, removing ~/.cargo/registry didn't work but a system reboot did. |
It seems like the issue still persist. The last thing that I did before
Edit: |
About a week ago,
cargo install
has stopped working on my computer (macOS 10.12.5) with the following error:(Note: there's nothing spurious about this error; it has stopped working 100% of the time.)
This happens with both the current stable and nightly versions of cargo.
Pinging github.com works fine, so I don't think it's a DNS issue:
I didn't notice any other network related issue on this computer.
Any ideas what the problem is?
The text was updated successfully, but these errors were encountered: