Bug 218503
| Summary: | fetching public key from update.freebsd.org no mirrors remaining giving up | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Services | Reporter: | Tony Hain <tony> | ||||
| Component: | FreeBSD Update | Assignee: | Rebecca Cran <bcran> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Many People | CC: | anandsuresh, bcran, gordon, h.t.medway, secteam, sven.siemsen, thierry, yklaxds | ||||
| Priority: | --- | ||||||
| Version: | unspecified | ||||||
| Hardware: | amd64 | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
I know this is an old issue, but you can get more information from freebsd-update by running it with "-v debug". That should let you know what it's trying and failing to fetch. MARKED AS SPAM I met it today on my RPI3B+. root@generic:/home/freebsd # freebsd-update fetch src component not installed, skipped Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update2.freebsd.org... failed. Fetching public key from update4.freebsd.org... failed. Fetching public key from update1.freebsd.org... failed. No mirrors remaining, giving up. root@generic:/home/freebsd # uname -r 12.0-RELEASE root@generic:/home/freebsd # (In reply to Rebecca Cran from comment #1) root@generic:/home/freebsd # freebsd-update fetch -v debug src component not installed, skipped Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update1.freebsd.org... fetch: http://update1.freebsd.org/12.0-RELEASE/arm64/pub.ssl: Not Found failed. Fetching public key from update4.freebsd.org... fetch: http://update4.freebsd.org/12.0-RELEASE/arm64/pub.ssl: Not Found failed. Fetching public key from update2.freebsd.org... fetch: http://update2.freebsd.org/12.0-RELEASE/arm64/pub.ssl: Not Found failed. No mirrors remaining, giving up. root@generic:/home/freebsd # Experiencing the same issue with FreeBSD 12.0-RELEASE on a Raspberry Pi 3. Tried `curl http://update1.freebsd.org/12.0-RELEASE/arm64/pub.ssl` and got a 404. MARKED AS SPAM (In reply to zindara from comment #6) What's this ？Seems like ADs. Created attachment 203126 [details]
Error
freebsd-update is not maintainer by clusteradm, but is maintained by secteam I believe. MARKED AS SPAM (In reply to ykla from comment #8) arm64 is not a tier 1 platform and does not have freebsd-update support. (In reply to ykla from comment #3) As others have said, there's no support for arm64 with freebsd-update. On the raspBSD website, it refers to a work-around using old (v11) packages for pkg, but freebsd-update is unsupported. https://www.raspbsd.org/raspberrypi.html I can't remember why I assigned this to myself, but since the follow-up comments were about arm64 and not amd64, I'm closing this. |
This has been a pathetic waste of a day ... Could not install FreeBSD-11.0-RELEASE-amd64-bootonly.iso due to 6 month old unresolved Hyper-V bug. Could not install (known to work on Hyper-V) 10.0-release-boot-only due to braindead mirror retention policy (clearly I am going to have to start local mirroring the dvd iso). Could not upgrade 10.3-release-boot-only to 11.0-release or 11.0-stable due to no mirrors Could not install FreeBSD-11.0-STABLE-amd64-20170323-r315855-bootonly.iso, no mirrors (note 10.3-bootonly did install, it just wouldn't upgrade) Can not update FreeBSD-11.0-STABLE-amd64-20170323-r315855-disc1.iso using: FreeBSD-update fetch install returns: src component not installed, skipped Looking up update.FreeBSD.org mirrors... none found. Fetching public key from update.FreeBSD.org... failed. No mirrors remaining, giving up. ping update.freebsd.org PING update5.freebsd.org (204.9.55.80): 56 data bytes 64 bytes from 204.9.55.80: icmp_seq=0 ttl=52 time=61.599 ms 64 bytes from 204.9.55.80: icmp_seq=1 ttl=52 time=60.528 ms ping6 update.freebsd.org PING6(56=40+8+8 bytes) 2001:470:e930::1 --> 2001:4978:1:420::cc09:3750 16 bytes from 2001:4978:1:420::cc09:3750, icmp_seq=0 hlim=56 time=53.656 ms 16 bytes from 2001:4978:1:420::cc09:3750, icmp_seq=1 hlim=56 time=52.460 ms Given that 10.3-bootonly installed, it appears that the mirror issue is related to 11.0, for both release and stable. FWIW: portsnap fetch on 11.0 also fails, but portsnap auto worked .?.?.?