-
-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
warning: unable to download: HTTP error 200 (curl error: Timeout was reached); #65015
Comments
I can not reproduce it from Germany/Europe. Maybe a temporary problem of the CDN.
|
Europe/Germany Running "nixos-rebuild switch" gives me the same error. I was able to reproduce this the last few days. At the moment the cache seems to be rather slow, sometimes it manages to use my full bandwidth but often it drops to ~500KB/s |
I've got lots of errors from Japan. Had to rerun ~7 times my nix-shell before it was able to fetch everything. On discourse, someone says to use -j1 : |
I have had this for a while in France. This seemed to be linked to a problem in my not fully ipv6 capable router. The simplest workaround I had was to only rely on ipv4 when needed. Something like $ sudo ip -6 route delete default makes sure that you do not use IPv6 (non permanent), which is quite sad I have to admit. |
I have had this problem for quite a while too (France) |
I'm also having this issue with one of my computers, starting a bit over a month ago. I have two computers running NixOS at the same location (and sharing the same slow connection), one on channel The Further, the The issue doesn't happen if I download the failed files directly (e.g. From observations, it appears that:
As @duhirsch noted, the next Nix release will support resumable NAR downloads (which is excellent 👍) in response to Nix#2952 (in which the same timeout messages can be seen). However, I feel that still leaves the question of why these specific timeouts happen to begin with. Hope this helps 😃. (p.s. I'm in Australia, as are the computers involved.) (p.p.s. I did try disabling IPv6 as an alternative – |
@aexoxea thanks for the detailed report. Could you please post the relevant part of your configuration on howto use nix from stable? |
Hi @feijoas, You're welcome. The relevant part of my config is:
This is based on an approach documented in NixOS Wiki: NB 1: This first requires that the NB 2: While this is working for me, I lack the knowledge to say whether this might cause other issues down the line, since I don't know to what extent Nix can be considered "like just another package" on a NixOS system. |
@lsix's solution, which is disabling ipv6 works for me. Nevertheless I consider this to be only a temporary fix, the real problem has to be somewhere else. |
I think the older thread did seem to indicate that IPv6 makes Fastly's issues more likely (or worse). Killing all IPv6 seems an overkill... it's just a single name, so it should be perfectly enough e.g. to override one DNS record
EDIT: just for you, as people without these problems probably want to keep IPv6. |
Both approaches, disabling IPv6 and using nix from stable channel, do not work. |
I close this issue since it seems to be a nix error: NixOS/nix#3025 |
If you are still having issues, there is a new experimental cache with some improvements: https://discourse.nixos.org/t/improvements-to-cache-nixos-org-help-test-the-new-config/3620 |
I have seen an error just like this; if I ran (I might have this backwards...) a "nix-shell" that was downloading larger NAR.xz items (copying ... into /nix/store/....) it'd show that xz exited with error 10; if I installed something with "nix-env -i" I got a HTTP error 200 (curl error: Timeout was reached). Long story short, in ~/.config/nix/nix.conf I put "stalled-download-timeout = 99999999" (just an arbitrarily large number). I guess you can put this into /etc/nix/nix.conf if you prefer. PROBLEM FIXED!!! Looks like default is 300, and it does sound fine to have a download abort if it's stalled for 5 minutes. But for whatever reason it's not... Anyway... I found the code and in essence curl "-Y" (--speed-limit) is set to "1" (byte per second), "-y" (--speed-time) is set to 300 (or whatever stalled-download-timeout is set to). Sounds fair enough. BUT, "nar.xz" are not downloaded then installed, they are downloaded into some kind of pipe, which (when it's extracting a bunch of tiny files) DOES cause the download to stall for a while. I don't think it's stalling for 5 minutes... but whatever, disabling this timeout fixes it. Cheers! |
Might help with issues described in: status-im/infra-ci#17. Details: NixOS/nixpkgs#65015 (comment) Signed-off-by: Jakub Sokołowski <jakub@status.im>
Might help with issues described in: status-im/infra-ci#17. Details: NixOS/nixpkgs#65015 (comment) Signed-off-by: Jakub Sokołowski <jakub@status.im>
This issue has been mentioned on NixOS Discourse. There might be relevant details there: |
Issue description
Since a few days I am getting a curl timeout when installing the dependencies mono and a few others:
I tried switching the cache from 151.101.194.217 to 151.101.66.217, but without any effect.
Steps to reproduce
nix-shell -p mono
Technical details
Here the output of the cloudfront.sh script from https://cache.nixos.org:
http://ix.io/1OOI
The text was updated successfully, but these errors were encountered: