Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Sep 2007 14:30:29 -0700
From:      "Kevin Oberman" <oberman@es.net>
To:        Giorgos Keramidas <keramida@FreeBSD.org>
Cc:        freebsd-current@FreeBSD.org, Colin Percival <cperciva@FreeBSD.org>
Subject:   Re: portsnap snapshot corruption? 
Message-ID:  <20070920213029.DBEE945027@ptavv.es.net>
In-Reply-To: Your message of "Thu, 20 Sep 2007 21:46:06 %2B0300." <20070920184606.GA73060@kobe.laptop> 

next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1190323829_17203P
Content-Type: text/plain; charset=us-ascii

> On 2007-09-20 21:42, Giorgos Keramidas <keramida@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@kobe:/root# rm -fr /var/db/portsnap/*
> > % root@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@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 :)

In my experience the term "transparent proxy" is an oxymoron (like jumbo shrimp). "Transparent" proxies seem to vary from the distorions of a fun-house mirror to barely translucent.  I really, really dislike them when trying to figure out the corrective lenses needed with each of them.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751



--==_Exmh_1190323829_17203P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
Comment: Exmh version 2.5 06/03/2002

iD8DBQFG8uZ1kn3rs5h7N1ERAiQQAJwLTKEYWsqGobhe1gh8eT6RAmILKACfX7Ok
g2PK8tFmgyUV4LjAVk7auZs=
=4wRf
-----END PGP SIGNATURE-----

--==_Exmh_1190323829_17203P--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070920213029.DBEE945027>