Bug 213418

Summary:	portsnap fetch fails due to wrong serverlist entry
Product:	Services	Reporter:	Santiago Pastorino <spastorino>
Component:	Portsnap	Assignee:	Colin Percival <cperciva>
Status:	Closed FIXED
Severity:	Affects Many People	CC:	ports-bugs, ports-secteam
Priority:	---
Version:	unspecified
Hardware:	Any
OS:	Any

Description Santiago Pastorino 2016-10-12 16:30:54 UTC

# portsnap fetch
Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found.
Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
Fetching snapshot metadata... done.
Updating from Mon Oct 10 01:42:51 EDT 2016 to Mon Oct 10 15:04:19 EDT 2016.
Fetching 0 metadata patches. done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 2 patches.
(2/2) 100.00%  done.
done.
Applying patches...
done.pping 98bb23a5c281b23a8de7849749ca1d9172a0eefe7d06438c9304966636a270a2-e26a1ffb6a660653d5d1aa162b78c50f95ae803e5b7534b047285062a47b045b (2 of        2 patchlist).
Fetching 2 new ports or files... /usr/sbin/portsnap: cannot open efae62888f99c084af0c78bfb3553953527887ee3344add64eb723179d7cea37.gz: No such file or directory
snapshot is corrupt.

Fix for now ...

# portsnap -s ec2-eu-west-1.portsnap.freebsd.org fetch
Looking up ec2-eu-west-1.portsnap.freebsd.org mirrors... none found.
Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
Fetching snapshot metadata... done.
Updating from Mon Oct 10 01:42:51 EDT 2016 to Wed Oct 12 12:08:36 EDT 2016.
Fetching 5 metadata patches... done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 163 patches.
(163/163) 100.00%  done.
done.
Applying patches...
done.
Fetching 24 new ports or files... done.

Comment 1 Santiago Pastorino 2016-10-12 19:31:44 UTC

Found the issue.

If you run ...

# host -t srv _http._tcp.portsnap.FreeBSD.org
_http._tcp.portsnap.FreeBSD.org has SRV record 1 10 80 ec2-sa-east-1.portsnap.freebsd.org.
_http._tcp.portsnap.FreeBSD.org has SRV record 2 10 80 isc.portsnap.freebsd.org.
_http._tcp.portsnap.FreeBSD.org has SRV record 2 10 80 sourcefire.portsnap.freebsd.org.
_http._tcp.portsnap.FreeBSD.org has SRV record 2 10 80 your-org.portsnap.freebsd.org.
_http._tcp.portsnap.FreeBSD.org has SRV record 3 10 80 ec2-eu-west-1.portsnap.freebsd.org.
_http._tcp.portsnap.FreeBSD.org has SRV record 4 10 80 ec2-ap-northeast-1.portsnap.freebsd.org.
_http._tcp.portsnap.FreeBSD.org has SRV record 4 10 80 ec2-ap-southeast-2.portsnap.freebsd.org.

As you can see your-org.portsnap.freebsd.org is in the list. And that is run here https://svnweb.freebsd.org/base/release/11.0.1/usr.sbin/portsnap/portsnap/portsnap.sh?view=markup#l368

Comment 2 Santiago Pastorino 2016-10-12 19:36:08 UTC

And also ...

# host isc.portsnap.freebsd.org
Host isc.portsnap.freebsd.org not found: 3(NXDOMAIN)

isc does not resolve neither.

Not sure what was the intention but seems like those entries should be removed from portsnap DNS servers.

Comment 3 Colin Percival freebsd_committer

2016-10-12 20:37:50 UTC

The your-org mirror crashed because we threw a lot of 11.0-RELEASE upgrading load at it.  It's back up now.

I'll look into the situation with the ISC mirror.

Comment 4 Colin Percival freebsd_committer

2016-10-12 20:54:41 UTC

The ISC mirror went away and is not coming back.  I've garbage collected those DNS entries.

Comment 5 Santiago Pastorino 2016-10-12 21:07:56 UTC

Cool, now is better.

Still ...

# portsnap fetch
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
Latest snapshot on server is older than what we already have!
Cowardly refusing to downgrade from Wed Oct 12 12:08:36 EDT 2016
to Mon Oct 10 15:04:19 EDT 2016.

Comment 6 Colin Percival freebsd_committer

2016-10-12 21:20:02 UTC

The your-org mirror is still resyncing after some crash-related data loss.  Try using ec2-eu-west-1.portsnap.freebsd.org for now.