RE: portsnap fetch errors
From: Elwell, Richard Sent: Wednesday, March 26, 2008 10:40 AM To: 'freebsd-questions@freebsd.org' Subject: portsnap fetch errors Greetings, I get the following error when I run portsnap fetch: Fetching 14248 new ports or files... /usr/sbin/portsnap: cannot open d5742d6e9ca3b11450f23606ae6a16b391a12f4c7b2d4fc638513ce34f7c2c25.gz: No such file or directory snapshot is corrupt. A quick search led to a similar problem in the past: Justin Meyer wrote: I'm doing a portsnap fetch here, and getting the following error: [snip] Can anybody tell me what's going on here, or how to fix it? Some files didn't get uploaded from the machine which performs the portsnap builds to the mirrors due to a network outage (note to self: I need to handle problems like this better!) I've manually copied the missing files into the appropriate places and everything should be working again now. Colin Percival Is this a similar problem, or do I likely have another issue? Rich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: portsnap fetch errors
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Elwell, Richard I get the following error when I run portsnap fetch: Fetching 14248 new ports or files... /usr/sbin/portsnap: cannot open d5742d6e9ca3b11450f23606ae6a16b391a12f4c7b2d4fc638513ce34f7c2c 25.gz: No such file or directory snapshot is corrupt. A quick search led to a similar problem in the past: Richard, By any chance is your portsnap using a proxy server, possibly squid? If so this may get around the problem prior to running your portsnap. # sysctl net.inet.ip.portrange.randomized=0 You may want to check the value first, and reset it after the portsnap. Maybe something like this in your portsnap script. - barry -- snip -- RANDOMIZED=`sysctl -n net.inet.ip.portrange.randomized` portsnap fetch update # or portsnap cron update sysctl net.inet.ip.portrange.randomized=$RANDOMIZED -- snip -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap fetch errors
On Wed, 26 Mar 2008 15:52:51 - Barry Byrne [EMAIL PROTECTED] wrote: By any chance is your portsnap using a proxy server, possibly squid? If so this may get around the problem prior to running your portsnap. # sysctl net.inet.ip.portrange.randomized=0 Why would that make a difference? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: portsnap fetch errors
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of RW Sent: 26 March 2008 18:35 To: freebsd-questions@freebsd.org Subject: Re: portsnap fetch errors On Wed, 26 Mar 2008 15:52:51 - Barry Byrne [EMAIL PROTECTED] wrote: By any chance is your portsnap using a proxy server, possibly squid? If so this may get around the problem prior to running your portsnap. # sysctl net.inet.ip.portrange.randomized=0 Why would that make a difference? I think some versions of squid may be a bit broken with respect to correctly handling HTTP/1.1 and in the case of portsnap downloading many files, squid starts closing some of the open connections, which portsnap then attempts to reuse. There was a thread on one of the FreeBSD lists in late 2006. Google a bit and you'll probably find it. Don't know for certain this is your problem, but it did fix it when I came across the problem. - barry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
