portsnap snapshot corruption?
Giorgos Keramidas
keramida at FreeBSD.org
Thu Sep 20 14:04:30 PDT 2007
On 2007-09-20 21:42, Giorgos Keramidas <keramida at FreeBSD.org> wrote:
> Hi Colin,
>
> I've tried removing all of /var/db/portsnap/* and refetching several
> times today, but all the attempts resulted in corrupt snapshots, like
> this one:
>
> % root at kobe:/root# rm -fr /var/db/portsnap/*
> % root at kobe:/root# portsnap fetch
> % Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
> % Fetching public key from portsnap3.FreeBSD.org... done.
> % Fetching snapshot tag from portsnap3.FreeBSD.org... done.
> % Fetching snapshot metadata... done.
> % Fetching snapshot generated at Thu Sep 20 04:07:10 EEST 2007:
> % 1a2086f1a8eea72b21ecc5c6a03587a26e3b86055bc54a100% of 49 MB 1451 kBps 00m00s
> % Extracting snapshot... done.
> % Verifying snapshot integrity... gunzip: snap/2bafbd0d8edc7a7cfa7e19833986ae4032f82006fd0d65cba9c4a75b432b5c8e.gz: unexpected end of file
> % gunzip: snap/2bafbd0d8edc7a7cfa7e19833986ae4032f82006fd0d65cba9c4a75b432b5c8e.gz: uncompress failed
> % snapshot corrupt.
> % root at kobe:/root#
>
> Is something wrong with the portsnap servers, or should I try to see if
> there's something odd with my latest CURRENT upgrade?
Damn, right after having spent an hour on this *and* posting a message,
our local admin notified us that our network has started using a
transparent proxy -- which is apparently broken.
Sorry for the noise. I'll try to resolve this with our IT guys :)
More information about the freebsd-current
mailing list