Bug 197240 - update3.freebsd.org is out of date
Summary: update3.freebsd.org is out of date
Status: Closed FIXED
Alias: None
Product: Services
Classification: Unclassified
Component: FreeBSD Update (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Some People
Assignee: Security Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-01 12:44 UTC by Derek Schrock
Modified: 2015-02-09 06:55 UTC (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Derek Schrock 2015-02-01 12:44:01 UTC
It appears update3.freebsd.org is out of date.
update{2,4,5}.freebsd.org appear to be 9.3-p9 and 10.1-p5

From a 10.1-p5 machine:
$ sudo freebsd-update -s update3.freebsd.org  fetch
Looking up update3.freebsd.org mirrors... none found.
Fetching metadata signature for 10.1-RELEASE from update3.freebsd.org... done.

Files on mirror (10.1-RELEASE-p4) appear older than what
we are currently running (10.1-RELEASE-p5)!
Cowardly refusing to proceed any further.

From a 9.3-p8 machine:
# freebsd-update -s update3.freebsd.org fetch
Looking up update3.freebsd.org mirrors... none found.
Fetching metadata signature for 9.3-RELEASE from update3.freebsd.org... done.

Files on mirror (9.3-RELEASE-p8) appear older than what
we are currently running (9.3-RELEASE-p9)!
Cowardly refusing to proceed any further.
Comment 1 Rudolf Čejka 2015-02-06 13:26:01 UTC
It showed up that the problem was in error in tar, after upgrade from FreeBSD 9.3 to FreeBSD 10.1. Until it is fixed, I added empty line into tar exclude list, which bypasses the error. The state of update3.freebsd.org should be current again.

For further details in tar bug, please see:

https://code.google.com/p/libarchive/issues/detail?id=401

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197371
Comment 2 Derek Schrock 2015-02-06 13:57:21 UTC
I don't know if I misread your comment but has this only been fixed for 9.3 
systems?  You need bsdtar 3.1.2 to be fixed for update3 to server 10.1-RELEASE?

If so add bug 197371 to depends on?

It appears the 10.1-RELEASE directory at update3 is gone.

$ curl -I http://update3.freebsd.org/10.1-RELEASE/
HTTP/1.1 404 Not Found
Date: Fri, 06 Feb 2015 13:55:20 GMT
Server: Apache/2.4.10 (FreeBSD)
Content-Type: text/html; charset=iso-8859-1


$ sudo freebsd-update -s update3.freebsd.org  fetch
Password:
Looking up update3.freebsd.org mirrors... none found.
Fetching metadata signature for 10.1-RELEASE from update3.freebsd.org... failed.
No mirrors remaining, giving up.


However, I see update3 now works with 9.3-p9:

# freebsd-update -s update3.freebsd.org fetch
Looking up update3.freebsd.org mirrors... none found.
Fetching metadata signature for 9.3-RELEASE from update3.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 9.3-RELEASE-p9.
Comment 3 Rudolf Čejka 2015-02-06 14:15:44 UTC
Oh no... I'm sorry.

Empty line in exclude list solved tar error, but unfortunately caused another problem, this time in mirror script, so all datas in update3.FreeBSD.org have to be restored now.

Hope that exclude list with "EMPTY" line will fix both tar and mirror script...
Comment 4 Derek Schrock 2015-02-07 21:46:12 UTC
It appears update3.freebsd.org is now serving 10.1-p5

From a 10.1-p5 system:

....
Looking up update3.freebsd.org mirrors... none found.
Fetching metadata signature for 10.1-RELEASE from update3.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 10.1-RELEASE-p5.
Comment 5 Colin Percival freebsd_committer freebsd_triage 2015-02-07 23:55:20 UTC
I think everything's working with this mirror now, but I'm going to wait 24 hours before I ask clusteradm to add it back to the SRV mirror pool just in case anyone notices any other issues.
Comment 6 Rudolf Čejka 2015-02-08 22:44:13 UTC
Yes, I hope so that everything is solved now, including exclude list suggested by Colin.
Comment 7 Colin Percival freebsd_committer freebsd_triage 2015-02-09 06:55:38 UTC
I've just asked clusteradm to re-enable this in DNS.  Thanks!