From owner-freebsd-stable@freebsd.org Thu Aug 4 19:55:26 2016 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 96665BAFF51 for ; Thu, 4 Aug 2016 19:55:26 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (mail.sorbs.net [67.231.146.200]) by mx1.freebsd.org (Postfix) with ESMTP id 894321A16 for ; Thu, 4 Aug 2016 19:55:25 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0OBE00269ICR2K00@hades.sorbs.net> for freebsd-stable@freebsd.org; Thu, 04 Aug 2016 13:02:53 -0700 (PDT) Subject: Re: freebsd-update borked? To: Yass Amed , freebsd-stable@freebsd.org References: <1f91d38b-967f-73ea-11c0-c76fa8c46bb9@gmail.com> From: Michelle Sullivan Message-id: <57A39DA4.2040704@sorbs.net> Date: Thu, 04 Aug 2016 21:55:16 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 In-reply-to: <1f91d38b-967f-73ea-11c0-c76fa8c46bb9@gmail.com> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2016 19:55:26 -0000 Yass Amed wrote: > On 08/04/2016 07:00 AM, freebsd-stable-request@freebsd.org wrote: >> Message: 1 >> Date: Wed, 03 Aug 2016 17:51:13 +0200 >> From: Michelle Sullivan >> To: St?phane Dupille via freebsd-stable >> Subject: freebsd-update borked? >> Message-ID:<57A212F1.6060309@sorbs.net> >> Content-Type: text/plain; CHARSET=US-ASCII; format=flowed >> >> As per the subject... >> >> >> [root@cheetah ~]# freebsd-update -r 9.3-RELEASE upgrade >> Looking up update.FreeBSD.org mirrors... none found. >> Fetching metadata signature for 9.2-RELEASE from >> update.FreeBSD.org... done. >> Fetching metadata index... done. >> Fetching 1 metadata patches. done. >> Applying metadata patches... done. >> Fetching 1 metadata files... gunzip: (stdin): unexpected end of file >> metadata is corrupt. >> [root@cheetah ~]# mv /var/db/freebsd-update /var/db/freebsd-update.9.2 >> [root@cheetah ~]# mkdir /var/db/freebsd-update >> [root@cheetah ~]# freebsd-update -r 9.3-RELEASE upgrade >> Looking up update.FreeBSD.org mirrors... none found. >> Fetching public key from update.FreeBSD.org... done. >> Fetching metadata signature for 9.2-RELEASE from >> update.FreeBSD.org... done. >> Fetching metadata index... done. >> Fetching 2 metadata files... gunzip: (stdin): unexpected end of file >> metadata is corrupt. >> [root@cheetah ~]# uname -a >> FreeBSD cheetah.sorbs.net 9.2-RELEASE-p15 FreeBSD 9.2-RELEASE-p15 #0: >> Mon Nov 3 20:31:29 UTC 2014 >> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > See this thread https://forums.freebsd.org/threads/28992/ you might > have a DNS issue according to this line "Looking up update.FreeBSD.org > mirrors... none found ". > OR, "sudo rm -f /var/db/freebsd-update/*.gz" and re-download the file > again. Well the: [root@cheetah ~]# mv /var/db/freebsd-update /var/db/freebsd-update.9.2 [root@cheetah ~]# mkdir /var/db/freebsd-update Would have done the same thing... DNS should be fine... appears to be: [michelle@cheetah /usr/home/michelle]$ dig update.freebsd.org ; <<>> DiG 9.8.4-P2 <<>> update.freebsd.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39566 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 6 ;; QUESTION SECTION: ;update.freebsd.org. IN A ;; ANSWER SECTION: update.freebsd.org. 600 IN CNAME update5.freebsd.org. update5.freebsd.org. 600 IN A 204.9.55.80 ;; AUTHORITY SECTION: freebsd.org. 600 IN NS ns2.isc-sns.com. freebsd.org. 600 IN NS ns1.isc-sns.net. freebsd.org. 600 IN NS ns3.isc-sns.info. ;; ADDITIONAL SECTION: ns1.isc-sns.net. 3600 IN A 72.52.71.1 ns1.isc-sns.net. 3600 IN AAAA 2001:470:1a::1 ns2.isc-sns.com. 3600 IN A 63.243.194.1 ns2.isc-sns.com. 3600 IN AAAA 2001:5a0:10::1 ns3.isc-sns.info. 3600 IN A 63.243.194.1 ns3.isc-sns.info. 3600 IN AAAA 2001:5a0:10::1 ;; Query time: 164 msec ;; SERVER: 89.150.192.2#53(89.150.192.2) ;; WHEN: Thu Aug 4 22:41:04 2016 ;; MSG SIZE rcvd: 294 And actually it'll do this: [michelle@cheetah /usr/home/michelle]$ host -t srv _http._tcp.update.freebsd.org _http._tcp.update.freebsd.org has SRV record 1 40 80 update6.freebsd.org. _http._tcp.update.freebsd.org has SRV record 1 50 80 update5.freebsd.org. _http._tcp.update.freebsd.org has SRV record 1 5 80 update3.freebsd.org. _http._tcp.update.freebsd.org has SRV record 1 35 80 update4.freebsd.org. Which actually returns this: [michelle@cheetah /usr/home/michelle]$ host -t srv _http._tcp.update.freebsd.org | sed -nE "s/update.freebsd.org (has SRV record|server selection) //p" | cut -f 1,2,4 -d ' ' | sed -e 's/\.$//' | sort _http._tcp.1 35 update4.freebsd.org _http._tcp.1 40 update6.freebsd.org _http._tcp.1 5 update3.freebsd.org _http._tcp.1 50 update5.freebsd.org You'll note however, that now... [michelle@cheetah /usr/home/michelle]$ sudo freebsd-update -r 9.3-RELEASE upgrade Password: Looking up update.FreeBSD.org mirrors... none found. Fetching metadata signature for 9.2-RELEASE from update.FreeBSD.org... done. Fetching metadata index... done. Fetching 2 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic world/base world/doc The following components of FreeBSD do not seem to be installed: src/src world/games world/lib32 Does this look reasonable (y/n)? y Fetching metadata signature for 9.3-RELEASE from update.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. . . etc.. So what ever was broken is not now... and it still says "Looking up update.FreeBSD.org mirrors... none found." Thanks for trying... > > > FYI: 9.3 will reach end-of-life in less than 4mos (try one of the 10.Xs). Not a hope in hell of that they don't work on this box, but even so the recommended path is go to the latest before the upgrade (and having not done that in the past and ended up bricking the box, I think it still stands.) -- Michelle Sullivan http://www.mhix.org/