From owner-freebsd-stable@freebsd.org Sun Aug 16 18:07:16 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D23A9BB9D7 for ; Sun, 16 Aug 2015 18:07:16 +0000 (UTC) (envelope-from pi@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C3DF51AC8 for ; Sun, 16 Aug 2015 18:07:15 +0000 (UTC) (envelope-from pi@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1ZR2Kx-000JOf-LV; Sun, 16 Aug 2015 20:07:15 +0200 Date: Sun, 16 Aug 2015 20:07:15 +0200 From: Kurt Jaeger To: Bob Bishop Cc: Christian Kratzer , freebsd-stable@freebsd.org Subject: Re: freebsd-update to 10.2-RELEASE broken ? Message-ID: <20150816180715.GM40589@home.opsec.eu> References: <2C3CC22D-749A-4B92-885C-D73311997050@gid.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2C3CC22D-749A-4B92-885C-D73311997050@gid.co.uk> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Aug 2015 18:07:16 -0000 Hi! [bob wrote] > [ck wrote] > > I have been trying to update several of my FreeBSD 10.1 amd64 > > VM to 10.2-RELEASE with freebsd-update and have been failing with > > an incorrect hash error. > FWIW I had the same issue yesterday on a couple of systems. > Repeating freebsd-update worked after two or three goes. I've seen the same problem on several hosts and discussed it by mail with gjb@. We assumed that I have a DNS problem because of this line: > Looking up update.FreeBSD.org mirrors... none found. This happens with this query inside the freebsd-update script, at line 950: host -t srv _http._tcp.update.FreeBSD.org If you prime your DNS cache with manual queries, then freebsd-update will sometimes find the hosts and will report that it found some hosts. But, I just tried to reproduce this and failed, the problem persists. So, yes, it looks like a real issue. -- pi@opsec.eu +49 171 3101372 5 years to go !