Date: Sat, 09 Dec 2006 17:25:50 -0800 From: Colin Percival <cperciva@freebsd.org> To: Adam McDougall <mcdouga9@egr.msu.edu> Cc: freebsd-current@freebsd.org Subject: Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update Message-ID: <457B621E.3020100@freebsd.org> In-Reply-To: <20061210010823.GS81923@egr.msu.edu> References: <20061210010823.GS81923@egr.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Adam McDougall wrote: > # portsnap fetch update > [...] > Fetching 2688 new ports or files... /usr/sbin/portsnap: cannot open > 3f115cb168a8e51fd0d19798f005ab7a251a1de6a5b9eda60cd327b60aa48799.gz: No such file or > directory > snapshot is corrupt. > > 2597 should have been fetched, but there was a stall at 30.. and after about a minute, > it continued on to 410...... and gave up apparently. For all my servers without > direct internet access, I have to run portsnap several times until it succeeds. You have four options: (a) Lower pf's tcp.closed timeout, (b) Increase the high port range, (c) Fix squid so that it groks HTTP/1.1 properly, or (d) Stop using squid. The problem here is that your proxy is closing portsnap's HTTP connection after each file is downloaded. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?457B621E.3020100>