unable to freebsd-update upgrade -r 10.2-RELEASE from 10.1 inside an virtualbox. cpu i386, ram 128MB screenshot attached
running it with debug, we can see that a Requested file is not available time /usr/libexec/phttpget update4.freebsd.org 10.2-RELEASE/amd64/f/f006a15124825bd5a5f80d510331a6e4969071de4e0201b5391a74e47d37612d.gz phttpget: Connection failure real 0m15.045s user 0m0.001s sys 0m0.002s time wget update4.freebsd.org/10.2-RELEASE/amd64/f/f006a15124825bd5a5f80d510331a6e4969071de4e0201b5391a74e47d37612d.gz ---- http://update4.freebsd.org/10.2-RELEASE/amd64/f/f006a15124825bd5a5f80d510331a6e4969071de4e0201b5391a74e47d37612d.gz Resolving update4.freebsd.org (update4.freebsd.org)... 209.193.13.98 Connecting to update4.freebsd.org (update4.freebsd.org)|209.193.13.98|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. ---- (try: 2) http://update4.freebsd.org/10.2-RELEASE/amd64/f/f006a15124825bd5a5f80d510331a6e4969071de4e0201b5391a74e47d37612d.gz Connecting to update4.freebsd.org (update4.freebsd.org)|209.193.13.98|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1964 (1.9K) [application/x-gzip] Saving to: 'f006a15124825bd5a5f80d510331a6e4969071de4e0201b5391a74e47d37612d.gz' f006a15124825bd5a5f80d510331a6e4969071de4e0201b5391a74e47d3 100%[==========================================================================================================================================>] 1.92K --.-KB/s in 0s (282 MB/s) - 'f006a15124825bd5a5f80d510331a6e4969071de4e0201b5391a74e47d37612d.gz' saved [1964/1964] real 1m16.618s user 0m0.000s sys 0m0.006s I think the bug is with phttpget which timeout is too small. But the web server is really slow to served this file time /usr/libexec/phttpget update4.freebsd.org 10.2-RELEASE/amd64/f/f008ab272d1062d557c56f66252936ef9c300b1ce24f3f5c5a9c8baff5d2d1e6.gz http://update4.freebsd.org/10.2-RELEASE/amd64/f/f008ab272d1062d557c56f66252936ef9c300b1ce24f3f5c5a9c8baff5d2d1e6.gz: 200 OK real 0m0.207s user 0m0.000s sys 0m0.004s
fixed for me this morning
Appears to have been a transient failure