From owner-freebsd-questions@FreeBSD.ORG Fri Jun 27 15:48:48 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBB95106566C for ; Fri, 27 Jun 2008 15:48:48 +0000 (UTC) (envelope-from astorms@ncircle.com) Received: from mail.ncircle.com (mail.ncircle.com [64.84.9.150]) by mx1.freebsd.org (Postfix) with ESMTP id B83BE8FC16 for ; Fri, 27 Jun 2008 15:48:48 +0000 (UTC) (envelope-from astorms@ncircle.com) Received: from CORP-MAIL.ad.ncircle.com (corpmail-01.ncircle.com [192.168.75.90]) by mail.ncircle.com (8.14.2/8.14.2) with ESMTP id m5RFV3kf074783 for ; Fri, 27 Jun 2008 08:31:04 -0700 (PDT) (envelope-from astorms@ncircle.com) Received: from 192.168.5.202 ([192.168.5.202]) by CORP-MAIL.ad.ncircle.com ([192.168.75.94]) via Exchange Front-End Server webmail-01.ad.ncircle.com ([192.168.75.93]) with Microsoft Exchange Server HTTP-DAV ; Fri, 27 Jun 2008 15:30:58 +0000 User-Agent: Microsoft-Entourage/11.4.0.080122 Date: Fri, 27 Jun 2008 08:30:57 -0700 From: Andrew Storms To: Message-ID: Thread-Topic: Phttpget problems (freebsd-update) Thread-Index: AcjYastcCirecEReEd2aUwARJIv+sA== Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Score: -4.358 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 64.84.9.150 Subject: Phttpget problems (freebsd-update) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2008 15:48:48 -0000 Anyone else experiencing issues related to phttpget when using freebsd-update? What I'm finding is that there is just enough delay between retrieval of the 6.2 and the 6.3 patches; that the upstream firewall closes the NAT. Then phttpget attempts to retrieve the 6.3 patch set and just assumes the session is already open. Firewall sends a RST back and phttpget doesn't attempt a new 3-way handshake. The end result is freebsd-update then just gives up. If it helps at all, I'm so far only seeing this happen behind a Cisco ASA appliance. Anybody else seen this and/or have a suggested work around? Thanks. ------- # sh freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching metadata signature for 6.2-RELEASE from update1.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. WARNING: This system is running a "foobar" kernel, which is not a kernel configuration distributed as part of FreeBSD 6.2-RELEASE. This kernel will not be updated: you MUST update the kernel manually before running "freebsd-update.sh install". The following components of FreeBSD seem to be installed: src/sys world/base world/dict world/doc world/manpages The following components of FreeBSD do not seem to be installed: kernel/generic kernel/smp src/base src/bin src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue src/sbin src/secure src/share src/tools src/ubin src/usbin world/catpages world/games world/info world/proflibs Does this look reasonable (y/n)? y Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Fetching files from 6.2-RELEASE for merging... done. Preparing to download files... done. Fetching 6888 patches.....10....20....30. done. Applying patches... done. Fetching 6748 files... failed. -----