Bug 227632 - portsnap: snapshot is corrupt.
Summary: portsnap: snapshot is corrupt.
Status: Closed Not Enough Information
Alias: None
Product: Services
Classification: Unclassified
Component: Portsnap (show other bugs)
Version: unspecified
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-19 11:16 UTC by Heraldo Barros Bahiense Filho
Modified: 2019-05-24 18:43 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Heraldo Barros Bahiense Filho 2018-04-19 11:16:29 UTC 
[root@s40 /usr/home/hbbf]# portsnap auto
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching snapshot tag from ec2-sa-east-1.portsnap.freebsd.org... done.
Fetching snapshot metadata... done.
Updating from Tue Apr 17 07:44:48 -03 2018 to Thu Apr 19 06:59:00 -03 2018.
Fetching 5 metadata patches... done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 44 patches. 
(44/44) 100.00%  done.                                
done.
Applying patches... 
done.pping ffc917251f4bf6d46cd575349b8eacae8d7904aade459ebf1f72ee528350a938-cd00dc57e8c5446d6c30f3c6ef01c1bd6b3a80ea7d5a60cd50378a932e92696b (44 of       44 patchlist).
Fetching 43 new ports or files... /usr/sbin/portsnap: cannot open a27732396323b40f8e44b6cc4636ccb77cebf0e72c5d34f4c7c302b6ef422d7e.gz: No such file or directory
snapshot is corrupt.
Comment 1 Heraldo Barros Bahiense Filho 2018-04-19 11:23:57 UTC 
Presenting on all servers in my network...
Comment 2 Heraldo Barros Bahiense Filho 2018-04-19 11:30:37 UTC 
rm -rf /var/db/portsnap/*

portsnap auto
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching public key from ec2-sa-east-1.portsnap.freebsd.org... done.
Fetching snapshot tag from ec2-sa-east-1.portsnap.freebsd.org... done.
Fetching snapshot metadata... 

not continue. Stop at this point.
Comment 3 Heraldo Barros Bahiense Filho 2018-04-19 13:25:30 UTC 
[root@n43s /usr/home/hbbf]# portsnap auto
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching snapshot tag from ec2-sa-east-1.portsnap.freebsd.org... done.
Fetching snapshot metadata... done.
Updating from Wed Apr 18 07:53:12 -03 2018 to Thu Apr 19 09:52:07 -03 2018.
Fetching 0 metadata patches. done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 40 patches. 
(40/40) 100.00%  done.                                
done.
Applying patches... 
done.pping ffc917251f4bf6d46cd575349b8eacae8d7904aade459ebf1f72ee528350a938-cd00dc57e8c5446d6c30f3c6ef01c1bd6b3a80ea7d5a60cd50378a932e92696b (40 of       40 patchlist).
Fetching 40 new ports or files... /usr/sbin/portsnap: cannot open a27732396323b40f8e44b6cc4636ccb77cebf0e72c5d34f4c7c302b6ef422d7e.gz: No such file or directory
snapshot is corrupt.
Comment 4 David 2019-05-24 18:43:56 UTC 
Heraldo,

I had this same problem.  Basically, the portsnap mirror on EC2 AWS in São Paulo (Region ec2-sa-east-1) isn't working properly and it's the one automatically selected for you like it was for me (connecting from Chile).

I couldn't find a list of portsnaps servers, but fortunately I have a FreeBSD server located outside South America so I could try from there and get it's portsnap mirror.

Here you go... This command worked for me:

portsnap -s ec2-eu-west-1.portsnap.freebsd.org fetch extract

David