Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 01 Sep 2018 10:09:46 -0700
From:      Randy Bush <randy@psg.com>
To:        Pete Wright <pete@nomadlogic.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: bad hash in repo
Message-ID:  <m236utrvol.wl-randy@psg.com>
In-Reply-To: <m2y3cxg6o4.wl-randy@psg.com>
References:  <m24lftov3m.wl-randy@psg.com> <m2zhxegyro.wl-randy@psg.com> <40cbc4e4-c0c8-e9f7-ba88-48dc226b032a@nomadlogic.org> <m2y3cxg6o4.wl-randy@psg.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>>>> 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... 104969ef03336523729ea1df2547267441a13cb040c778e971=
b74103e88dbc77 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?=A0 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... 104969ef03336523729ea1df2547267441a13cb040c778e971b74=
103e88dbc77 has incorrect hash.

this is now over two weeks.  still multiple systems on public net, v4
and dual stack.

randy



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m236utrvol.wl-randy>