From owner-freebsd-stable@freebsd.org Sun Aug 16 19:20:08 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 EEB799BB431 for ; Sun, 16 Aug 2015 19:20:08 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B98B21DE1 for ; Sun, 16 Aug 2015 19:20:08 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: by igbjg10 with SMTP id jg10so42098364igb.0 for ; Sun, 16 Aug 2015 12:20:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Lh84QqbIx5Qr5D4Z+Sv0Sy1zOa4h3GjtAT1avwubLkk=; b=sJ6xnU0BBj3WI0VJc668Q9DT70/vUQyVEftKzpeXOKmkP/fPpYj7TgMjhL9wqUQafs UhJ/FUJ+SWTtpD3rUUMNV1FQ9olw80hNQkpqwWu9wF+McNIKetEuV+6k4mApbpv/WMEO YXExb63U9+iPvGOjHbGwO4F2Y/BD1CSJ/UntuAZKxkGMkSJimqcYAEMH1Vm2PxFJplKI Fw8pitYjSxnVcdwXZI+ea8FBg4Pr2VXarKVAMBfzE7fu2DUKSWG+kJhBO2sS9sjOqd4m dWg1H/NT/URWZ0V27PwQSbMgoYcyoYA8YVizQZiutRz08s07MBhsrN0/SSm2q+rdZBu5 Ekkw== MIME-Version: 1.0 X-Received: by 10.50.97.71 with SMTP id dy7mr13443954igb.76.1439752808225; Sun, 16 Aug 2015 12:20:08 -0700 (PDT) Received: by 10.107.131.163 with HTTP; Sun, 16 Aug 2015 12:20:08 -0700 (PDT) In-Reply-To: References: <2C3CC22D-749A-4B92-885C-D73311997050@gid.co.uk> <20150816180715.GM40589@home.opsec.eu> Date: Sun, 16 Aug 2015 22:20:08 +0300 Message-ID: Subject: Re: freebsd-update to 10.2-RELEASE broken ? From: Kimmo Paasiala To: Christian Kratzer Cc: Kurt Jaeger , "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 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 19:20:09 -0000 On Sun, Aug 16, 2015 at 10:07 PM, Christian Kratzer wrote: > Hi, > > On Sun, 16 Aug 2015, Kurt Jaeger wrote: > >> >> 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. > > > hmmm. Thanks for pointing me at the dns issue. > > I actually did not see that message as it seems to only appear on > subsequent rounds of running freebsd-update. I always deleted > /var/db/freebsd-update and thus always started clean. > > I was able to complete the freebsd-update upgrade when I manually > specified on of the mirrors as in: > > freebsd-update -s update2.freebsd.org -r 10.2-RELEASE upgrade > > So this does seem to be a dns related issue. It could also be the > related to parsing the results of the dns lookup. > > Anyway seems we have a workaround if we specify the mirrors manually. > > Greetings > Christian > > -- It could be the classic fall back to TCP on SRV records problem on your upstream DNS forwarder if you're using one: http://lists.freebsd.org/pipermail/freebsd-ports/2012-May/074801.html The cure would be to use your own caching DNS resolver (configured to query the authoritative name servers directly) such as dns/unbound. -Kimmo