On Wed, Oct 8, 2008 at 2:25 AM, Barry Byrne <[EMAIL PROTECTED]> wrote: >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Steve Franks >> Sent: 07 October 2008 21:57 > >> I've googled high & low but I cannot find much other that "this cannot >> happen" replies. I've got a dual boot to amd64 and i386. The amd64 >> hasn't been able to portsnap fetch or cron since march. The i386 I >> just installed, and it portsnap's fine, so it's not a firewall or >> related issue. I've checked my key and it looks ok. What am I >> missing? >> >> Best, >> Steve >> >> >> dystant# portsnap fetch >> Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. >> Fetching snapshot tag from portsnap1.FreeBSD.org... done. >> Fetching snapshot metadata... done. >> Updating from Mon Mar 3 07:50:14 MST 2008 to Tue Oct 7 >> 12:43:25 MST 2008. >> Fetching 0 metadata patches. done. >> Applying metadata patches... done. >> Fetching 0 metadata files... done. >> Fetching 12365 patches.. done. >> Applying patches... done. >> Fetching 13708 new ports or files... /usr/sbin/portsnap: cannot open >> e53d7ea3f6fbc2e6a87a1f194ea623fc6b27c74d9aecfd61e0d765e86d861ad5.gz: >> No such file or directory >> snapshot is corrupt. >> dystant# > > Steve: > > Are you using a proxy server? If so this could be perhaps the proxy server > not fully supporting HTTP/1.1 persistent > connections. Can you try this: > > sysctl net.inet.ip.portrange.randomized=0 > portsnap fetch update >
Well, I can't say for sure if that works. I'm definitely behind a ugly cheap-o windows firewall (iserver), but sometimes it works, and sometimes not...can't hurt, though, right? Best, Steve _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
