Date: Fri, 04 Aug 2006 19:21:01 -0700 From: Colin Percival <cperciva@freebsd.org> To: Gary Newcombe <gary@pattersonsoftware.com> Cc: freebsd-questions@freebsd.org Subject: Re: portsnap oddities Message-ID: <44D4008D.1000309@freebsd.org> In-Reply-To: <000001c6b830$80213a00$1f01a8c0@tosh> References: <000001c6b830$80213a00$1f01a8c0@tosh>
next in thread | previous in thread | raw e-mail | index | archive | help
Gary Newcombe wrote: > I'm getting the following error when I use portsnap lately on one of my > servers: > [snip] > Fetching 2 new ports or files... > gunzip: stdin: not in gzip format > snapshot is corrupt. > > I have now removed /var/db/portsnap and started from scratch 3 times. This > fixes the problem, but a few days later, I get the same story. I haven't had > any problems on any of the other servers (although they have older kernels), > so I'm guessing this could be a problem with portsnap from this kernel build > or it's related to something else. First, the obvious thing to check: Are you running out of disk space on /var ? Second, please run 'portsnap --debug fetch' and send me the output; this will give me a chance of identifying the problem. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44D4008D.1000309>