From owner-freebsd-stable@freebsd.org Sat Sep 1 18:18:28 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAF25FF6ACB for ; Sat, 1 Sep 2018 18:18:28 +0000 (UTC) (envelope-from spork@bway.net) Received: from smtp1.bway.net (smtp1.v6.bway.net [IPv6:2607:d300:1::27]) (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 7722575C45 for ; Sat, 1 Sep 2018 18:18:28 +0000 (UTC) (envelope-from spork@bway.net) Received: from frankentosh.sporklab.com (pool-108-53-194-153.nwrknj.fios.verizon.net [108.53.194.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: spork@bway.net) by smtp1.bway.net (Postfix) with ESMTPSA id 9299695853; Sat, 1 Sep 2018 14:18:16 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: bad hash in repo From: Charles Sprickman In-Reply-To: Date: Sat, 1 Sep 2018 14:18:15 -0400 Cc: Pete Wright , freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8C150C27-844D-4F32-907B-8ABD7D711846@bway.net> References: <40cbc4e4-c0c8-e9f7-ba88-48dc226b032a@nomadlogic.org> To: Randy Bush X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2018 18:18:28 -0000 > On Sep 1, 2018, at 1:09 PM, Randy Bush wrote: >=20 >>>>> seeing a lot of these >>>>>=20 >>>>> Looking up update.FreeBSD.org mirrors... 2 mirrors found. >>>>> Fetching metadata signature for 11.1-RELEASE from = update4.freebsd.org... done. >>>>> Fetching metadata index... done. >>>>> Inspecting system... done. >>>>> Preparing to download files... done. >>>>> Fetching 2 patches.. done. >>>>> Applying patches... done. >>>>> Fetching 2 files... = 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has = incorrect hash. >>>> these continue; like for a week. for multiple servers, all on the >>>> global internet no filters other than samba etc. >>>=20 >>> have you forced pulling down metadata from the pkg servers? i have >>> gotten into this state in the past and a "pkg update -f" would get = me >>> out of that scenario. >>=20 >> # pkg update -f >> Updating FreeBSD repository catalogue... >> Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 =20 >> Fetching packagesite.txz: 100% 6 MiB 2.2MB/s 00:03 =20 >> Processing entries: 100% >> FreeBSD repository update completed. 32029 packages processed. >> All repositories are up to date. >> # freebsd-update fetch >> Looking up update.FreeBSD.org mirrors... 2 mirrors found. >> Fetching metadata signature for 11.1-RELEASE from = update5.freebsd.org... done. >> Fetching metadata index... done. >> Inspecting system... done. >> Preparing to download files... done. >> Fetching 2 patches.. done. >> Applying patches... done. >> Fetching 2 files... = 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has = incorrect hash. >=20 > this is now over two weeks. still multiple systems on public net, v4 > and dual stack. The other brute-force approach is: rm -rf /var/db/freebsd-update/* Also, is it always fetching from "update5.freebsd.org=E2=80=9D? Charles >=20 > randy > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org"