portsnap fetch : "snapshot is corrupt"

Avinash Sonawane rootkea at gmail.com
Fri May 15 13:48:41 UTC 2015

On Fri, May 15, 2015 at 7:01 AM, andrew clarke <mail at ozzmosis.com> wrote:
> On Thu 2015-05-14 20:13:53 UTC+0530, Avinash Sonawane (rootkea at gmail.com) wrote:
>> Hello!
>> I am using FreeBSD 10.1 RELEASE
>> Whenever I try to fetch the portsnap it says "snapshot is corrupt". I
>> rmed `/var/db/portsnap/*` to start from fresh but then too when I
>> issue `portsnap fetch` it says the same.
>> Here is the complete error message : http://pastebin.com/AiLn8QdE
>> Anybody has any idea how do I get that missing gz?
> I've noticed this happen in the past on the odd occasion. I ruled out
> hardware error on my machine and put it down to some sort of
> corruption (or more likely syncronisation problem) with the snapshot
> server(s). If I waited a while (a few hours) then re-ran portsnap the
> errors went away.

Same here. Now I can fetch the portsnap without any "sync" errors.

But from browsing the web and from the mailing list archives I found
this same problem to be quite frequent and having the only apparent
solution "just to wait few hours"

Is this specific issue is bound to happen? I mean it seems as if
community has adjusted with it. Is this "sync" issue is inherent in
portsnap design?

I am sorry but I am new to BSD world (Just completed a week!) so have
no idea how things work here.

Thank you.

Avinash Sonawane (RootKea)
PICT, Pune

More information about the freebsd-questions mailing list